My first job was actually nontechnical - I was 18 years old and sold premium office furniture for a small store in Munich.
I did code in my free time though (PHP/JS mostly, had a litte browsergame back then - those were the days), so when my boss approached me and asked me whether I liked to take over a coding project, I agreed to the idea.

Little did I know at the time: I was supposed to work with a web agency the boss had contracted to build their online shop. Only that he had no plan or anything, he basically told them "build me an online shop like abc(a major competitor of ours at the time)"

He employed another sales lady who was supposed to manage the shop (that didn't exist yet). In the end, I think 80% of her job was to keep me from killing my boss.

As you can imagine, with this huuuuge amout of planning and these exact visions of what was supposed to be, things went south fast and far. So far that I could visit my fellow flightless birds down in the Penguin's republic of Antarctica and still need to go further.

Well... When my boss started suing the web agency, I was... ahem, asked to take over. Dumb as I was, I did - I was a PHP kid and thought that Magento, being written in PHP, would be easy to master. If you know Magento, you know that was maybe the wrongest thing I ever said.

Fast forward 3 very exhausting months, the thing was online. Not all of it worked yet, but it was online and fairly secure.

I did next to everything myself, administrating the CentOS box the shop was running on, its (own) e-mail server, the web server, all the coding required for the shop (can you spell 12 hour day for 8 hour pay?)

3 further months later, my life basically was a wreck, I dragged myself to work, the only thing I looked forward being the motorcycle ride home. The system worked though.

Mind you, I was still, at the time, working with three major customers, doing deskside support and some admin (Win Server 2008R2 at the time) - because, to quote my boss, "We could not afford a full time developer and we don't need one".

I think i stopped coding in my free time, the one hobby I used to love more than anything on the world, somewhere Decemerish 2012. I dropped out of the open source projects I was in, quit working on my browser game and let everything slide.

I didn't even care to renew the domains and servers for it, I just let it die without notice.

The little free time I had, I spent playing video games and getting drunk/high.

December 2013, 1.5 years on the job, I reached my breaking point and just left, called in sick at least a week per month because I just could not see this fucking place anymore.

I looked for another job outside of ALL of what I did before. No more Magento, no more sales, no more PHP. I didn't have to look for long, despite what I thought of my skills.

In February 2014, I told my boss that I quit. It was still seven months until my new job started, but I wanted him to know early so we could migrate and find a replacement.

The search for said replacement started in June 2014. I had considerably less work in the months before, looks like he got the hint.

In August 2014, my replacement arrived and I got him started.

I found a job, which I am still in, and still happy about after almost half a decade, at a local, medium sized ISP as a software dev and IT security guy. Got a proper training with a certificate and everything now.

My replacement lasted two months, he was external and never really did his job - the site, which until I had quit, had a total of 3 days downtime for 3 YEARS (they were the hoster's fault, not mine), was down for an entire month and he could not even tell why.

HIS followup was kicked after taking two weeks to familiarize himself with the project. Well, I think that two weeks is not even barely enough to familiarize yourself with nearly three years of work, but my boss gave him two days.

In 2016, the shop was replaced with another one. Different shop system, different OS, different CI. I don't know why and I can't say I give a damn.

Almost all the people that worked at the company back with me have left for greener pastures, taking their customers (and revenue) with them.

As for my boss' comments, instructions and lines: THAT might not be safe for work. Or kids. Or humans in general. And there wouldn't be much left if you put it through a language filter...

Moral of the story: No, it's not a bad thing to leave a place if you're mistreated there. Don't mistake loyalty with stupidity!

And, to quote one of my favourite Bands: "Nothing matters when the pain is all but gone" (Tragedy + Time by Rise Against).

Maybe it's old and well known, but somebody asked, so here it goes:

A shepherd is quietly grazing his sheep on the fresh village pastures.

Suddenly a shiny new car stops by. A cool guy, very well dressed hops out and asks him: "Good man, If I guess exactly how many sheep you have, can I win one?"

The shepherd, puzzled, accepts.

The cool guy, opens his laptop, download a satellite picture of the area, run a NASA algorithm for image recognition and in few seconds answers "you have 1342 sheep"

"Wooow" says the shepherd "you won, take one"

The cool guy is about to live when the shepherd approaches him:

"Ehi, Young man, I bet all my flock against your car that I can guess what is your job"

The cool guy, (he likes to bet after all) accepts.

"You are a consultant" says the shepherd.
"WTF! how did you even..."

"Well, easy" says the shepherd "you came out of nowhere, well dressed and smart looking, you answered a question nobody asked you, you told me something I already knew, you want to be payed for that and in addition, you don't understand shit about my business."

"Now", adds quietly the shepherd "please, give me back my dog"

(for @LOLjustCoding)

TLDR So according to our managers, our company is not dead yet, but very close to the edge. And there's nothing I can do about it.

Basically, they are asking the software devs to twirl our thumbs while we wait for other departments to pull us out of the dirt. Meanwhile, those people who can actually do something to get everyone back on track are running for the hills, looking for greener pastures (you know, sinking ship, turns out rats can swim).

I was told that I shouldn't leave as I am a 'vital part of the team whatever and so on'. But that is difficult to believe when I'm looking at 2 years minimum, in which nothing I will develop or have worked on in the past will make any difference. Whether I keep my job is determined by people who love numbers and have little concern for me as a person (not that this is new, but at least I was contributing before).

Guess I will be spending all that extra time at work reading and programming personal projects, since aside from no new projects, there will be no budget for taking courses that were promised before. Oh, and polishing my resume so I'll be ready when this ship finally goes down.

I'm an idealist. I'm an optimist.
So of course I get enormously stressed out and depressed when the world just keeps fucking me over.

I have been at my current job for 2.5+ years. Been on the same project for the past 2+. And I am now on my 4th manager (not including the guy who hired me and got fired before I started).

It's just been one thing after the other. So many problems on this project with only one other dev on it until recently. Management has been avoiding taking proper actions.

I have done as much as I can and it has been a burden on my health. Last year I got passed over for a pay raise because of a bad manager, who since left for greener pastures. This year I got a small pay raise (below inflation) and a surprise bonus of such minuscule proportions that it's fucking laughable. I am being grossly underpaid for the weight that I'm pulling.

We just had a reorg that actually is a huge step in the right direction, and my new manager seems to actually want to give the project some proper attention.
So I asked him for a talk about my title and salary, so we can set things right.

We have now had two talks in a little over a week, in which he has emphatically stated over and over again how he just doesn't have the information or the power to give me anything at all.

And the thing is. I don't want to find another job. Of course I could easily do so, and for a lot more money too. But the problem is, I'm an idealist. I actually believe that what I'm working on, and what I will be working on in the future, at this place, is really important.

I should just get the hell out, as many of my colleagues have. It's actually quite incredible how many people have left my team over the past 6 months.

But I'm an optimist. I cannot see how management can possibly continue on this path without realising the consequences and taking action.

So now I've scheduled a meeting with the CEO to give him my two cents. I've done it before, which may actually have played a part in putting the reorg in motion.

I have to believe I can appeal to reason.
Otherwise, what's the point of anything?

I know. I'm the fucking clown meme.

Peace out.

Good code is a lie imho.

When you see a project as code, there are 3 variables in most cases:

- time
- people / human resources
- rules

Every variable plays a certain role in how the code (project) evolves.

Time - two different forms: when certain parts of code are either changed in a high frequency or a very low frequency, it's a bad omen.

Too high - somehow this area seems to be relentless. Be it features, regressions or bugs - it takes usually in larger code bases 3 - 4 weeks till all code pathes were triggered.

Too low - it can be a good sign. But it should be on the radar imho. Code that never changes should be reviewed at an - depending on size of codebase - max. yearly audit. Git / VCS is very helpful here.
Why? Mostly because the chances are very high that the code was once written for a completely different requirement set. Hence the audit - check if this code still is doing the right job or if you have a ticking time bomb that needs to be defused.

People
If a project has only person working on it, it most certainly isn't verified by another person. Meaning that only one person worked on it - I'd say it's pretty bad to bad, as no discussion / review / verification was done. The author did the best he / she could do, but maybe another person would have had an better idea?

Too many people working on one thing is only bad when there are no rules ;)

Rules. There are two different kind of rules.

Styling / Organisation / Dokumentation - everything that has not much to do with coding itself. These should be enforced at a certain point, otherwise the code will become a hot glued mess noone wants to work on.

Coding itself. This is a very critical thing.

Do: Forbid things that are known to be problematic in the programming language itself. Eg. usage of variables in variables, reflection, deprecated features.

Do: Define a feature set for each language. Feature set not meaning every feature you want to use! Rather a fixed minimum version every developer must use and - in case of library / module / plugin support - which additional extras are supported.

Every extra costs. Most developers don't want to realize this... And a code base that evolves over time should have minimal dependencies. Every new version of an extra can have bugs, breakages, incompabilties and so on.

Don't: don't specify a way of coding. Most coding guidelines are horrific copy pastures from some books some smart people wrote who have no fucking clue what you're doing and why.

If you don't know how to operate on people, standing in an OR and doing what a book told you to do would end in dead person pretty sure. Same for code.

Learn from mistakes and experience, respect knowledge from other persons, but always reflect on wether this makes sense at this specific area of code.

There are very few things which are applicable to a large codebase on a global level. Even DRY / SOLID and what ever you can come up with can be at a certain point completely wrong.

Good code is a lie - because it can only exist at a certain point of time.

A codebase should be a living thing - when certain parts rot, other parts will be affected too.

The reason for the length of the comment was to give some hints on what my principles are that code stays in an "okayish" state, but good is a very rare state