ThomaszKrueger

12 ms·

61.
by ThomaszKrueger 11y ago
For a Civil Engineer to build a bridge that collapses, he has to be licensed and will be liable because there are standards to follow (strength of materials, calculus, etc). No such thing exists for software.
62.
by ThomaszKrueger 11y ago
That seems to be the exception. Practically everywhere you look it is like someone else pointed out "mf* programming".
63.
by ThomaszKrueger 11y ago
Software Engineering is an oxymoron. If it weren't, professionals in the field would be held accountable when projects go belly up, and they would be required to be licensed to practice. Since there is no real understanding of what tha
64.
by ThomaszKrueger 12y ago
As a target process user, I have to agree with the assessment that Enterprise Software has no taste.
65.
by ThomaszKrueger 12y ago
A lot depends on who you are programming for . Usually it is for a company that places more importance on a deadline than anything else, including quality. Other "ilities" are even less relevant. So you just hunker down, and prod
66.
by ThomaszKrueger 12y ago
I usually give "them" a shocker estimate, and my rationale is pretty simple - unknowns. And for the most part my estimates are usually right. If asked to trim it, I simply state that OK, I'll deliver what may not be the right
67.
by ThomaszKrueger 12y ago
Yes, you are. Don't be fooled by companies with hiring processes that basically say "dance for me, monkey". They have their own agenda; just because you don't look like the programmers they would hire it doesn't mea
68.
by ThomaszKrueger 12y ago
How do you account for the hours you spend "communicating", and will there be hours left for real work?
69.
by ThomaszKrueger 12y ago
As many here said, immediately and honestly. Next time make sure you either have enough information to base your estimate off, or way-way-way over-estimate. Stick to your guns. If you finish early, fudge - make the estimate. This way you ac
70.
by ThomaszKrueger 12y ago
It seems to me that in your case the relevant part is engineering, the standards are the real thing and programming is there to support them. This is not the case in my experience, where programming involves creating a new web site, a new d
71.
by ThomaszKrueger 12y ago
I'm 53 with an EE degree, went to programming because it so happened that there was a telecommunications research center close by the school. And programming looked cooler and easier than EE. I compare programming to writing, more than
72.
by ThomaszKrueger 12y ago
I work in such open office arrangement. The worse is when the two guys across your desk have their phones on a conference call on speaker phone and the echo of both come through as they speak, utterly distracting, I might as well just pack