News for hackers. Stuff that matters.
Re:San Francisco Bubble by IndianAstronaut on Friday January 29, 2016 @01:01PM (#10997029)
>Djikstra said "Beware premature optimization" and that's quite true.

This is why a product I was working on almost got killed. The senior engineer working on it wanted perfection before delivery. The project was already one year overdue. He suddenly came in one day and rushed me to finish up something and he wrapped up a couple things and we launched at the end of the week.

Found out that the project was going to be axed if we didn't deliver very soon.

Re:San Francisco Bubble by ionforce on Friday January 29, 2016 @01:20PM (#10997198)
How does a guy like that become senior? As a senior one should know that there is a pragmatic balance lost in trying to aim for perfection.
Re:San Francisco Bubble by IndianAstronaut on Friday January 29, 2016 @01:30PM (#10997306)
He has his strengths. He produces exceptional quality code (albeit a bit on the spaghetti side) and is good at finding problems in code. He is also 63 and has decades of experience.
Re:San Francisco Bubble by restalis on Friday January 29, 2016 @02:23PM (#10997769)
It's a challenge for me to imagine "exceptional quality code" with "albeit a bit on the spaghetti side". Can you elaborate?
Re:San Francisco Bubble by IndianAstronaut on Friday January 29, 2016 @04:46PM (#10998741)
It covers a lot of corner cases, it is fast, it is robust, and produces good quality data. Only thing is it is hard to navigate.
Re:San Francisco Bubble by superplussed on Friday January 29, 2016 @06:22PM (#10999345)
These developer descriptions sound like they are coming from the "Silicon Valley" tv show.
Re:San Francisco Bubble by Shorel on Friday January 29, 2016 @06:32PM (#10999406)
He can use goto :)
Re:San Francisco Bubble by gearoidoc on Friday January 29, 2016 @04:25PM (#10998616)
"exceptional quality code (albeit a bit on the spaghetti side)" is an oxymoron.