Forgot your password?

typodupeerror

Comment: It's really quite simple (Score 1) 446

by Plammox (#38888853) Attached to: Ask Slashdot: Transitioning From 'Hacker' To 'Engineer'?
1. Understand the users and businesses who are going to use your product, and what they need from you to be successful. (And create a minimum no. of support requests later on). Spend actaul time doing it. No, really!
2. Understand that testing is needed to uncover all flaws in your program. Learn to appreciate the good testers, who do anything to break your code. Again, it will help minimize the shit storm, when you release (flawed) code to production.
3. *Then*, you can start honing your hacker skills, selecting the algorithm that will squeeze out the last 2% real world speed increase.

The most successful engineers I have met as a project mgr/product owner master the 3 above.

Comment: Re:Furniture (Score 1) 312

by Plammox (#38445872) Attached to: Smallest space my belongings could fit (unbroken):
Confirmed. This is partly due to the fact that they often try to use newer technology than comparable brands (example: Renault had electronic handbrakes before VW, Toyota, etc. ) and partly because they always try to differentiate their design. Mostly Citroën....with adverse effects on quality, sometimes, but they also have some good original ideas. Like their hydropneumatic suspension, which allegedly ensures configurable hardness, easy servicing, a smooth ride and good handling in curves. Don't [always] underestimate French engineering. PS: IANF

The magic of our first love is our ignorance that it can ever end. -- Benjamin Disraeli

Working...