Earlier quoted context omitted.
For me it's at least the following: - Attention to detail - Control of flow (if this then that) mentality - More binary thinking - Precision when describing (programming does not allow ambiguity) - A lot of frustration tolerance :) That's at least my experience
> Precision when describing (programming does not allow ambiguity) Really? Should we count how many bugs happen due to type conversion, precision errors, off by one etc?
Why are so many successful founding CEOs software engineers?
361–365 of 365 posts
Re: Why are so many successful founding CEOs software engineers?
#362Re: Why are so many successful founding CEOs software engineers?
#363Earlier quoted context omitted.
not to be pedantic but drywall is screwed in not nailed. i happen to be a software engineer who has also built actual houses.
Once upon a time it was nailed. Screws are a relatively recent change, I've used both. The problem with nails is that they walk out over time. Secondarily, they can become "squeaky" when used in floors.
Re: Why are so many successful founding CEOs software engineers?
#364Earlier quoted context omitted.
I don't know how true the % is, but that is what Howell claimed and several Google employees verified that his software was used by significant parts of Google's engineering staff. At any rate, the point is that a guy who used software used by a large portion of Google's engineering team because it was superior to the in-house solution could not get a job at Google because he failed to answer a programming question i…
I have no idea how great a developer Howell is, but it's simply not true that Homebrew was used by many Google employees. I was at Google at that time (2015), had a macbook for several years, and had never even heard of Homebrew. Google is a linux shop, and you were generally not allowed to even keep the source code in your notebook.
Re: Why are so many successful founding CEOs software engineers?
#365Earlier quoted context omitted.
I have no idea how great a developer Howell is, but it's simply not true that Homebrew was used by many Google employees. I was at Google at that time (2015), had a macbook for several years, and had never even heard of Homebrew. Google is a linux shop, and you were generally not allowed to even keep the source code in your notebook.
Where would one keep the source code then - if not locally?