- 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
Too late: http://en.wikipedia.org/wiki/The_Prisoner
Admin
Sure, blame it on Nixon. But he did open up China.
Admin
Wait a goddamned second here. Why bother with multiple databases and tables? Just throw it all in one big table and let the application code figure it out from the primary key?
That trick always works, Bullwinkle.
Admin
This needs to be a featured comment. Big time.
Admin
The One True Lookup Table
The article surely can't describe an open source project. I came up with a remotely similar concept in my blog the other day, and was suitably castigated.
Admin
Comment57
Word1 Word2 Word3 Word4 Word5. Phrase1; Word6 Word7 Word8. Invective1!
Admin
Woo! Go fighting 29s!
Admin
If it happened on a wooden table with the Irish girl, I wouldn't mind faxing some pictures to your FTP site. Unless of course it is an embedded system, in which case it doesn't have a file system. Then I'd have to recruit little Bobby Tables.
captcha: secundum - it would take at least two!
Admin
So this guy couldn't be bothered to find out the specifics about his stock options (which are apparently somewhat important to him) during the interview process?
Was this the conversation: "There will be stock options.", "Sign me up!" And he wants to critique how others do things?
Why do I get the feeling that a lot of these stories are whitewashed quite extensively in favor of the submitter?
Admin
It is very important for the candidate(as well) to understand how sort of company he is "actually" interview at. Well companies would go to the extent that they would ask candidate to write the code. But what if candidate ask company to see their existing software development standards? coding practices? their release management system? their actual working process?!
Admin
As someone who has interviewed candidates, one of the biggest questions I always toss out is: "Do you have any questions for me?" If they don't have any good questions, I chuck 'em down a few pegs. Either they're not really interested, or they're not really qualified.
//Conversely, I bring a list of questions to an interview.
Admin
I say we tell them the planet is doomed and send them off in a spaceship to colonize another planet.
Admin
I don't normally mod funny posts up, but you make a good point, hilariously.
Now, where's the Mod Up button..... d'Oh!
Admin
so do I, but the good interviewers cover that during the course of the interview.
Admin
That doesn't always work because the biggest question a developer should ask a potential company is "Can I see a sample of your source code" so you can see if the code looks like the shit on this site, and no company will ever let you do that (but they'll ask to see samples of YOUR code).
Admin
I worked in (unrevealed) industry where one of the most popular applications for that industry had a relational database in which one of the tables had the first 60 or so columns containing specific data followed by over 100 columns of (name, value) pairs (i.e., column n contained the name, and column n+1 the value). Null values weren't stored, so one row might have "PRICE" in the 80th column, and another would have it in the 90th column.
I had to write an in-house application to access the data; the only nice thing was that with Perl, I could access a row and then assign all those variable columns at the end to a hash with one statement.
Admin
But if we do that, we'll all end up dying from a virus from an unsanitary telephone!
Admin
you sir, just made my week :D
Admin
I've started getting build, code, and test walk throughs from potential employers and found them to be about as enlightening as asking interview candidates for code and to code solutions to simple problems. Most places you'd want to work will do it, although there's variation in how deep they want to go on their special sauce.
"we believe in good test coverage" can turn into "but we don't have automation or unit tests"
"we believe in thorough documentation" can turn into "Fred actually does it, but the rest of the team is going to be up a creek in a few years"
Admin
What?? Not WoodenTable?
Admin
HA! Great post.
Admin
Either lay off the shit or abstain from posting after taking your medication.
Admin
I've seen quite a few crap softs in dev for two years while they would have taken six month to write properly.
Admin
Seems quite standard to me. I have worked on three different ERPs and they all had a bunch of "non standard fields" on each tables so that when you see NonStandardField5 its meaning depends on each customer.
Admin
Admin
I saw the unicorn and rainbow images too. Could there be a problem with the ads on this site injecting js into the webpage? The images were of various sparkley unicorn and rainbow cartoons that appeard anywhere within the web-page, and kind of multiplied when you clicked on them. One of the images had graphicsarcade.com written on it.
A page refresh cleared them and I havn't seen them so far since then.
Admin
Admin
Admin
Happens all the time, Dunning-Kruger effect + dishonesty. I had quite similar experience myself recently - with a plainly stupid dude who thinks he's a total hotshot, super negotiator, and who knows what else, on basis of a single not yet concluded deal that he ever negotiated in his whole life.
Admin
Please sign any code you write so I can leave immediately when I see it.
Admin
Admin
I've actually seen a package that looks exactly like this. It was called "Customer/1" and sold by Accenture (then Andersen's) and all the developers had data dictionaries printed out on 132 column fan-fold.
"What's Column3 for again?""
Admin
TRWTF: Greg bought the promises of the startup.
Admin
Check in the table-and-column meta-database Table5 Column219.
Admin
I'm just pedantic, not smart.
Admin
Admin
This kind of things would be almost funny if it wasn't the ugly truth... The only single thing you must actually do is to run away or if you can't (and believe me sometimes you just can't) is to laugh alone like a mad man. Pretty sad...
But it can be even sadder if you've got the silly idea to try to make things right... Actually, it could be the only thing you could possibly do if you are disignated as the "alpha guy in the pack" from the start. Tooo baaaad buuudyy!
Happy coding, we love our job and long life to the king.
Admin
Humans are primates, not canids, so the pack/arse-sniffing metaphor is inaccurate.
Admin
Absolutely agree. Pro-tip for interviewees; the wrong answer to that question is "no". It's shocking how many people don't seem to get that.
Admin
Okay, how about this then:
Admin
I actually worked at a place where some of the major organs of the system were written by my supervisor. According to him, his sycophants and inept management, it was a visionary SOA-like thing. The underlying database was a monstrosity (just as in this story), and the Java code was the uber-generic solution to SOA...
... with services that handled from simple things like querying a database in the same subnet to inane little things like string concatenation and date calculation, the whole abomination redundantly implemented with layers upon layers of marshallers and unmarshallers that converted unstructured data dumbs with xml tags into unstructured typeless hash maps.
Oh, and it was important to keep the hash maps unstructured and untyped.
And that was because domain models in general, and pojos in particular were bad. They had a bad experience doing domain modeling and concluded that this abominable, gelatinous mass of untyped unstructured xml-to-hashmap turds was a better engineering fit for their business model (that is, they f* sucked at domain modeling and basic soft. engineering principles, decided to go with his massive example of what-not-to-do and proudly claimed they were revolutionizing SOA.)
And when people weren't able to maintain or work with that crap, management would declare them incompetent (literally and publicly) for not being able to work with their brilliant piece of stupidity... err... engineering.
Oh man, that brought some horrible flash backs. Anyways, crap like the one described in the story (CEO/manager dropping a turd and declaring it a brilliant piece of engineering) is not that uncommon.
Admin
Sometimes I think to myself that WTF and the comumnity in general is the only link that keeps people away from insanity...
Humor will save us all !!!
Admin
It is called retinoblastoma.
Admin
""It's very important to me that we have a generic, object oriented approach," the CEO explained"
So, everyone in the company got the same wages and benefits?? Because that would be generic and object oriented.
Sounds something like the failed analogy our director brings up when attempting to promote universal skill sets here - he calls it the "Swiss cheese approach" (don't ask me to explain it..). We like to counter with "so, full of holes, then?" or "so, we all get the same wage - like your wage, for example?".
Ahh, management.. what fun.
Admin
Admin
Captcha: iusto - there ain't no justice.
Admin
Then Competition399 will be... Adjective42, to say the least.
Admin
Wrong, just store everything as strings! No worries about fixed or float or integers, and anything can be stored anywhere! You lack vision...
Admin
So stand still, and we'll throw shit at you.
Admin
I'm wondering... if I had to work there and didn't have the choice of leaving (say, for example, I moved to the damn city for the job and had a family to support... which I've done) then how could I live with this?
I suppose the first thing I'd do is treat it like a maze of twisty little passages, all the same (or all different): I'd make a map. First on paper, then eventually in code with a preprocessor to convert my real code into the CEO's gibberish.
In a couple of months I would do all my coding in my "higher level" language.