meta user
network profile
| bio | website | |
|---|---|---|
| location | Munich, Germany | |
| age | 35 | |
| visits | member for | 2 years, 3 months |
| seen | Apr 14 at 21:30 | |
| stats | profile views | 206 |
I work at a small mechanical engineering company, where I develop software and image processing algorithms for camera-based inspection machines.
|
Feb 18 |
awarded | Caucus |
|
Feb 6 |
awarded | Necromancer |
|
Jan 24 |
awarded | Yearling |
|
Jan 21 |
awarded | Notable Question |
|
Jan 8 |
awarded | Announcer |
|
Sep 21 |
awarded | Custodian |
|
Sep 14 |
comment |
Is there a constant for “end of time”? I think the Mayan calender has an "end of time" constant = 2012-12-21 ;-) |
|
Sep 14 |
revised |
Programming languages with a Lisp-like syntax extension mechanism Replaced the potentially copyrighted sample with one from the Boo test cases |
|
Sep 14 |
revised |
Programming languages with a Lisp-like syntax extension mechanism added 2057 characters in body |
|
Sep 13 |
revised |
Programming languages with a Lisp-like syntax extension mechanism added 166 characters in body |
|
Sep 13 |
answered | Programming languages with a Lisp-like syntax extension mechanism |
|
Sep 10 |
comment |
Is catching general exceptions really a bad thing? You could throw away cached data in case of an OutOfMemoryException, then try again. That might make the situation better. Or, for a desktop application, you might save as much of the user's data as possible to a temporary file and try to restore it on restart. |
|
Sep 8 |
comment |
Does *every* project benefit from written specifications? @JBKing: Apparently, people mean different things when they say "spec". At the places I've worked, "requirements" contain the "what" and "specifications" contain the "how". Including sentences like "when button X has the focus and the the user presses Tab, button Y gets the focus". |
|
Sep 7 |
revised |
Does *every* project benefit from written specifications? added 373 characters in body |
|
Sep 7 |
comment |
Does *every* project benefit from written specifications? @Ramhound: I wonder if you have ever worked on vertical-market software? If that 50-million dollar contract comes around, and the software we deliver doesn't solve his problem the customer doesn't care what the spec says. He will haunt you anyway. So if that's really the only advantage of having specs you see, then there really is no advantage for my kind of work. |
|
Sep 7 |
comment |
Does *every* project benefit from written specifications? @whatsisname: That's what I suspect. But specs are one of the 12 commandments in the Joel test, and a lot of people here on PSE treat them with almost religious enthusiasm, so I was wandering... |
|
Sep 7 |
comment |
Does *every* project benefit from written specifications? And: Of course we do planning. We write documents that describe new features and discuss them internally and with customers. We do all the things you say. We just don't produce full written specs on the way. |
|
Sep 7 |
comment |
Does *every* project benefit from written specifications? Obviously the developers do talk to the customers. How else would they get domain knowledge? What would be the use of dummy screens if you didn't ask the customers questions about them? But the point is: Our customers won't read a 100 page full behaviour specification. |
|
Sep 7 |
comment |
Does *every* project benefit from written specifications? @Ramhound: I've been a professional developer for 15 years, working for six different small and large companies. |
|
Sep 7 |
asked | Does *every* project benefit from written specifications? |
