- Feature Articles
- CodeSOD
- Error'd
- Forums
-
Other Articles
- Random Article
- Other Series
- Alex's Soapbox
- Announcements
- Best of…
- Best of Email
- Best of the Sidebar
- Bring Your Own Code
- Coded Smorgasbord
- Mandatory Fun Day
- Off Topic
- Representative Line
- News Roundup
- Editor's Soapbox
- Software on the Rocks
- Souvenir Potpourri
- Sponsor Post
- Tales from the Interview
- The Daily WTF: Live
- Virtudyne
Admin
Admin
1.) "Having to wear a suit" and "great workplace" - isn't that mutually exclusive (at least in our business) ? Correct me if I am wrong.
2.) If you are at work wearing clothes you do not like it is not such a great workplace after all ...
Admin
Yeah, it about writing your prof's research pubs and books, slaving away as a grad student, learning to write (hopefully winning) grant posposals as a PhD and publishing first. It involves buckling down to people higher in the hierarchy and kicking anybody lower in the heirarchy.
Admin
Whilst this article shows us how a 'programmer's first foray into a paid peice of work snowballs into a nightmare - its really an illustration of poor requirements analysis more than anything else.
There is NO WAY that an application whose purpose in life is to generate flyers can end up with thousands of controls and drop down lists covered by dozens of tabs.
Without even looking at the specs, I would be willing to bet that if you sat down with the customer, and analysed the requirements in a sane manner, then you would agree that a simple interface, and a simple short stint of development would satisfy the customers actual NEEDS 100%.
Most 'new programmers' tend to ignore the customer's needs, and drive the development in such a way that it gives them reason and scope to try out ideas that they want to gain experience in.
Guiseppe needs to be placed into a jar of isopropyl alcohol, and donated to medical science.
Admin
tiffany