I recently joined the dark side - an agile consulting company (why and how is a long story). The first client I was assigned to was an international bank. The client wanted a web portal, that was at its core, just a massive web form for their users to perform data entry.

My company pitched and won the project even though they didn't have a single developer on their bench. The entire project team (including myself) was fast tracked through interviews and hired very rapidly so that they could staff the project (a fact I found out months later).

Although I had ~8 years of systems programming experience, my entire web development experience amounted to 12 weeks (a part time web dev course) just before I got hired.

I introduce to you, my team ...

Scrum Master. 12 years experience on paper.
Rote memorised the agile manifesto and scrum textbooks. He constantly went “We should do X instead of (practical thing) Y, because X is the agile way.” Easily pressured by the client to include ridiculous (real time chat in a form filling webpage), and sometimes near impossible features (undo at the keystroke level). He would just nag at the devs until someone mumbled ‘yes' just so that he would stfu and go away.

UX Designer. 3 years experience on paper ... as business analyst.
Zero professional experience in UX. Can’t use design tools like AI / photoshop. All he has is 10 weeks of UX bootcamp and a massive chip on his shoulder. The client wanted a web form, he designed a monstrosity that included several custom components that just HAD to be put in, because UX. When we asked for clarification the reply was a usually condescending “you guys don’t understand UX, just do <insert unhandled edge case>, this is intended."

Developer - PHD in his first job.
Invents programming puzzles to solve where there are none. The user story asked for a upload file button. He implemented a queue system that made use of custom metadata to detect file extensions, file size, and other attributes, so that he could determine which file to synchronously upload first.

Developer - Bootlicker. 5 years experience on paper.
He tried to ingratiate himself with the management from day 1. He also writes code I would fire interns and fail students for. His very first PR corrupted the database. The most recent one didn’t even compile.

Developer - Millennial fratboy with a business degree. 8 years experience on paper.
His entire knowledge of programming amounted to a single data structures class he took on Coursera. Claims that’s all he needs. His PRs was a single 4000+ line files, of which 3500+ failed the linter, had numerous bugs / console warnings / compile warnings, and implemented 60% of functionality requested in the user story. Also forget about getting his attention whenever one of the pretty secretaries walked by. He would leap out of his seat and waltz off to flirt.

Developer - Brooding loner. 6 years experience on paper.
His code works. It runs, in exponential time. Simply ignores you when you attempt to ask.

Developer - Agile fullstack developer extraordinaire. 8 years experience on paper.
Insists on doing the absolute minimum required in the user story, because more would be a waste. Does not believe in thinking ahead for edge conditions because it isn’t in the story. Every single PR is a hack around existing code. Sometimes he hacks a hack that was initially hacked by him. No one understands the components he maintains.

Developer - Team lead. 10 years of programming experience on paper.
Writes spaghetti code with if/else blocks nested 6 levels deep. When asked "how does this work ?”, the answer “I don’t know the details, but hey it works!”. Assigned as the team lead as he had the most experience on paper. Tries organise technical discussions during which he speaks absolute gibberish that either make no sense, or are complete misunderstandings of how our system actually works.

The last 2 guys are actually highly regarded by my company and are several pay grades above me. The rest were hired because my company was desperate to staff the project.

There are a 3 more guys I didn’t mention. The 4 of us literally carried the project. The codebase is ugly as hell because the others merge in each others crap. We have no unit tests, and It’s near impossible to start because of the quality of the code. But this junk works, and was deployed to production. Today is it actually hailed as a success story.

All these 3 guys have quit. 2 of them quit without a job. 1 found a new and better gig.

I’m still here because I need the money. There’s a tsunami of trash code waiting to fail in production, and I’m the only one left holding the fort.

Why am I surrounded by morons?
Why are these retards paid more than me?
Why are they so proud when all they produce is trash?
How on earth are they still hired?

And yeah, FML.

Long rant ahead.

Holy shit is this hard.

I'm not a dev, but I'm working really hard to become one. I come home from work every day at 7:00pm and study between 3 and 5 hours of coding, and finally I'm starting to make decent responsive web pages. I got excited, finally the studies are paying off and I guess I got carried away and told a "friend" about it.

"What?, But making web pages its fucking easy anybody can do web pages! I did mine with dreamwiever, is that even considered development"

And there goes my self steem holy shit..I know, I know its not development, Im not a programmer neither do I pretend to be one but holy shit.

I guess I wish some people would anderstand the amount of effort that can go into an app or web..

Tl;Dr - It started as an escape, carried on as fun, then as a way to be lazy, and finally as a way of life. Coding has defined and shaped my entire life from the age of nine.

