Remove Agile Remove Engineer Remove Java Remove Software Engineering
article thumbnail

Lessons Learned: About the author

Startup Lessons Learned

In 2007, BusinessWeek named Ries one of the Best Young Entrepreneurs of Tech and in 2009 he was honored with a TechFellow award in the category of Engineering Leadership. He is the co-author of several books including The Black Art of Java Game Programming (Waite Group Press, 1996). An engineer who can talk intelligently about gender!

article thumbnail

Lessons Learned: The ABCDEF's of conducting a technical interview

Startup Lessons Learned

Finding great engineers is hard; figuring out whos good is even harder. The six key attributes spell ABCDEF: Agility. When talking about their past experience, candidates with agility will know why they did what they did in a given situation. I have found this quite rare in engineers. At first, I thought I was doing well.

Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

article thumbnail

CEO Friday: Why we don’t hire.NET programmers

blog.expensify.com

As one of the coherent commentators says below, Joel Spolsky himself laments schools teaching Java with the same basic reasoning of my article above, albeit more diplomatically stated.) .NET My example: I have mainly programmed _by choice_ in Python, Ruby, Scala, Haskell, C# and currently I’m doing Java. Alcides Fonseca.

Java 107
article thumbnail

How to hire a programmer to make your ideas happen

sivers.org

But what I think was hard, and it was something he couldnt consider was that it would be harder to find a *maintaining* programmer, and how much it would cost to run the software, because of technical details he didnt understand. Would love to hear your insights sometime into how to partner with engineers. This is great info.