|
Giving the code I've had to work with that's insulting to beaver dams and ant hills!
Even spaghetti doesn't start to describe it.
It's like, if an ant colony went to make an ant hill on a beaver dam and you had earphones made of spaghetti, that you kept in your bag for a year, so it's TUBAR (Tangled Up Beyond All Repair), and threw that in the ant hill on the beaver dam... Then maybe you get the slightest idea of the crap I've had to deal with
|
|
|
|
|
'By the way... you have to use our new enterprise grade product lifecycle management tools to do configuration management...'
No thanks - Git and Redmine'll do me, thank you very much...
'No, you HAVE to...'
But it'll slow things down SO much - why?!
'Because corporate...'
Yeah, people imposing stupid, damaging tools and processes 'because that's the way we do things...'
Java, Basic, who cares - it's all a bunch of tree-hugging hippy cr*p
|
|
|
|
|
There is nothing scary for a developer who have at-least 4-5 yr exp., I think.
Development is always challenging task & after few year exp., anybody can face any issue... !
|
|
|
|
|
Hemant Singh Rautela wrote: There is nothing scary for a developer who have at-least 4-5 yr exp You wouldn't say that if you had at least 4-5 years of experience!
|
|
|
|
|
It's just my perception. As I think First 2 year is just learning period & next 2 year exp.
|
|
|
|
|
Trust me, even the most seasoned developer gets a good scare when he opens some SQL procedure with over 5000 lines of code (yes, they exist)
Also, as a developer we're never done learning.
I know a lot of "experienced" developers who get scared by new technology.
They never kept up and their knowledge is obsolete, any new technology will make that painfully clear
By that sentiment I'd like to point out that "years working in the field" != "experience".
When you do the same thing over and over you don't get more experienced.
Actually, I'd like to argue that the more experience you have the scarier it gets.
Do you remember the first time you had to refactor something?
Maybe you were young, arrogant, and full of spirit, that refactor wouldn't get you down!
And then the refactor DID get you down.
Your next refactor does the same.
And the third time is no different.
Hell, you'll be scared the fourth time you need to do a refactor because experience taught you this will end in tears
|
|
|
|
|
Sander Rossel wrote: ..when he opens some SQL procedure with over 5000 lines of code (yes, they exist)..
Yet again, you've got me looking around the office looking around for you.. I swear we must be at the same company!
I came into this game for the action, the excitement. Go anywhere, travel light, get in, get out, wherever there's trouble, a man alone. Now they got the whole country sectioned off, you can't make a move without a form.
modified 31-Aug-21 21:01pm.
|
|
|
|
|
Do a funny dance on your desk, that way I'll recognize you!
|
|
|
|
|
That's why I write my subject heading to "Nothing Or Everything".
If after working few years you didn't learn how to face scary situation's without scared, Everything would be scary always.
Because using past exp. we can learn only one thing how to learn (how to face), that's it.
|
|
|
|
|
Nah, we just pretend to be unimpressed by anything, just to spook the youngsters.
The language is JavaScript. that of Mordor, which I will not utter here
This is Javascript. If you put big wheels and a racing stripe on a golf cart, it's still a f***ing golf cart.
"I don't know, extraterrestrial?"
"You mean like from space?"
"No, from Canada."
If software development were a circus, we would all be the clowns.
|
|
|
|
|
"Can you have a look at that bug in our legacy software that no one really knows how to use and whose original developers left the company long ago...?"
Sure I can, right after I spoon my eyes out!
|
|
|
|
|
Went from scaring to live horror: all developers had to move from their 2 - 4 person rooms to open plan offices, mixed with sales guys, marketing and support, "to improve the company's community".
The transcription for they just wanted to save money.
No changes to deadlines, expecting the same productivity.
Workaround: home office days and good headphones. 
|
|
|
|
|
My biggest fear is clients unrealistic estimates of what software development will cost them.
"I just want a smart phone app that will change the world. That will only cost a of couple hundred dollars wont it?"
|
|
|
|
|
But I was not given a widescreen monitor to develop and test.
modified 1-Nov-16 23:14pm.
|
|
|
|
|
Run the app on a remote system. mstsc.exe will accept practically any weird resolution you throw at it.
|
|
|
|
|
Imagine a program like an anthill. For the last 25 years countless ants have been whipped through tight schedules. There is no docmentation and no architect. Every ant has to insticvely know what to do without any additional information and finish assignments on time. Speaking of the assignments: They are usually a handful of lines out of context that might as well read 'Do something, ant!'. Why waste time with giving the ants any details about what you want them to do?
I have worked in such a place and left because I'm not a good ant. From my observation, this anthill mentality is common in connection with Visual Basic. The anthills very often are old projects that started out with Access or VB6 and kept their good old practices for decades. When I hear something like that in an interview, the whole thing is over for me.
The language is JavaScript. that of Mordor, which I will not utter here
This is Javascript. If you put big wheels and a racing stripe on a golf cart, it's still a f***ing golf cart.
"I don't know, extraterrestrial?"
"You mean like from space?"
"No, from Canada."
If software development were a circus, we would all be the clowns.
|
|
|
|
|
I've worked in one such place in the past, and it's not a nice experience. Workplaces like that are so common that it's a scary thought. You don't realize what's going on until you're being whipped around, "doing something" there. If only there was a way for us to know if the place is an anthill before we could accept their offer.
|
|
|
|
|
CDP1802 wrote: When I hear something like that in an interview, the whole thing is over for me. Whereas my most lucrative contracts in the 90s were these. Power user builds a pile of spaghetti in access, does the job, sort of. The boss decides to extend it to a full on production system with multiuser access and get a professional in, me.
I instantly trot out ms own words that access is s single use tool and scream rewrite.
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
Every new version of Windows is worse than the previous one. The horrors that await us in Windows 11 are so bad that they defy imagination.
|
|
|
|
|
|
It's not so much of a fear as a concern, in that it slows us all down considerably. No amount of software engineering or coding standards can fully eliminate this problem.
|
|
|
|
|
Remotely programming my toaster and coffee machine so that my toast
is ready at the same time as my coffee because the two devices don't
like each other.
73
|
|
|
|
|
There always, always... someone who is compelled to say something negative about other peoples work.
Not so much a fear, more of a PITA annoyance like nuisance phone calls. Time wasters.
It was broke, so I fixed it.
|
|
|
|
|
S Houghtelin wrote: There always, always... someone who is compelled to say something negative about other peoples work.
Oh god, yes - I've had review comments about my use of apostrophes in comments...
And that was working on safety critical code, where there are many, many more things to be worried about...
Java, Basic, who cares - it's all a bunch of tree-hugging hippy cr*p
|
|
|
|
|
Because the are people that are so careless about what they write that everything they do is mediocrity...
Philippe Mori
|
|
|
|