When I was nine I was playing a game on my ZX spectrum and accidentally knocked the keyboard as I reached over to adjust my TV. Incredibly parts of it actually made a little sense to me and got my curiosity. I spent hours reading through that code, afraid to turn the Spectrum off in case I couldn't get back to it. Weeks later I got hold of a book of example code to copy out to do various things like making patterns on the screen. I was amazed by it. You told it what to do, and it did it! (don't you miss the days when coding worked like that?) I was bitten by the coding bug (excuse the pun) and I'd got it bad! I spent many late nights on that thing, escaping from a difficult home life. People (especially adults) were confusing, and in my experience unpredictable. When you did things wrong they shouted at you and threatened to take you away, or ignored you completely. Code never did that. If you did something wrong, it quietly let you know and often told you exactly what was wrong. It wasn't because of shifting expectations or a change of mood or anything like that. It was just clean logic, simple cause and effect.

I get my first computer a year later: an IBM XT that had been discarded by a company and was fitted with a key on the side to turn it on. With the impressive noise it made it really was like starting an engine. Whole most kids would have played with the games, I spent my time playing with batch scripts and writing very simple text adventures. And discovering what "format c:" does. With some abuse and threatened violence I managed to get windows running on it. Windows 2.1 I think it was.

At 12 I got a Gateway 75 running Windows 95. Over the next few years I do covered many amazing games: ROTT, Doom, Hexen, and so on. Aside from the games themselves, I was fascinated by the way computers could be linked together to play together (this was still early days for the Web and computers networked in a home was very unusual). I also got into making levels for Doom, Heretic, and years later Duke Nukem 3D (pretty sure it was heretic; all I remember is the nightmare of trying to write levels entirely by code!). I enjoyed re-scripting some of the weapons and monsters to behave differently. About this time I also got into HTML (I still call this coding, but not programming), C, and java. I had trouble with C as none of the examples and tutorial code seemed to run properly under a Windows environment. Similar for my very short stint with assembly. At some point I got a TI-83 programmable calculator and started rewriting my old batch script games on it, including one "Gangster Lord" game that had the same mechanics as a lot of the Facebook games that appeared later (do things, earn money, spend money to buy stuff to do more things). Worried about upcoming exams, I also made a number of maths helper apps, including a quadratic equation solver that gave the steps, and a fake calculator reset to smuggle them into my exams. When the day came I panicked and did a proper reset for fear of being caught.

At 18 I was convinced I was going to be a professional coder as I started a degree in Computer Science. Three months later I dropped out after a bunch of lectures teaching what input and output devices were and realising we were only going to be taught Java and no C++. I started a job on the call centre of a big company, but was frustrated with many of the boring and repetitive tasks we had to do. So I put my previous knowledge to use, and quickly learned VBA to automate tasks. It wasn't long before I ended up promoted to Business Analyst where I worked on a great team building small systems in Office, SAS, and a few other tools.

I decided to retrain in psychology, so left the job I was in and started another degree. During my work and placements my skills came in use a number of times to simplify and automate tasks. I finished my degree, then took a job as a teaching assistant while I worked out what I wanted to do next and how to pay for it. Three years later I've ended up IT technican at the school, responsible for the website, teaching a number of Computing lessons each week, and unofficial co-coordinator for Computing as a subject. I also run a team of ten year old Digital Leaders who I am training in online safety and as technical experts; I am hoping to inspire them to a future in coding. In September I'll be starting teacher training with a view to becoming a Computing specialist teacher. Oh, and I'm currently doing a course in Android Development in my free time.

And this all started with an accidental knock on the keyboard of a ZX Spectrum.

I just LMFAO(ed..?) at myself so hard.....

Messing around with all the option in the Android Emulator's "Extended Controls" window, and I was playing with the battery level slider.. got a little carried away, and suddenly my emulator just shut down.. by itself!

🤔

It took me way longer than it should've to realise what happened. But yeah, that's what Android does when your fucking battery reports 0%.

🤣🤣🤣🤦

I think I must stop working now, this day is done with me.

I stayed at work till 8:30 last night writing tests. It was awesome!

Got home and told Mom: "sorry, got carried away".

Me: I should make REST API docs
Also me:

Random story, I was working on a project a few years ago that had a very tight deadline and a lot of code to write. I had been working late in the office most evenings but one night myself and a colleague had stayed later than usual as we got carried away with supporting peripherals​ in the epos.
The cleaner came in on evenings and we had seen her that night, but had not heard anything for a while so when it came time to leave we figured we best lockup the 2 offices.

After making a quick pass through the building we couldn't see her so proceeded to lock up. Fortunately before setting the alarm we spotted her motorbike in the adjacent car park and decided to have another look.

I'm not quite sure why I decided to look in the tiny supply room/closet but fortunately I did as I found the cleaner standing in this tiny room​playing games on her phone 😂

!dev

Another tinder story from last night.

Matched with a girl, I thought she was cute and all. She texted me first, and we started talking. We kinda just clicked, had similar interests and everything. Conversation turned to musicals, she said she wanted me to come listen to one with her at some point when we were both free. I mentioned the whole story from Sunday night to her (see previous rant), and told her how the girl said I was a "rebound", but nothing actually happened. Then she changed the conversation by saying something like "rebounds normally involve sex, maybe I can make up for it".

