- Feature Articles
- CodeSOD
- Error'd
-
Forums
-
Other Articles
- Random Article
- 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
Thanks for that succinct translation of the word "leverage" from management-speak to plain English.
Admin
O_O
Admin
Honestly, I got lost...
that just sounds insane.
I mean fuck, if I HAD to work there (like for whatever reason I was inprisoned in that job), I would buy my own pile of consumer used computers and just setup test machines out of them out of my own pocket.
Just to save my sanity.
Sure, it'd run slow as hell. And sure, it may not perfectly emulate the production environment.
But at least I wouldn't be doing THAT.
Admin
this made me physically ill. 10/10
Admin
Dear DailyWTF,
Stop trying to make "developmestuction" happen. It is a terrible, awkward, Cronenberg-esque abomination of a word, and you need to just forget that it ever happened.
Admin
I misread it as "developmentruation" at first and was very confused for a few seconds.
Admin
Seems cromulent to me.
Admin
Agreed. The try-hard cringmanteau detracted from the realhorrorstory that followed.
Admin
tell that to management
Admin
Dunno about that.. "developmestuction" looks like a perfectly cromulent word to me, and use of it will leave everything copasthetic.
Next you're going to complain about the not-quite-official meaning of the word "Santorum" ?
Admin
Development 'round the world!
Admin
Why test? If you decide to let users access functionality in testing, they might as well test it on the go. You only need to detect when something fails and preferably how it fails. Developers tend to miss a lot of testcases anyway. Undoing your changes will also be easier because there will be no test transactions.
Admin
(spam)
Admin
Admin
.
'_.-( 9``````````P )--...).((|| __ ||))( ) |<````---__|| ( )||) ,xx xx. //)__--,/ OO//,'_ )--,/ ,, // |// / (( // ( (._ _,) (_) -OH YEAH! \ \````/ / \ ^--^ / \_ _____ __/ | | | | ( ) ( ) ,--'~'\ /'~'--, (_______) (_______) _ __ ___ ___ _ ___ _ ___ | / /| . || . || | ___ | . || || . \ | \ | | || | || |_|___|| || || | | |_\_\'`'|| ||||||/ __ __ ___ _ _ _ | \ | . || \ || | | || || ||/ ||||||||_|<_>Admin
/XXXXXXXXXXXXXXXXX. *XXXXXXXXXXXXXXXXXXXXXXXXI (XXXXXXXXXXXXXXXXXX /XXXXXXXXXXXXF*YXXXXXF- HXXXXXXXXXXXXXXXXXXX XXXXXXXXXXXT XXL VXXXXXXXXXXXXXXXXXXXX) /XXXXXXXXXXXX MMMM VXL VXXXXXXXXXXXXXXXXXXX/ JXXXXXXXXXXXX X Y YXL IXXXXXXXXXXXXXXXXXXXXXXXXXXX--XXX VXL (XXXXXXXXXXXXXXXXXXXXXXXF * VXL (XXXXXXXXXXXXXXXXXXXXX NM $$$ VXX (XXXXXXXXXXXXXXXXXXX Y $ $$ XXL TXXXXXXXXXXXX/AXXXY 7 $$ R $ )XI -XXXXXXXXXX/ XXXXI $ $$ $ $ YXX XXXXX XXXX( $ $ $ ,$ IXX TXXXX $ $ $.$$$$ /XX) XXXXX $ $$$ $$$ XYTTX=-. XXXX( $$$$$$$ XXXX-, / X XXXXL $$$ XX .,. Y X XXXXL XX XXXXX XXX ) XXXXL,. XX XXXXXX X X I XY XXXX X / X X X X X X X X X Y XX. X X ( X X. .*V .X I TX=XXXXXXXX=XXX X X XX TL. T )XV X X XX X. X/ XX XX XX. .X X TXXXXXX,( TT X XX X XXX XX XXX XXXX XXXX
Admin
(spam)
Admin
(spam)
Admin
(spam)
Admin
(spam)
Admin
Please someone shoot blakeyrat
Admin
HELP! RAPE!
Admin
You mean "side EFFECT". The "side affect" would be the displayed emotional state of the developers (presumably depressed).
Admin
Rule #1 of Java development: Don't abuse the classloader
Admin
... or it may spit in your exe file.
Admin
I don't like the word "developmestuction". I always read as "develop-me-estuction", so I'm always thinking "Do you want to be developed as an 'estuction' environment?"
And also, I wouldn't be surprised if they disable guest comments after Blakeyrat's spam. Or worse, Discourse returns.
Admin
Finally, another great article from Snoofle, and half of the comments are from blakey who's throwing a tantrum? That's kinda sad.
Admin
We're not even sure if this is the real blakey or someone who decided to be as annoying as him. I think it might be the latter... he's bound to have pissed dozens of guys so far. One of them might have too much time on their hands.
Either way, that was a nightmarish environment and I just feel glad that even with all the wrong things that happen where I work it's far better than the article's environment.
Admin
This reminds me of an environment I had to work in for about 6 months. (while being forced to commute an hour farther than my normal, because they refused to replicate the environment in the office I was hired to work at...) While, thankfully, it didn't cause anything to deploy to production, it was still a nightmare. Basically: in a single environment where a large number of developers are all working in parallel, there was a single actual deployment of the codebase... globally shared between all the developers. Anytime anybody made a patch to their code, it would affect every single other developer. There were no local deployments to each box. On top of that, in order to build anything, every developer had to SSH into the same (shared) box and run their build there. If I were to build the code I was working on (and it wasn't a short build even!) it would basically choke the entire box for everyone else, and vise versa. Actually making a build could take anywhere from a couple minutes to 30+, depending on who was using it at any given time. There were all sorts of fun times where I would have something working, tell my boss to show them it was working, and have it be completely broken by the time they got there because someone else somewhere made a change that broke the provider of the data I was using. The fun part was that no matter whose fault it was, I always got the blame for something not working because my stuff was visible, even if my code hadn't changed and it had been rock solid for a while. And all that was on top of working in what was essentially a server room, with a desk just wide enough to hold a keyboard and mouse, almost literally should to shoulder with other developers. And that was if I even got a desk due to them all being shared between all the other developers trying to test/build things. And that doesn't even get into how things were configured. (I once broke a huge number of applications by adding a single line to the config file where the beginning of a key was the same as an entire other key, even though the key itself was unique. and the config file wasn't even locked down!)
Oh and this was a huge company that everybody probably knows about.
I still shudder when thinking about working there.
Admin
This is the kind of stuff that would have been solved not by buying a bunch of servers, but by buying a big one that hosts virtual machines. As many environments as you want, as long as you're not using them all at once.
Admin
I have had to do something a bit like this but that many releases is extreme.
Admin
The problem with this phrase is only the ambiguity with "Developmestruction" -- work environments of mass destruction. Yet, somehow that term also applies to snoofle's little shop o' horrors.
A better term might be "Developtestduction", or "Developtestageduction", depending upon how much work is overloaded onto one set of servers.
The real eyebrow-raiser is how the customer puts up with flaky behavior and regulatory violations, but still won't cough up the protection money.
Addendum 2016-06-07 20:25: Probably the customer puts up with it for the same reason we won't use NodeBB for the comments.
Admin
An ugly word for an ugly situation.
Admin
Sounds like your entire system could be broken with a version change performed by some jive turkey who means well but has no idea what he's messing with.
Admin
Yerp!
Admin
Yerp!
Admin
Inquiring minds want to know:
Does the editor realize that the image selected to illustrate this article is not just any patchwork, but a specific style known formally as -- wait for it -- a crazy quilt? (Probably yes, since the alt text includes the technical term along with a partial definition, but it's still a happy detail.)
Admin
I've come into a development environment like that. I changed it, found a way to deploy it locally, then improved the deployment process. Migrated it to maven, after the maven specialist brought in said it couldn't be done after two days and left. Implemented CI. Then I suggested a change that would improve performance. It was turned down by business, because we already had a cache mechanism that would cache all pages overnight. I implemented it in my spare time and showed management it reduced page load times from 58 seconds avg to 1.2 seconds avg. They gave the go. Then I had clout, and me and some colleagues went on to turn this project into a giant win. Even after a mandatory switch from SVN to ClearCase. After the project was a full success, we were in charge of implementing phase 2, while in parallel, the freelancer that broke the first project was given the go ahead to redevelop the application in a much newer, better technology. Then they replaced our team leader with a corporate nepotist asshole and I left. In short order, all the other devs on my side left, the last one getting fired after a physical altercation with that manager.
I wish I could say I left for greener pastures.