After that the conversation got sexual. Dirty talk, nudes, everything. Talking about how hard she wanted me to fuck her and everything. That carried on until about 6 in the morning. We both decided we should go to sleep.

I woke up around 11, we talked for a few minutes, then she said she had to get ready for a doctor appointment, and I didn't think anything of it. Went to work at 2, had to go get a car from a dealership like 20 minutes away. Me and my coworker got back, I decided to check my phone and see if she messaged me or anything.

Come to find out, she basically just fucking ghosted me. Blocked me, unmatched me on tinder, the whole nine yards. No warning, nothing. 8 hours earlier she was saying how much she wanted me inside her (not paraphrasing), and now she just decided "nah fuck him altogether".

I don't fucking know what it is. It's been about 10 hours since I found out, and I just..I don't know. She could have just said "nah I don't wanna fuck" and I would have been 100% fine with that. But nope. No warning, just blocked me.

I'm not mad that she just backed out of it, I'm mad that she didn't say fucking anything about it. Like, even apart from all the sexting and stuff, I genuinely liked this girl. She was nice, cute, funny, just everything I could have asked for. And now, I'm honestly kinda sad about it. Everything seemed like it was going well (maybe all the sexting would have been better for another time in the future ya know, but I can honestly say I didn't initiate it), and now I have nothing again.

I finally got assigned to a project, working like a dog but it is for operators safety so it feels good. Also, I have been tasked with writing custom C++ plugins for our process simulators and damn it feels so good to match both my biggest interests. I hope to not get carried away by it in my evenings since I was learning some webdev in my freetime.

Also got UNIXstickers in the mail like 99% of the people here.

Oh, I also received my Seiko SKX and damn I already love it.

My first experience with a computer was when I was about 7-8 years approx. I came back from school and dad told me he got me enrolled with a teacher who lived around 5 kms away. Me and my dad walked in the warm summer afternoon (one of my most fond memories tbh), cut through a meadow that had freshly cut grass and reached his place. He lived in the third floor, and there was a stray dog that used to stay in the second. The stench was horrible, but over time I got used to it.
He opened the door and showed me how to boot up a computer, then asked me to open LOGO (it ran on MS-DOS at the time). Taught me the fd 40 rt 90 stuff and I loved it - he noticed and asked me to go to town. I started drawing on the screen and remember being delighted at how it ran what I asked it to run.
We then did some theory, and every grade I finished my syllabus in like 2-3 days. Too bad we didn't have coding until I was like 14, but that's another story and deserves another post :)

Sorry for the long post, got carried away

(Note: I got a bit carried away while writing this, so the end result is a lot longer than I expected. Apologies for the long post!)

The beginning of my programming journey started with a book.

This was back in 7th grade. I had some basic exposure to BASIC (pun maybe intended?) from our school curriculum, but it was nothing too interesting as our teachers never really treated it as anything important. They would stress a lot on those Microsoft Office chapters (yes, we actually studied Microsoft Office as part of our computer science course at school) and mostly ignore the programming chapters because I dare say many of them struggled with it themselves. So although I had been exposed to *some* programming, it was mostly memorizing the syntax without actually understanding what was going on.

Then one day there was this book fair thing going on at this local Carrefour (for those of you who've no idea, it's a pretty famous hypermarket chain) in this mall, and for some reason my mother and I were in that mall on that day. Now the interesting thing is that this usually never happens -- I usually visit malls with my dad or my friends, this is the only instance I remember where I had actually visited one with just my mom. This turned out to be fortuitous. My father is the kind of person who's generally not amenable to any kind of extraneous shopping requests. My mother, on the other hand, was and remains pliable.

So I basically saw this book -- Sams' Teach Yourself JavaScript in 24 Hours -- being sold at half price. I vaguely remembered having read somewhere that JavaScript is a good introductory programming language (and it helped that this was the time when I was getting into a Google-craze -- I basically saw some photos of Google Zurich and went all HOLY SHIT THAT'S WHERE I NEED TO WORK WHEN I GROW UP (for those of you who haven't seen it, I recommend googling it. That office is the bomb) -- and I'd also read that you need programming skills to join Google). So I begged and begged my mum to buy that book, and thankfully she did.

Back home I returned with my new prize under my arm. Dad took one look at it and scoffed that I'll never actually use it. Pretty much entirely out of spite (to prove him wrong), I attacked the book with a zeal. I still remember how I felt when I wrote my very first JavaScript program (printing the current system date in an h1 tag) and marveling at the output. I guess that was when something struck -- the realization that this was probably what I wanted to do in life.

Fast forward to today, and I've never looked back and wondered what it would be like to have done something else.

PS: for all you beginners out there, JavaScript is a horrible language. Please start with something like Python. Also there are better resources than Sams' Teach Yourself JavaScript in 24 Hours available, that I just didn't know of back then. I'd recommend Eloquent JavaScript any day.