Every fkn 3 to 4 days, some random dev shows up in my office really really fkn confused and frustrated about something he doesn't understand - because I have a dark secret.

Sometime, in cold lonely nights, when no one is watching, I write my documentation before the actual code.

Somehow, sometimes documentation without code attached to it makes it to production.

Today someone yelled at me for wasting his time because he wasted 3 hours trying to find the code the documentation belongs to - and demented I stop the practice from now on.

Agh.

Me and my team in middle of our first hackathon-
a girl who is our class topper is my team mate, trying to write some Android Code.

I am writing nodejs Api, she calls me saying there's a bug in my code,so for saving time I decided to fix that small thing on her laptop,so when I went to the backend folder to open the js file,I see no default text editor set for it. After searching,I found out she had no atom,sublime,vs etc.
I asked her - "Do you even have notepad++ ?".
She - "I have notepad,but not ++".

That day I had to edit my code in Wordpad. I am still shaking.

Alone at home ✔️
Night time ✔️
Battery about to die ✔️
No electricity ✔️
Painfully hot weather ✔️

If I die here tonight, please commit and push my code..
Thanks

Is this the code life
Another scrum meeting
Caught in the the Node life
No escape from reality
Open your eyes
Look up to the screens and see..
I'm just a dev boy
Doing some debugging
Because there's warnings here
Errors there
Segment faults
Everywhere
Anytime you distract
Takes another hour from me
From me

*piano starts

Mama. Just committed a bug
Merge the branch to production
Did it fast for milestones
Mama. The repo has just begun
But now they going to throw the stack away.
Mama. U u u uu
Didn't mean to code in LAMP
But it's the only stack i know how to setup
In Ubuntu. Without docker
I really don't get vagrant

*piano

It's too late
My team is done
Some dev is working in Nepal
A UX dev. Now what is that?
Goodbye everybody
I've got to go
Gotta leave this lame meeting
And face the truth
Oh nooooo. I i interns
(they have questions)
I want to debug
I don't want to stay till 3 in the morning

*epic guitar

I see a litlle dev over there
Let's code review, let's code review
Did he do the last commit?
Coding in the white board
Very very frightening me
That's bug(that's a bug)
That's a bug (that's a bug)
What the f*ck did you do that?
Magnificcooooooo

I was just coding and nobody liked it
He was coding and nobody liked it, spare his some time to do his debugging

Easy man. Here go. Will you let me code?
A meeting. No,we will not let you code. ( let me code)
A meeting. we will not let you code. ( let me code)
A meeting. we will not let you code. ( let me code)
We will not let you code
Never never let you go
Never let you code, oh
No no no no no no no
Oh mama mia, mama mia ( dude, you've gotta let me code)
Screw you guys, I'm gonna code and commit. Commit. Comiiiiitt!

*epic guitar

So you think you can review me and spit in my eye?
So you think you can dump me and erase my branch?
Oh baby, cant do this to me baby
I've just have to log out.
I've just have to log outta here

*epic guitar solo

Nothing really matters
The users will not care
Nothing really matters
To them

Any way this code blows

PHP 🐘 is so damn easy to learn, run straighforward in all OSs, that anyone can start coding in no time. Therefore, the amount of crap code around, made by unskilled devs, is just *unbelievable*. 💩

Had a PR blocked yesterday. Oh god, have I introduced a memory leak? Have I not added unit tests? Is there a bug? What horrible thing have I unknowingly done?

... added comments to some code.

Yep apparently “our code needs to be readable without comments, please remove them”.

Time to move on, no signs of intelligent life here.

Fuck you, devs who quote Knuth:

"Premature optimization is the root of all evil"

I agree with the spirit of the quote. I agree that long-winded arguments comparing microsecond differences in performance between looping or matching constructs in a language syntax is almost always nonsense. Slightly slower code can even be preferable if it's significantly clearer, safer and easier to maintain.

But, two fucking points need to be made to you lazy quickfix hipsters trying to sell your undercooked spaghetti code as "al dente", just fucking admit that you had no clue what you were doing.

So here we go:

1. If you write neat correct code in one go, you don't need to spend time to optimize it. Takes time to learn the right patterns, but will save you time during the rest of your career.

2. If you quote Knuth, at least provide the context: "We should forget about small efficiencies, say about 97% of the time [...] Yet we should not pass up our opportunities in that critical 3%"

YES THAT CRITICAL 3% IS WHERE YOU MESSED UP.

I'll forgive you for disgorging your codevomit into this silly PR.

BUT YOU'RE QUOTING KNUTH IN YOUR DEFENSE?

Premature optimization is the root of all evil... 6300 SQL queries to show a little aggregate graph on the dashboard... HE WOULD FUCKING SLAP YOUR KEYBOARD IN HALF IN YOUR FACE.

This fucking customer...
I've told that person so many times that they need to FIX THEIR CODE, because it get's pwned all the time.
To make stuff worse - they are still using Debian 5, and we are unable to upgrade because all their shit will break.

I found his fix today - he installed an old version of NGINX because it is "better".

No fuck you.

So, rage time.

A few months ago I inherited a big Wordpress website, with around 750 pages.

The client has reported the main menu is broken.

Upon looking at the code it appears the previous "Wordpress Developer" (ahem ...) attempted to rewrite navigation system - no idea why.

As part of the 4000 class below is a screenshot of part of the file where he's determining if the current menu item is active, within a loop. Whilst the whole if statement spans 409 lines - the code basically continues exactly the same downwards.

Shameful :/

Why is it that every time I tell someone I code they instantly think I can hack into things like their phones. Then after that they never trust me with any electronic device.

Me: Hey can I use the toaster?

Them: No! Your just going to hack it.

Why do people (Some devs too...) bloody hell think that devs have Hard time fixing the Semi Colon issue, we have a lot of other issues to figure out, like the Structure of Data, Code Fragmentation, API Creation, Invalid Data Handling, Injection Prevention. But no, since we are developers, we are having sleepless nights because of one fucking semicolon? FUCKING NO, it hardly takes 30 seconds to figure out that there is a missing semi-colon. Really People, stop the ; thing!

Reviewing coworker's code:

Me: I see you're doing a convoluted sort for every element twice to get your two lists in sync... 😐
CoWorker: Yeah. *straight face, no regrets* That's the only way to do this.
Me:... Uh... No? You can just manage one list with a simple struct and then use the the standard sort.
Coworker: Yeah sure I know. But it'll take time. We don't have time.
Me: *aghast* This is embarrassingly bad code!
Coworker: Don't worry, later on I'll use a hashmap for it. But this needs to be pushed now.
Me: *to myself, no you don't need a hashmap*
Okay, you do you but I can't back you on this. It isn't going to take a lot of time to correct it.

Next day.
Coworker: Hey can you review my code again?
Me: You've made the changes already? *in a bored tone, knowing that they wouldn't have changed shit*
Coworker: No this is a different file. Our manager agrees that we can worry about performance later.
Me: Sure. *😀🔨🔨*

Few weeks pass by:
QA: The operation takes absurdly long time to complete even with the smallest data. Ten minutes for X is unacceptable.
Me: Who would've known? ☺️

It's disheartening to see a senior member of my team shitting on the code of less mature developers. Don't just say "this is unacceptable", elaborate, teach them. How are they going to action anything from that feedback?

Take the time to respond to their questions when they ask for clarification on what you're saying. Don't berate them.

Honestly some developers need to learn a thing or two about code etiquette.

There's no room for good cop / bad cop behaviour.

As time goes on, I've always wondered what I'm going to say to my future grandchildren about what Dev work was like today:

"Grandpa Josh what was programming like when you were a kid?"

"OH IT WAS AWFUL. ALMOST NOBODY USED VERSION CONTROL CORRECTLY AND NEW JAVASCRIPT FRAMEWORKS WOULD APPEAR EVERY SINGLE DAY!"

"They at least attempted to use new paradigms in their framework code, right grandpa?"

"NO CHILD. THEY WERE EXACTLY THE SAME IN EVERY WAY..."

Dude, for the hundredth time, stop leaving random chunks of commented out code all over the place in case we "need to find it easily later"...

This is literally the reason we use git.

No, I will not pass it in a code review. The same as last time. And the time before...

Dahhhhh

Yes of course we can have a fourth meeting this week to discuss possible KPI’s for the project.

I have a suggestion though, since the first deliverable is 3 weeks away and it doesn’t work yet, maybe I could spend time ON the project ... so I can build something that could be a KPI ... and not piss off the other companies for delivering nothing.

Of course I’m not a manager, so what do I know, but this shit might be why people keep leaving the team. Perhaps devs don’t enjoy having no time on the project while simultaneously being yelled at for not getting it done.

Hello, I just want to let you know I'm working on a 15 year old product and it is currently in production.

It uses Angular.js and one of the earliest versions of React.js. I cannot use ES6, we don't have Babel, no JSX syntax, no CSS preprocessor. No webpack.

I must support browser since IE6 with an ES3 syntax. (luckily I got some some polyfills for an ES5 syntax)

When I build a component I have to call React.createClass and React.createElement.

The render() function is basically a nested pile of React.createElement.

There is no documentation for this product, no tests, no anything.

I had to reverse engineer it in order to understand how it works.

The code base uses mixed programming styles and naming conventions, plus thousands of little js files.

Oh and obviously no hot reload, every time I make a change I have to restart everything.

Please, send help.
I'm in danger.

Sincerely,
An underpaid developer

....
I'm not crying, you are crying...

Manager: I like nested ifs

Dev: They can be difficult to maintain

Manager: No they aren’t I write them all the time!

Dev: Have you ever maintained one?

Manager: No, I don’t do code maintenance. I don’t have time for it.

Do you really expect that I can debug in a few minutes, a part of the software that I didn't build and have never seen before and have no knowledge of the external, third-party web service that code is reaching out to?

Dude, flippin' chill, take a walk, grab a drink, pop some popcorn and give me some time to figure out what the hell this code is doing so I can properly debug it!

You know what it turned out to be? Wrong test data used for the 3rd party service. So in essence... Nothing was wrong! Frickity frack!

Been a jr. dev at a company that's badly in need of more devs. So they hire a sr. dev to work w/ me. Dude's got yrs of xp over me, so he should be ramped up in no time, right?

Jk, he doesn't even know the basics of git. Also, his code is shit. If he's not let go anytime soon, at least I'll look awesome relative to this guy come performance reviews ¯\_(ツ)_/¯.

I have no words to describe how I'm feeling these days. I have to do a C project for uni.

After a couple of years dealing with web dev, javascript, typescript, angular and stuff, for the first time I have a project where I have to deal with only two problems:

1) my code
2) my machine

No tools, no bloated libraries, no webpack, no json configurations, no tutorials.

It's just me, vim, gcc (actually nvcc, it's a cuda based project, but still) and the cuda manual.

I feel I'm actually building something.

Plus, the guy I'm doing the project with is cool with this stuff and most important he's open minded.

I'm happy

It was 1999. I was just starting my first real job as a programmer for a major insurance company. We were working on code that would screen scrape legacy mainframe data output and convert it to a web-based UI. REALLY stupid project approach I had no input on. I happened to find a programmer in Germany who had released his code in the public domain that would help with making a certain conversion task easier. I downloaded his code and put it to work.

During a code review, a programmer who was probably about 60 asked me where I got the code and what it was doing. I didn't even get to the part about what it was doing because he made fun of me so badly, in a fake German accent in front of a room full of non-programmers, for using code that today is no big deal due to the prevalence of open source. I just clammed up in humiliation because he got everyone laughing at me. His philosophy was if we didn't buy it or write it ourselves, we had no business using it.

I guess I was just ahead of my time?

That moment you realise why you enjoy the dev life again.

It's been a long time since I've had a solid day of coding, just coding..., no meetings, no wild requests, no crazy issues, no data fixing because someone can't type a number correctly, just me, myself and that keyboard going on a field trip of quality coding time again.

Ah, it's a good day to end the week on!

Girlfriend had issue with her Python code (she does mathmatics, not actual programming):
```
t = 51.74636335135748
i = int(t*100) // 5174, wrong value
```
instead of
```
t = 51.74636335135748
i = int(t)*100 // 5000, right value...
```

She asked me if I could fix it for her.
I found the issue but wanted her to understand what went wrong.
She didn't care "because she didn't have time for it".
Well, then it's quite simple for me: I have no time to help her :^)

I am sure this has happened to all of us in some extent with some variations.

Colleague not writing comments on code.
Ask him something like "How am I suppose understand that piece of garbage you have written when there is no comments or documentation?"
This keeps happening for a long time. Some time after, I write a kernel module using idiomatic C and ASM blocks for optimizations (for some RTOS) and purposely not write neither documentation nor comments.
When he asked for an explanation, I answered to everything he questioned as general as I could for "that trivial piece of code".
After that he always documents his code!
Win! 🏆

"LeT's uSe gRaPhQL!" They said.

"It EliMinAtEs cOmpLeX aNd vErBoSe REST coDe!" they said.

Me sitting here for hours waiting for the backend team to fix major regressions every time they push the smallest "updates" to staging... 🤡

Call me a boomer but I can't help but feeling graphQL makes things MORE complex than REST... either that or the backend devs have no idea what they are doing

You know what grinds my gears. Spaghetti code, bloated code base with 5000 line files, and poor file organization.

Seriously really pissing me off right now. Its like walking into a library and there's no shelves and the books are just thrown into massive piles.

I've spent so much time trying to figure shit out just to implement basic things. Its messing with my productivity and making me hate my job.

!rant ~dev

I use my headphones religiously every time I code, as well as for things like tutorials & courses.

I was devastated that the slider switch on my pair of H8s snapped and I could no longer use them wirelessly.

I didn’t want to be without headphones for weeks while they were replaced abroad, so...

Hello upgrade. Hello business expense.

Lovely new pair of H9is.

1. Trust no one even yourself
2. Ask questions even if they are stupid
3. Test your solutions, even manually
4. Write comments
5. Take your time to solve problem, even if it looks like easy see point 1
6. Take some time during work to get familiar with code and read something about technology that is part of your current work - even if you know it - see point 1
7. Always try to see a big picture - see point 2 - why is it implemented is more important then how is it implemented

There are three things in my workflow that I don't like:

1. Feature requests appearing out of thin air.

It's common to be handled work at 2pm that needs to be deployed by the end of day. Usually it's bug fixes, and that's ok I guess, but sometimes it's brand new features. How the fuck am I supposed to do a good job in such a short time? I don't even have time to wrap my head around the details and I'm expected to implement it, test it, make sure it doesn't break anything and make it pass through code review? With still time to deploy and make sure it's ok? In a few hours? I'm not fucking superman!

2. Not being asked about estimates.

Everything is handed to me with a fixed deadline, usually pulled off my PM's ass, who has no frontend experience. "You have two weeks to make this website." "You must have this done this by tomorrow morning." The result, of course, is rushed code that was barely tested (by hand, no time for unit or integration tests).

3. Being the last part of the product development process.

Being the last part means that our deadlines are the most strict. If we don't meet the deadline, the client will be pissed. The thing is, the design part is usually the one that exceeds its time (because clients keep asking for changes). So when the project lands on our desks it's already delayed and we have to rush it.

This all sounds too much like bad planning to me. I guess it's the result of not doing scrum. There are no sprints, no planning meetings, only weekly status update meetings. Are your jobs similar? Is it just usual "agency work"?

I'm so tired of the constant pressure and having to rush my work. Oh, and the worst part is we don't have time for anything else. We're still stuck with webpack 2 because we never have time to update it ffs.

CR: "Add x here (to y) so it fits our code standards"
> No other Y has an X. None.

CR: "Don't ever use .html_safe"
> ... Can't render html without it. Also, it's already been sanitized, literally by sanitize(), written by the security team.

CR: "Haven't seen the code yet; does X change when resetting the password?"
> The feature doesn't have or reference passwords. It doesn't touch anything even tangentially related to passwords.
> Also: GO READ THE CODE! THAT'S YOUR BLOODY JOB!

CR: "Add an 'expired?' method that returns '!active'?"
> Inactive doesn't mean expired. Yellow doesn't mean sour. There's already an 'is_expired?' method.

CR: "For logging, always use json so we can parse it. Doesn't matter if we can't read it; tools can."
CR: "For logging, never link log entries to user-readable code references; it's a security concern."
CR: "Make sure logging is human-readable and text-searchable and points back to the code."
> Confused asian guy, his hands raised.

CR: "Move this data formatting from the view into the model."
> No. Views are for formatting.

CR: "Use .html() here since you're working with html"
> .html() does not support html. It converts arrays into html.

NONE OF THIS IS USEFUL! WHY ARE YOU WASTING MY TIME IF YOU HAVEN'T EVEN READ MY CODE!?

dfjasklfagjklewrjakfljasdf

They've literally left me with nothing to do. I'm doing nothing. I can't be happy doing nothing.

To illustrate the chaos: Everyone on the team was trying to figure out some defect. No one knows what is going on in the code. It's unlike anything I've ever seen.

I found an API call with a misspelled endpoint. It was wrong since the code was written two months before. There's no way it ever worked. Obviously no one tested the code because they would have immediately seen that the call returned a 404 every time.

I fixed it. That was my only PR in about a month. It was literally one character.

The next week that PR got reverted. Apparently the app works better if the API call fails. No one said what goes wrong if the request is made, just that it "causes problems."

That's how bad it is. No one knows why anything does or doesn't work. People write code that doesn't work, never test it, and the application works better in some unspecified way if that code never gets executed.

The last straw for me was when an architect told us that if we want to improve our skills we need to learn how to read and debug stuff like this.

1) Not to be immodest, but I'm good at figuring out bad code.
2) Just because I can doesn't mean I want to do it all day instead of actually developing software
3) He trivialized the really important skill, not making a mess like this in the first place. If his idea of skill is to sling crap without tests at the wall and then debug it, how is he an architect?

I tried really hard but I can't keep a good attitude. I don't want to become toxic, but why would I consider working that way? I try my best to be good at this. Writing decent code means a lot to me. It should mean a lot to them. Their code is costing them hundreds of thousands of dollars. Maybe millions.

I can't write good code and add value if all I do is debug bad code.

So I'm out. I'm going to another project. Have a nice life.

Guys guys guys. Conversation had right just now. A PM from the company I’m freelancing for just said

“We need to move away from SQL server and shift all the data to MongoDB. I don’t want it to take more than a month tops”

Verbatim. No context. Nothing. The website is for a small time supply chain software that’s been chugging along for a decade now with spaghetti code everywhere.

How do I even respond? The other guy who works with me sent 😂😂😂 to me privately and now is offline lol wtf

Okay so this happened ages ago (nearly five years) but this suddenly came to my mind again.

It was in the first year of my study (currently in my 5th and last year).

I was experimenting around with php and mysql during some free hours. All the insert,delete and so on statements worked perfectly find except for one update statement. Started to debug of course and after a little while of no results I was like "oh yeah right, something like logs exists of course". Looked in the logs but nothing. No matter how I altered my code (rewrote it numerous times for some 'clean starts') it just would not run the update statement.

Alright, time for some class mate help. After multiple hours of debugging with a few classmates, there was still no result at all.

Time to bring in one or more teachers. After hours of debugging, still no result even with the help of a few good teachers.

Decided to give it a rest for that day.

Two weeks later it still was not updating anything/working and I finally gave up.

Till today, I still have no clue what went wrong and it still bugs me from time to time :/

I have this teacher who focuses so much on documentation that I hardly get to code sometimes. The worst experience with that teacher was with a project I think about two years ago. Every time I came up with (modified) documentation (we have to document EVERYTHING before allowed to start programming) she would turn me away with some bs argumentation and also point out non existing English grammar errors (my English is way better than hers). After nine weeks of documenting (so, no single line of code yet and projects take ten weeks) she gave me the green light. Then at 'delivery' she had the fucking balls to to tell me that MY CODE WASN'T THAT STABLE AND GOOD YET.

I WAS LITERALLY HAVING A LIVE RAGE ATTACK OVER THERE.

Structure: decades of programming in too many languages to enumerate. I lean functional, but only when the language doesn't fight it. No matter what I'm doing, my code is immutable in practice, if not paradigm.

Syntax: No one thing in particular. I code differently depending on the language.

When I start learning a language, I'll find the standard style checker and create a project where I write an example of every single rule.

The end result is generally a quick intro to the language and a bonus understanding of the hot sports opinion in said language. I call this an ocean boiler.

I lean heavily into autoformatting because I've worked on too many projects to care, and I have a general expectation that something which is important enough to make a code standard is important enough to be enforced in tooling. I'd rather spend my time solving problems that thinking about stylistics.

Finally fixed a major bug.....

FUCK YOU C# AND YOUR FUCKING CASE SENSITIVE BULLSHIT.

DAYS
THAT TOOK FUCKING DAYS AND AT NO POINT DUD VISUAL STUDIO BOTHER TO MENTION THAT FUCKING ERROR.

1 CHARACTER, ON ONE LINE, EFFECTIVELY BROKE THOUSANDS OF LINES OF CODE

fuck this, I quit. See you next time you contact the Microsoft live support chat!

FUCK FUCK FUCK FUCK
I HAVE A TEST TOMORROW AT 8 AM AND I'VE BEEN TRYING TO SLEEP SINCE 12.30 AM. IT'S 6 AM ALREADY, 6 AM!

I guess when they no screens before sleeping they really mean it. I'm fucked, I'm really fucked. I guess I'll stare the ceiling until the alam goes off and accept an awful day and hope I get pumped up during the test or something. Fuck me. I want to fucking SLEEP. Fuck.

I just wanted to install vivaldi before sleeping and watch the last rick and morty episode. Does that fucking make me a fucking night owl? No. I could've use these precious time learning or writing code, or even sleeping, but fuck! I'm stuck here in time, just waiting for fucks sake!

Good night...
OR That's what I WOULD say if I could sleep...

When your specs simply won't run new code no matter what you do, non-conditioned (and unmodified) calls don't get called, and 2+2 somehow equals Q, you know it's time to give up and restart the simulation by going to bed.

Except it's early afternoon and the project deadline is tonight. 😔

Back to debugging reality.

So this one time me and my teammates had just started working on react (please note that we all were backend developers and no one has the basic understanding of javascript) and things were looking quite exciting..

But towards the end of the deadline we were sitting and refactoring each others code since we had not decided on the coding standards and practises and random code had been written left right and center.. It once happened that the same piece of code was refactored multiple times by only 2 people..

And it is obvious that we couldnt make it to the deadline and that code is sitting there like a mixture of weird things..

Boss: Any idea why ColleagueX's code might be blowing out the memory?

Me (internal): Cos he's a fucking retard who can't code for shit, doesn't listen when I tell him to do stuff properly because he's fucking lazy, has no idea what stack and heap are, uses goto everywhere, doesn't know how to debug, doesn't write any unit tests, and generally WASTES MY FUCKING TIME!

Me (external): Probably a memory leak. I'll take a look.

My current project is a fucking nightmare.

It started in 2007, using a solution developed by an Indian company due to outsourcing (aka low-quality code).

It's running on Java 7 on the back-end and its front-end side is pure Javascript files. There are thousands of little .js files everywhere, no documentation, no comments, differents coding styles, outdated API that were already outdated at the time, mixed oop and procedural.
Not even when I started coding, I wrote something so horrible.

Yo, it's a clusterfuck and I just wanna get drunk.

No rant, just appreciation

A thank you to the senior developers out there who take the time to help us juniors out, to look at our (potentially) shitty code and point out how to improve it.

To help us to see the bigger picture and maybe take a more lengthy approach to a problem that'll pay off in the end.

And lastly, thanks for allowing us to learn from your years of bug splatting, stack tracing, null pointers and error messages.

You guys rock

Another project with legacy code got just dusted off at work. Shits fucked beyond recognition! We got:
- Rando variable names that mean nothing
- Timers running with a cycle time of 2.5ms if you start them with the multiplier 1.
- An Interrupt routine thats 300 lines long.
- Another interrupt thats starting an ADC conversion and waiting for it to complete before returning.
- For loops that start with one and subtract one from the iterator in the loop
- Every value that would normally be expressed as a regular number is written down in Hex. Eg: if(val==0x05)
- State machine built without writing down which state is which. Its just a number. (In hex obviously!)
- All running on a Microcontroller you cant debug on.
- Using a compiler no one has ever heard of before.
- Weird ass Port manipulations
- 15 different .hex and .elf files with no clue whats in them.
- No version control
- We tried explaining the code to a monkey and it hanged itself.

We are a small size product based company. There was a change in management a year back and the new management decided to fire the entire engineering team one by one. I was hired as full time back-end developer (C++). Just after I joined they removed the last 2 engineers from the previous regime and handed over devops and Python API development to me as well.
There was no documentation for the main product which was a sophisticated piece of software. There were no comments in the code as well. I had to go through line by line (roughly 100,000 lines of code).
Then they decide to hire more devs.Turned out to be false hope. They hired interns who had no programming knowledge.
Now they got two clients who are interested in using the service. They lured them using empty promises. The product is not stable. The cloud infrastructure is not at all ready. The APIs are a mess. I don't know which one to work on.
Worst part is that there is no other technical person in the office.

I'm thinking about quitting now. I don't know why I haven't already.😖😖

Me: I want to be a dev..
Mom: But you only sit in front of the computer to play games.
Me: That's not what I always do.
Mom: Then why are you sitting behind the computer all the time.
Me: To make software. Most of the time you clearly see me typing code.
Mom: No, I can't trust you, you play too much games. Study hard and get another job.
Me: *Middle finger behind a back.*

Today I looked at some code from our CTO. He used plain SQL Statements with huge selects and no prepared statements.

I asked him:
1. why dont you build some helpers or even use some frameworks?
2. why are there no prepared statements?

His answer (to both questions)
We do not need that. That just uses too much ressources and time. It's more cleaner and simpler this way.

My Face: 😵

Devs : Lets pick library X, it is well know piece of open source technology, actively maintained by community for over 10 years.
Architect : NAH, it is an overkill to use it in our project , lets build our own solution.
*2 Months later*
The code base is hundreds of thousands lines of code, we basically started to look at library X on GitHub to copy features or get inspiration from that code. In that time we delivered 0 business value, it is horrible to use it and we constantly adding something or bugfixing because no one thought about something in first place.

Dumbest experience.
Talked to recruiter, they praised I know ruby, said I needed to do a code test in ruby.

I was given 1 hour to complete 5, exercises in a codefight like thing.

1 exercise had C as the only lang option.
2 more had C and Python.
The last two has ruby too, they were permutation exercises that never completed within the time restriction (that was probably on me, but they did complete on my local ¯\_(ツ)_/¯ )

I told them about all this, I failed, no second chances, no explanation, no nothing.

!rant

Snow may be around
There may be no sound
Except for the quiet hum
Of a devs system

While you want to stay up and code
Don't forget to decorate your abode
For it's that time of year to put up the tree
And surround yourself with family

bladder: I got to pee.
me: NO! To deep in code zone.

[20 mins pass]
bladder: I got to pee.
me: NO! Let me finish this.

[30 mins pass]
bladder: I'VE GOT TO PEE
me: NO! In a zone.

[5 mins pass]
bladder: GO! GO! GO!
me: D**n you bladder.

I hate this game. I lose every time.

Manager: We need to fix this QA backlog. I’m going to share the workload of doing QA.

Dev: Please don—

*Dev email notification getting spammed with approvals*

Dev: …Are you even pulling the code down to test it locally?

Manager: There’s no time for that! We have to get this PR backlog pushed through! I’m just looking at the code to see if it looks good and approving based on that.

*Later that day*

Manager: HEY NONE OF THE FEATURES ON STAGING MEET THE REQUIREMENTS AT ALL. THIS IS A BUGGY MESS, WHAT HAPPENED GUYS??

Dev: …

On a bus, no wifi. Time to code in a language i dont know without the docs.

!rant
Just started working for a new company. Super cool. Just like the last one (as far as perks), except they actually trust their devs.

Old company: Make sure your code is extensible
Devs at old company: You know it's not written in stone right?
Old company: Does that mean you can make it do this?
Devs at old company: No. That's the wrong code base

New company: I need a feature. Get it done when you can
New company devs: Well, guess I'll take some time to refactor all this stuff while I'm at it
~Some time later~
New company: Thanks, that feature works great!

No staring over shoulders, asking when it will be done. No asking why we want to refactor something. As long as work continues to flow, there are no issues. It's great!

Also, if we want to try a new tech, we just have to put together a short paper explaining why it will work better in that situation than the tech that's already in place.

The one that made me quit was when I was told I had to drive to the data centre and do a backup every day over the bank holiday weekend with no extra pay or time off. For no reason. And yes I know I'm an idiot for doing it but whatever.

The one that made me walk out, a month and a half later, was when I came in on Monday morning to discover that my boss had entirely rewritten the code I had spent literal months on in one weekend. Naturally he'd broken it and said it was an improvement.

[Typical dump Client]

After finishing an Android app, the app was amazing and the client is happy.

Client: I think we should write iOS version.

Me: ok, but this will take a time to code in different language with those native features..

Client: Can we just "convert" it to iOS, it should be easy no?

Needed to convert a collection of .avi videos to .mp4. Online converters only allow 1-2 videos at a time, with slow uploads, so no option.
Can't find a program that quickly fulfills my needs. Interesting ... 🤔
Look for python and a quick and dirty solution, ffmpeg and subprocess it shall be then.
Install ffmpeg, run subprocess with ffmpeg, put it inside a for loop, iterate over all videos with their respective number. Done.
3 lines of code, saved some time.
It's great to be a developer (sometimes).😏

long time ago....
Feature request: We want an android backup solution in Our app!
UI guy has already developed it, you just need to see if his solution is solid!
Ok then - lets look at the UI: Nice progress bars, that turn into green checkmarks. Looks good.
Now lets look at the code: ... Ok. loading some files into memory.... and... dafuq? does not write to a file?

Backup to RAM. With no restore. 🤦‍♂️.

I look after servers, softwares,vendors and write code too. I am also learning datascience in spare time. Suddenly I found that I am giving no time to family and friends.

Wrote some code that solved a program in a semi unique way for the codebase. As in not oft used functionality of language.

Some time later... This might be hard to understand. Maybe I should do a different way.

Some time later... No, I will leave a comment to describe what is going on.

Some time later... That comment is kind of cryptic. Maybe should rethink.

Some time later... No, if the next dev doesn't know how this works then they should learn how it works. (reasoning here is that the functionality requires a knowledge of internals of language)

Some time later... Also, if nobody else gets this then they have to ask me how it works. Job security?

Some time later... STOP THINKING ABOUT THIS CODE AND MOVE ON!

A project I'm working on uses Elastic for internal monitoring and logs. The customer asked to access those logs - not something we'd normally do, but it's isolated from other things we use and there's no critical data there, so what the heck, let them have it.

Ever since, we're getting tons of questions like "There are tons of [insert random info message] all the time, do you have any plans to resolve them?" and it gets to the point where I'm just about ready to scream back "NO, SUZAN, BOOKING NOT COMPLETED MANS THE USER F###ING CANCELLED IT, IT'S NOT SOMETHING I CAN FIX IN THE CODE"

Edit: the customer's name isn't actually Suzan

My first rant...

Every time a coworker asks for an enhancement, the request is followed by "it should be easy to implement".

1) If you think it's easy, then you obviously know the code better than me, right?
2) The idea of the enhancement may be easy, but you don't think about how a small change can have a cascading effect throughout the entire process... and potentially in a catastrophic way.

Happens every time. Maybe I'm just bitch eating crackers at this point, but it annoys me when people analyze something they have no idea how to write themselves.

Being so busy that there is no time to code 😭

So... I've got a confession to make.
I'm no longer a Dev. After the disaster that was my last commercial gig, I went and got a sec Ops role... And I love it. It's just technical problem solving and explaining all the way.
Don't get me wrong, I still love to code. But that's exactly the thing. As a commercial developer employed by corporations, I spent close to 80 % of my time not coding, but in useless meetings, or trying to figure out just what my colleagues thought was "common sense", reverse engineering their work and documenting how to get it running, etc. Basically, fixing shit for braindead academics with next to no real world experience.
Now, when I code, I get to do it on my own terms, with my own stack and as much comments and docs as I want to have. I own my time, and the only ones that are allowed to interrupt me is the local fire department.
I can do what I'm fucking passionate about and leave the rest for the useless people.

Confession: I'm launching a major project for a client this time next week. It's some of the worst code I've ever written in my entire life. It's beyond awful, but I have no choice. It's sure going to be fun fixing it for the next 2 weeks post launch.

We have this important product with deadline closing in. Dev who was working on it for months went on vacation. Bugs came out, no comments in the code, no docs, some of the variables are as verbose as var abc = "some weird shit"; and I'm tasked with trying to test, fix algorithms and instruct on how to use it.

This isn't first time happening, so I'm dusting off my CV this weekend.

I don't get it why there are so many people out, that think testing stupid model classes with getters and setter is needed.

Dude. There is no logic in this class ... it's pure data that gets not modified there (well except if you call the setter)

I've wasted way too much time writting useless unit test because some ppl want to masturbate on 100% code coverage 🤦🏻‍♂️

So I had this conversation with my boss yesterday...

Me: Hey, I found this bug in the other team's code that has a major impact on what we're trying to do. Can you ask them to look into it?

Boss: No, I don't want to be the one who has to tell them there's a major bug in their code. Find a workaround.

M: But... It isn't really a major bug, it just has a big impact on our side of things.

B: Workaround!

Fuck bosses who value how they think they look to other devs over a day of my time. Fuck.

HELL WEEK is coming!! they are going to make us code IN PAPER again.... no compilers, no way to check for errors, time to die again

Am I the only one who can't cheat on my design/development stages? For example, if I am doing a favor for someone, I will do it my way even when I'm short on time. I simply can't just "take it from the internet and incorporate it into my project".

I just feel for comfort when it's mine. (no Im not referring to reusing code. Clarification in comments)

So I was looking through some old files, looking for some help while I was working on a project and I came across my first codes I wrote in school.
This one time I challenged myself and I tried to write the code a bit.....different. When i ran the code it worked as it should, no problems, then he said:" Show me the code how you did it". I giggled a bit and opened it up. I still remember the expression on his face. He wanted to say something twice but couldn't. Then he just sighed and said, please don't do that again.

The more I learn about programming the more terrified I become about having huge knowledge gaps and learning something wrong by possibly making wrong assumptions about how certain things work or by falling on bad tutorials. I'm constantly hyped about coding, and at the same time I always feel I will never be able to say confidently "I know how to code".
How the hell do you make sure you are learning programming correctly as a self taught? Or do i just have to accept that no matter how and what I code there will always be a better way to do it, resulting in me constantly feeling as a low-skilled coder?

After a developer writes a 1000 lines of code with no unit tests then it is time to go home.

I have a lab at uni where my lab group have to refactor some code from an open source project. We got assigned some Apache project and jfc that code is a mess. Little to no documentation, hard to navigate, tests that you have no idea what it's testing, and so on. On top of that the teacher expects us to spend more time than we have on it. I'll be glad when this course is over :))

Dear fellow project member,

I agree that most code should explain itself, but if you need to use a certain method which requires you to pass several different values of the same type and you just pass values as you like and then get, as you like to call it, 'unexpected behavior', then that is YOUR F***ING PROBLEM.

I DO know your thoughts about documenting code and I DO know you think documenting code only delays the progress, but if you for once could please CHECK THE DOCUMENTATION I WROTE, there would be no need to message me EVERY FIVE BLOODY MINUTES to complain about something that actually works when used right, just because you are too lazy to read the docs!

If you would do that next time, at least the time i spend writing documentation for our project would not be COMPLETELY WASTED! 😤

Kind Regards

Well after years of programming, I've hit my first runtime error that provides no info , the code fails prior to being able to generate an error so this is fucking fine :-)

And of course, the one time I need stack overflow, it tells you to initialise the class with data... Yet the class doesn't contain a fucking constructor... Smiley face

Step 1. Learn to code .
Step 2. Exchange code for money.
Step 3. Exchange money for car, soap & a clean shirt.
Step 4. Profit.
[GOTO: Step #1]

Lol. OK on a serious note coding improved my love life, it drastically reduced the frequency of dates - but dramatically improved the quality and duration of my relationships.
I used to believe that anyone/thing had the potential to be great - and (like me) all they needed was a little time to seize an opportunity.
This essentially meant there were no deal breakers and I spent a lot of time giving people benefit of the doubt and investing a lot of time & effort supporting and trying to build on aspirations that would turn out to simply be fantasies I was indulging.

I still idealistically believe that everything/one has infinite potential - only now I know which problems are worth solving, which are purely for fun or a thought experiment and which should immediately be thrown out and refactored.

All the ambition in the world is void without drive.

So... I was in bed going to sleep 5 minutes ago... I just had a thought I have no idea from where...
My dreams are controlled by code source files...
Change source files, I will have different dream....

Guess I spent a good amount of time with source files today 😅😅

Most painful code error you've made?

More than I probably care to count.

One in particular where I was asked to integrate our code and converted the wrong value..ex

The correct code was supposed to be ...

var serviceBusMessage = new Message() {ID = dto.InvoiceId ...}

but I wrote ..

var serviceBusMessage = new Message() {ID = dto.OrderId ...}

At the time of the message bus event, the dto.OrderId is zero (it's set after a successful credit card transaction in another process)

Because of a 'true up' job that occurs at EOD, the issue went unnoticed for weeks. One day the credit card system went down and thousands of invoices needed to be re-processed, but seemed to be 'stuck', and 'John' was tasked to investigate, found the issue, and traced back to the code changes.

John: "There is a bug in the event bus, looks like you used the wrong key and all the keys are zero."
Me: "Oh crap, I made that change weeks ago. No one noticed?"
John: "Nah, its not a big deal. The true-up job cleans up anything we missed and in the rare event the credit card system goes down, like now. No worries, I can fix the data and the code."
<about an hour later I'm called into a meeting>
Mgr1: "We're following up on the credit card outage earlier. You made the code changes that prevented the cards from reprocessing?"
Me: "Yes, it was my screw up."
Mgr1: "Why wasn't there a code review? It should have caught this mistake."
Mgr2: "All code that is deployed is reviewed. 'Tom' performed the review."
Mgr1: "Tom, why didn't you catch that mistake."
Tom: "I don't know, that code is over 5 years old written by someone else. I assumed it was correct."
Mgr1: "Aren't there unit tests? Integration tests?"
Tom: "Oh yea, and passed them all. In the scenario, the original developers probably never thought the wrong ID would be passed."
Mgr1: "What are you going to do so this never happens again?"
Tom: "Its an easy addition to the tests. Should only take 5 minutes."
Mgr1: "No, what are *you* going to do so this never happens again?"
Me: "It was my mistake, I need to do a better job in paying attention. I knew what value was supposed to passed, but I screwed up."
Mgr2: "No harm no foul. We didn't lose any money and no customer was negativity affected. Credit card system may go down once, or twice a year? Nothing to lose sleep over. Thanks guys."

A week later Mgr1 fires Tom.

I feel/felt like a total d-bag.

Talking to 'John' later about it, turns out Tom's attention to detail and 'passion' was lacking in other areas. Understandable since he has 2 kids + one with special-needs, and in the middle of a divorce, taking most/all of his vacation+sick time (which 'Mgr1' dislikes people taking more than a few days off, that's another story) and 'Mgr1' didn't like Tom's lack of work ethic (felt he needed to leave his problems at home). The outage and the 'lack of due diligence' was the last straw.

* No raise after one year, even that I don't earn that much
* Working in the oldest project
* Everyday I have to make quick fixes, usually requested by leader
* No spare time to rewrite shitty code - always something have higher priority (like doing some tasks that I shouldn't do, just because I had no tasks for next sprint)
* Got feedback from leader that I "hack" too much instead of writing code properly (see third dot)
* Every company around pays more and have more up-to-date stack
* The only guy that wanted to change stuff and use more generic approaches from other teams just threw resignation paper

PM: this is our super fancy new CI/CD pipeline, it's the greatest. i expect you to learn and understand all this in no time.
devs: so i have to spend some more time on this topic because it's completely new to me and requires some learning...
PM: nooo, that's a super easy task with zero effort, my braindead hamster can do that in no time, so can i, and so can you! let's assign 1 story point for that.

~ 3 months latèr ~

also PM, after he has started developing as well: so i'm realizing there are many things that i have to learn, and it takes me some time. i haven't developed with C++ and <other tool stack> for a longer time. by the way, you guys don't need to check for any quality right now, we need to deliver fast. it's okay, when you have memory overflows, your code is completely crappy, poor architecture or memory overflows, it doesn't matter.

he even has a subtask for migrating his code from VS project to our new project structure, since he refused to learn our pipeline right from the beginning and created VS project instead. シ why is this a subtask? this job can be done in no time, my left vanishing twin named Klaus who has dislexia and hates vim can solve this task in 20 seconds!!!!11

(and still no PR, not even a feature branch in our repo)

as a C# dev every time i have to code something in JS i'm just ranting because

- no types
- no fucking errors

i tried to move a Oval in an HTML5 canvas via Drag and Drop and after one hour I gave up...

such a fucking creepy broke language..
as a proof, if js wouldnt be that fucked up why is there typeScript, CoffeeScript, Brython, ... ?

Cant wait to finally use WebAssember...(really)

So before the Age of JavaScript, when programming was trying to be an engineering discipline, I felt like we were getting close to figuring out what worked and what didn't. We had rules of thumb (more general than Patterns) and code smells.
Then JavaScript came in and no one had time to think about "engineering" anymore. I'm fine with MVP and small iterations, but the disdain I see for making code clean and extendable and improvable is baffling (and annoying). First-time coders might never have had to fix someone else's code, but two weeks in a chair should have fixed that.
It's not that understanding code is so hard (although it can be); understanding the _intent_ is hard. This MVP is great, but when no one had time to document what is actually supposed to happen, programmers have to reverse-engineer the *design*.

My day:
5:30AM - 2yo son wakes me up, I send him back to his bed
6AM - wakes me up again, gotta grab a coffee
7:30AM - leaving towards the office
8:30AM - finally arriving to the office, after horrible traffic.
*continue working on major schema change I started yesterday*
12:30PM - Lunch + Beer
1:30PM - Tequila time!
*back to work*
7:30PM - Finally done with coding, leaving the office
8PM - home at last
9:30PM - Beer time
9:31PM - "I'll just write a couple of more lines"
12:30AM - "That's it, no more code for today"
12:31AM - "I'll just scroll through devRant"

It feels like no matter what i fucking try at this point, the universe is doing everything in its power to stop me from succeeding.............. I got so fucking depressed that i am literally writing code and crying in the same time.........

How do you deal with someone like this?

I've got this dev at my workplace that is terrible to work with, he's 2 main reasons why I say this:
1. He has no clue about team work, every piece of code he writes is written as if he is the only person that has to ever touch that
2. He's overtly protective and opinionated on things that make no sense, they're non standard "rules" that he sets and enforces by replacing others code with his own (often times you see quite large PRs and after inspection you realize he rewrote parts of code to follow his style). These "rules" also take up a really long time to follow and would make any actually experienced developer question this guy's knowledge, one example of this is where he repeats the same code over multiple components for "encapsulation reasons" and God forbid you create a global helper of some sort, he'll straight up remove it the next chance he gets. Another example is that all his components or utilities live inside 1 base directory, so you have roughly 300+ components in a /components directory, all with non standard names so you can't tell which is related to which.

I hate working with this person, it's annoying and it also sucks because he's sort of a more "senior" Dev so managers take his side most of the time.

Made an Android app a while ago. I needed some pet project so I decided to go with Java for Android. First time, no experience at all.

So everything went ok, I had a little help from a colleague, structuring code, and pushing to the store. Work done app was doing ok.

A year later I came back to this project. I needed to fix a bug - date time and daylight savings crap. 😥

Spent a week on it. Ready to push a new version to the store, with some extra features! Build apk. All good.

Wait. I need to sign the APK? Wtf. I had to format my hard drive. How do I recover my fucking certificate?

*Google's for a while*

No fucking way. I can't restore the certificate. Or get the keystore back. The solution is to create a new app with a brand new package name?

Thanks for nothing, I'm done with Android development.

So here I am testing some python code and writing to a file. No big deal. But damn is it taking a long time to get data back from this API. Ah it's fine I'll let it work in the background.

40 minutes later.

Oh! The requests timed out. No big deal. I'll just cut out the parts that are already done.

1st request in.
I wonder what the file is looking like.
Only showing 1 request.

waitaminute.jpeg

I should have more than that.
*Suddenly realizes that I was writing to the file and not appending.

Fuuuuuuuuuuuuuuuuuuck

I did mostly Java and JavaScript coding before I came to my current job. When I started I pretty much had to learn PHP on the fly. Pretty much no problems, but my greatest shame from the few years I've been writing code is when I spent over an hour debugging an unknown error, after which time a fellow dev looked at my code and informed me that PHP uses . instead of + to concatenate strings...

When you spend 10x time coding just because you can't, just can't resist writing good code, even when you no it's gng to make no difference whatsoever🙁
Why brain, oh why?

How I feel when im asked to add functionality to a project that was built like 10+ years ago and needs refactored in its entirety but the code base is so terrible that youre honestly better off just starting it from scratch but you are thrown into 5 other million things and there is no time to do it so you just shit out the bare minimum code that will not break the rest of the application.

Our project at work goes live in 3 weeks.

The code base has no automated tests, breaks very often, has never had any level of manual testing

will not be releasing with any form of enforced roles or permissions in our first release now due to no time to enforce, however there is a whole admin api where you can literally change anything in our database including roles.

We also have teams in various countries all working separately on the same solution using microservices with shared nuget packages and they aren't using them properly.

Our pull requests are so big - as much as, 75 file changes - in our fe app that I can't keep up with it and I honestly have no idea if it even works or not due to no automated tests and no time to manually test.

We have no testing team, or qa team of any sort.

Every request into the system has to hit a minimum of 3 different databases via 3 different microservices so 1 request = 4 requests with the load on the servers.

We don't use any file streams so everything is just shoved in the buffer on the server.

Most of the people working on the angular apps cba to learn angular, no one across 2 teams cba to learn git. We use git so they constantly face problems. The guy in charge has 0 experience in angular but makes me do things how he wants architecturally so half the patterns make no sense.

No one looks at the pull requests, they just click approve so they may as well push directly to master.

Unfinished work gets put in for pull request so we don't know if the app is in a release state since aall teams are working independently, but on the same code base.

I sat down and tested the app myself for an hour and found 25 fe only issues, and 5 breaking cross browser issues.

Most of our databases are not normalised. Most of our databases make no sense. 99% of our tables have no indexing since there is no expertise with free time to do it.

No one there understands css properly. Or javascript.

Our. Net core microservices all directly use ef in the controller actions so there is no shared code there.

Our customer facing fe app is not dry because no tests so it was decided it was better this way.

Management has no idea on code state, it seems team lead is lieing to them about things like having any level of tests.

Management hire devs that claim to be experts but then it turns out they have basically no knowledge of what they were hired to do, even don't know what json is or the framework or language they are hired for, but we just leave them to get on with it and again make prs too big to review.

Honestly I have no hope that this will go well now but I am morbidly curious to watch. I've never seen anything like the train wreck that we are about to get experience.

Spent 5 hours working on a solution for a hash difficulty comparison/scaling algorithm. after a bunch of different iterations and approaches, I find that my problem can be solved by the attached equation. Its such a simple answer but no way in hell would you be able to discern the amount of time and brainpower that was put into it. The git commit is literally 10 lines of code total, but I guess its not about the amount of code, but the time spent thinking about it thay counts?

Boss: Where should i put this piece of code so the android app will work correctly?
Me: Maybe here and we run some tests.
Boss: What? You built the app so you have to know where I should write the code for the endpoint and your app will work. No time for tests. And no update.

Fuck you boss.

I hate my freelancer life.
1. No weekends
2. No particular time to close
3. Work for 12 to 14 hours without sleep sometimes
4. Keep explaining the dumb clients about how development is not wordpress.

Its all fucked up. I have no life.

My average Lines of code this month is around 700 LOC/day. Whereas the average that showed on internet is 100 LOC/day.

I have choosen a hellish life.

I worked with a developer for months. He was senior to me; on more money than me and had way more experience. I spent at least 25% of my time explaining the most basic stuff to him. Things like 'no, that's not how a cache works', 'no, you shouldnt be doing string concatenation inside a loop', 'no you've completely written the wrong thing because you didn't listen'

When he left, he claimed to have finished off a feature for our application. We dove into it, rewrote it, made it more efficient, the code cleaner, the documentation more succinct and the logic more obvious. When I say we, I mean me and a student, and by me and a student, I mean the student with some very light prodding from me.

Fuck. The entire day to do this shit.
The screen was my first experiment, but because of a bad module (i2c) it didn't worked.
Today I finnaly got it to work.
Starting making everything almost like in the picture, everything mounted (and lots of black hot glue, no wires showing...
Didn't work.
One hour breaking everything apart without damaging the screen... Was a loose wire.
Started again... Didn't work...
The pot is also damaged, sometimes it works, others need to turn it hard.
New pot.
New set of wires.
Soldering everything right, testing all wires so no mistakes this time... But it takes so longgggg... Making everything in modules this time (to reuse without having to sordering again. And finally... It works.
By this time I should have 3 or 4 learning projects finish (I really wanted the screen to adapt all output in text, no serial, no blinking less, everything in modules, code prepared so, when I get my 40+ packages from China I already have a prototype tester ready.
10 hours... Fuck I'm really addicted, or else I would just solder everything together :D

Forgot to change code in my api for rate limiting, after development. No unit tests.. because who really needs that right? 🤦‍♂️🙅‍♂️🤷‍♂️lolololol

Long story short, API went to production eventually, and stopped working almost immediately. Rate limiting was set for 2000 requests in a 1 hour time period. Not my finest moment.. fml 🤦‍♂️

Parts of the code I am working on date back to the early nineties, written in ancient C++ with lots of special cases for ancient compilers by people with 0-2 years of coding experience.
My favourite coding moment is every time when after refactoring a part of the code, it has about 1000 lines less (no exaggeration), is more reliable, AND can do a lot more than before.

After a long time I finally reached this milestone of 100% code coverage. I often asked myself why I had to test every function, no matter how small. But this log output of 100% was worth it.

I am currently refactoring some code which exists before my time in this company.
The code was so inefficient before. To put into perspective for every function call it used to loop through some data 100+ times .
I replaced it with a map and voila, no more loops anymore.
The person who wrote this code don't even realise how bad his code was. He sits besides me writing more stupid hacky code for other parts of the app.

"We need this project done by friday"

When:

Requirements changing on a daily basis.

No standards whatsoever, anywhere.

5 different people commiting changes with no code review.

Original team leader quit a month ago.

Current team leader doesn't know our own deadlines.

QA looking at layout through a microscope at every single possible resolution. (please move this 2 pixels to the left between 934px and 936px range)

QA being too vague some times (this looks weird some times)

Same thing being changed back and forth because no-one could agree on how exactly should it look.

PM implying at every chance that I did nothing and what little I did broke everything all the time.

I was mentoring a group of students and helping them with their graduation project. I taught them NodeJS, MongoDB & few other things.

One time, one of them came to show me her code, and it has the weirdest and most bizarre structure ever!

I asked her, “who told you to structure your code like that? This is wrong! I didn’t teach you this way!”.

She replies: “<<a local shitty tech startup name>>’s CTO”

When I searched about him, he’s a civil engineer who founded a startup and assigned himself as CTO with no technical background or knowledge whatsoever! FFS students believe that he’s a real CTO and started learning from him 😑 His code was so bad in every way that a fresh would write a better code!

Can anyone tell me why is it good to use some crap language that transpiles to javascript? Yes i hate js too but 90% of my time using reason/ts/elm is just

>ddg how to do x in y
>no answer
>Js.unsafe.eval "js code"

Like???? None of them is a 100% complete wrapper???

Boss: look we have only VR projects this year. You need to learn Unity.

ME: NO fucking way..... FUCK You unthankful PRICK. I'm not going to learn your fucking unity bullshit after all those backends, mobile apps, code I've wrote for you? I FUCKING HATE UNITY. Time for a new job I guess.

A tutorial app that convinces everyone to adopt UTC (so I no longer have to account for time zones and/or DST in code.)

So I wrote a python code and was waiting for +1 on code review and I needed to merge it fast. That shit of a reviewer took his time to finally NOT give a +1 with comment, "if statement has no else part". OF COURSE IT DOESN'T HAVE ELSE PART. I DON'T NEED A ELSE PART. But to give him the benefit of doubt, I'd like to ask devRant community if they believe all ifs should have elses.

I've been working for the last 5 years on some large legacy code used in production, more than 100K LOC, poor comments (when existing) often outdated, huge parts of code that can no longer be reached, over-engineered class hierarchy, functions of thousands lines, huge parts of deprecated code that cannot be removed because "someone might still be using it". Statistically, every small change caused 3 new issues somewhere else and every bug fix or new feature required 10 times the time that would be necessary with a decent codebase. But after five years in hell I can finally say that... Oh wait, nothing changed, the code is still legacy and nobody is going to do anything about that.

Started a new job last week. Pays a tad below average for position, but i get training time and budget for anything i want.
So far i have had few days of company introduction, and now a week for training courses related to position.
I have not seen any code yet, brought no value in, just joined.
Massive green flag to me.

I want to lose some weight and tone some dormant muscles. So I decided that I'll do some pushups and crunches every time I run into a bug with which I'm struggling. Seeing as I write more bugs than stable code, I should be ripped in no time.

I almost always program in Ruby but every single time I switch over to JavaScript, I cannot stop adding semicolons to my Ruby code for hours. Brain, y u no readjust!?

What the hell is wrong with using GitHub, or Git??? A client told me he’s concerned because it’s been, in his words, “compromised” and the admins can “see our code for trouble shooting purposes” and he doesn’t feel comfortable with that…🤨 like…no one wants this code my dude, like the fuck!?! We’re already using a skeleton project from someone else’s git, yet you dnt want this project on there??? Ooooor, is it because you dnt know how to use it??? Nor do you want to take the time to learn it??? 🤨 fuck boy. 😡😡😡😡😡😡🤬🤬🤬🤬🤬🤬🤬

As much fun it is to code and create new features for users. Take a break from the computer and spend time with real people.

A few years ago I would stay at work to get tasks done. While everyone in the office would go home I would stay and finish some task. After doing that for a few months my wife started to yell at me.

It made me realize that no matter how important a new feature, a bug or optimizing code is family and the relationships you have are more important.

we had a front-end dev that needs to "re-architecure" his codes when we need to add a small change or a feature.
and im like: wtf is wrong with your code and you need to re-architect it every damn time?!

PS: that dev is no longer with us now. thank god.

So I got this new job as Java developer, the people are really great but is the kind of companies that only takes care for fast results and not for code quality.

Because this I have to deal with libraries updated 4 years ago, classes with 8000 lines, methods with 500 lines, a WHOLE lot of work arounds because there is no time to really fix the issue unless it affects directly the customer (something not working or being really slow) aaand we use fucking svn.

Some of this practice's they know and encourage it (+1000 lines classes for example) and every time I try to talk about good practices in the code everyone seems so interested but there is always no time.

Sooo I will stay here for at least two years, I hope I can make a change for good in their code smells.

// example.json
{ "hasCustomerAgreedToTermsAndConditions": no }

Slightly irritated by my IDEs warning, I squinted back at my code. It took me a second too long to spot my mistake. First, I was baffeld at my own incompetence. Then I grew defensive about it. "Why not?!" I thought. "Less typing, so efficient, so much time saved, so wow!"

I realized at that moment, that it was probably best to call it a day and go to bed.

And so I did.

One word rants really .. just piss me off ... like omg ... you can't take the time out to actually have an opinion !

Eclipse ... no that not a rant it's a hateful pies of sh1t which supplies you a default view of code which makes you feel like you are a pirate looking though a portal to an island 10 miles away ..

Soap ... that just the annoying mechanism you will use and and swear at and every time you use it it's different ...

Sql ... that's just something you should learn ... learn it .. it's useful ..

Ok so you're a pretty good programmer. You don't take time to grasp stuff, but then we all know there are times when we all fail to understand certain things. But why does that 'making a fool out of yourself' incident HAVE to happen when your colleagues are around?
Scene 1:
Coding alone, no bugs at all. Perfectly optimized code. Runs with no compile-time errors or warnings.
Scene 2 :
Typing code. Colleague enters my cabin. Before even I execute it, finds 300 compile-time errors. All of them happen to be true
Judged for life..

Why, oh programmer god, why?

Being lazy taught me more about (code) automation that years of study ever did.

“Ugh! Updating translations is boring, why do I have to do this manually?”

“Damn I really hate having to remember endpoints”

“Oh, come on! Its the third time I initialise this the same way!”

I’d love to say this is a motivational speech or something but no, im just lazy lol

So... My boss is "hard working", meaning that she'd rather edit and upload a html file every morning at 5am for the last 5 years and manually send a push notification notifying the user that the new file is up than learning a little bit about automation (cron? IFTTT?) and even after letting her know about those options she has "no time"

She'd rather keep source code (pug, sass), manually build on local computer and upload to live servers instead of learning git and letting me setup once and for all CI/CD

SERIOUSLY!?!? NO TIME!?!? But there's time to do things at a turtle pace like in the 90s... 🤦‍♂️

when you get to Friday and realized you've had almost no time to code this entire week. There is always next week.

God I hate my job I hate my job I hate my job.

I know that you are supposed to make more than what you have been hired in the first place today, especially in tiny company, but I expected to code a little bit...
This week, all I have to do is to deep-etch pictures in photoshop, send packages, answer the phone, do the SEO and be the community manager on Facebook. No time to code at all.

I just have to stay till august, then I will finally be able to switch company. Please make it fast...

Started a contract about 7 weeks ago now and initially it was great. The boss man was out of the office the majority of the time so I was able to get shit done.

Now the boss man is in the office all the time and I can't have a technical conversation with another dev without him jumping in to explain why we are wrong.

He has no technical experience to speak of and so I now have to explain every technical decision to someone who thinks you can put php code into javascript.

Maybe this is rubber fuck debugging?

Now I just keep telling myself "it's only 4 more months..."

Whenever I have to ask about how certain code of someone else works, I feel bad. I feel like I should be able to figure it out on my own.
On the other hand, if people ask me to implement something within their code, that I am not familiar with, I kinda expect more info? Like if you don't have any tutorials or documentation on your tool, be prepared to answer some stupid questions about how to set it up and whatnot. How else am I gonna know how to start with? Having to read the entire source code is a massive waste of time, no?

tl;dr: if you don't provide documentation or tutorials, be ready to answer stupid questions.

<insert obligatory "long time lurker" statement here>

Started a role about 6 months ago. I'm the sole IT programmer. A bit of the mess I inherited...

- 100+ stand-alone applications/tools (luckily most of them aren't too big).
- No documentation.
- Some applications' only copy of the code exists in production.
- We only have production.
- A single file consisting of 30K+ lines of VB. Little to no comments. The one comment at the top says to keep old code by commenting it out and state what you changed.
- Previous devs didn't like foreign keys.
- No. Fucking. Version. Control. At. All.
- And so much more...

Luckily I was hired due to my experience so I could fix all these problems. Its actually a really great job.

i was having a really hard time because there was no record of changes in code, the boys would communicate changes in private and I'd spend hours trying to figure out why i couldn't compile. when i asked my boss that they put that info somewhere, he said it was unnecessary and that it always worked that way before i came. ofc it worked, it was 2 guys coding. i couldn't work properly and everything took forever to sort, no one tried to help. i went to hr and they just told me i was right and that i had to be patient. i quit soon after

Spending 2 days trying to figure out why code signing wasn’t working when deployment is started from teamcity. Every time I tried manually it worked, but through teamcity it just kept telling me that no certificate could be found.

I finally twigged what the problem was, my code signing certificate is smart card based and you can’t access it if is requested from a RDP session. I had launched the teamcity build agent from an RDP session a few days back without thinking…

Rebooted and started the buildagent via VirtIO VNC and low and behold it started working again.

Be me, get a consultant job, go to a supposedly great client that has fame of getting scouted by Google. (attn: I doubted all this shit before I started)

Learn the basics by a awesome mentor and trial/error stuff at the same time to get the hang of things, after that was done, I noticed there was no documentation whatsoever, code is spaghetti and your documentation, good luck!

Royal spaghetti, you can't make heads or tails of it, dev code in production, empty try/catch blocks, empty statements, if (true)... (incl. their core classes)

Keep in mind this is a multi milion dollar company...

Someone please understand my pain...

When you have no work all week long because you finish 3x as fast as the estimates. You ask for more work, and due to "red tape" you can't even work on the back log.

Time to sit and look busy :).

Sadly, this is too common for me... I want to be buried in code and tasks! Not sit and twiddle my thumbs.

Null Pointer Exception

Null Pointer Exception,
you're in a class of your own.
I will try and catch you,
each instance you're thrown.

Null objects expel you,
because you are vile.
I dread that I'll c you,
when I attempt to compile.

Like the grim reaper,
you destroy lines of code.
And so to you,
I dedicate this ode.

You have no remorse
for those who won't test.
As a result,
I need to confess.

From time to time,
when there's no time waste.
I must rely
on cut and on paste.

Although we're acquainted,
I really must mention.
You're not my friend,
Null Pointer Exception.

You all know that these AI dev tools are reading your code right?

It is sending it back to a data center and doing evaluations on the code. This is like handing your code to an unknown entity with no guarantees for privacy or copyright protection.

This concept bothers me and I would have to consult with my employer to even determine if we wanted to take that risk. I think it is just a matter of time before a bad actor takes advantage of this and rips off a company somewhere.

What is worse than React native? A crash in flutter ....

They need to work on their stack trace all it's errors lead to framework assertion failed, but which fucker in my code caused it....

No one knows, time to play cat and mouse with this thing 😒

Made this amazing discovery in my project. Made sure to commit the code in Git to show a demo to the manager.

Could not find the code at all when it was time for the demo. Checked all the commits to find out, nope, no luck.

Later realized I committed that code to special branch :/ And I totally forgot about that :(

Working on codebase of a 20+ year old system that the company I work for bought five years ago and in that time there’s been no refactoring, no security updates, no attempt to create automated testing (there is none), new features have just been built on the codebase with no regard for quality and it’s just spun into the horror cesspool that it is today.

I joined one year ago and I’m slowly refactoring the codebase and updating it to get it to a more modern codebase, cleaner code, faster load times and creating a ton of dev documentation so the devs in India can start getting into best practices and start producing quality code.

WRITING CODE ON PAPER...smh

I know many people wrote about this already, but writing code on paper is one of the worst things of a CS class. I’d rather get a computer with no internet access and use a notes app to write code instead of having to write everything by hand. It takes so much more time that you could spend thinking about the problem. Not only that but also my hand gets tired of writing...ughhhh

I need to convince my teacher and the school to switch to writing code on computers! I will not loose this battle ahah

Have you ever committed to an impossible deadline simply because your client would have been completely FUCKED if you didn't?

this would have been remotely doable if the existing code base that was handed over was just mildly reasonable. But how could this shit ever have worked the first time?!

Gilfoyle would just have said no. Why can't I be more like Gilfoyle >.<

Every morning I start visual studio code from cmd... So I wanted to make a script to open that specific folder and start it in code...

The time I spent trying to make this thing is longer than the time it would take me to start code every morning.

Guess I'm no hackerman :/

Finally code start working fine no bugs, no warning just working.

Moments later!

start to compile again but this time either with warning or with bugs. Anyone?

Agile my ass.
What has become of: "Individuals and interactions over processes and tools"?
A fuckton of rules and processes to do it the 'right' way: tickets, estimations, hours of sprint planning. Yeah, we're so professional we no longer have time to write code.

Note: manifest was mainly full of fluffy business buzzword bullshit (effective sustainable excellence), but one thing resonated:
>Simplicity--the art of maximizing the amount of work not done--is essential.

(I cherish every line of code deleted or unwritten, so it needn't be maintained)

Man I'm only 4 years in and I'm so tired of writing bullshit code that no one cares about. How do people do this for 20 years. I don't know. Motivation is at an all time low. It seems stupid to me that instead being out there with the butterflies I am dying staring at a rectangle for days on end. FML.

Wish me luck. Looks like the feature I am developing is going to be late because QA doesn't feel like following the estimates we agreed on. We already identified that development was going to be the longest part of this whole effort and that QA was going to be relatively easy, but but no. Because this is the day we have to be "code complete", they don't want to test a relatively simple feature. In fact we had to talk them into even starting testing on it today. Even though regression day is Monday and they are basically going to be done testing their last ticket this morning. Like what the fuck were they going to do for the next 7-8 hours? They don't write any documentation. There are no reports to do. There are no meetings. Did they just want a virtual day off?

Edit: they are literally playing with people's careers here. This is not the first time I have had something delayed by QA even though they agreed that it was simple to test and it was delivered with enough time to fucking test. Then I get in trouble because of late delivery.

A house.. or lego star destroyer..😝😆

Joke aside, I'd rewrite current project from scratch to get rid of all the automation and IE dependancies and make it cross browser and all the dead code...and all excess ORMs and especially EFCF..and also make support for db diff than oracle..and no need for ora client installation..

Yeah, I'm a work junky, I have no projects of my own.. one kid is demanding enough of my time.. 😉

GOD I FUCKING HATE UNITY AND FUCKING C# SO MUCH
EVERY TIME I TRY TO MAKE IT DO WHAT I FUCKING WANT IT TO IT'S LIKE "mmmmmm nah lmao" LIKE FUCK WHY CAN'T YOU JUST FOLLOW FUCKING 3 LINES OF CODE NO MATTER HOW I PUT THEM OR ORDER THEM YOU BRAINDEAD FUCKING PIECE OF SHIT PROGRAM

My colleague told me today that companies with shit code quality, complete chaos, no tests of QA of any kind, and poor security practices still make loads of money and are extremely successful so it's all a waste of time.

I detest this idea and I refuse to work like that anymore. But I also think he's right :(

For the first time I have got an opportunity to have an internship at a local software development team and they are asking for program samples now... I am a little nervous because I have never shown my code to anyone who understands anything of coding and I have no idea how it would do in an interview...

Imagine a time when a colleague contributes a shitty spaghetti of non-optimized code that neither use mnemonic variables nor conventional naming of functions, and you can imagine the dark hours of maintaining it and your fingers itch to fix it but you don't have the time and the responsibility too to do it. He doesn't listen to you and you feel bad to tell this to the boss as the colleague is also a friend you've known since college and is a good person otherwise. No options seems to give peace.

The worst rejection was one after a first interview and a subsequent 3 hour code challenge. I was super nervous as it was my first code challenge in an interview that was one of my first. I wasn't confident when I submitted my work, but the time was up and so there wasn't much to be done.

The rejection was simple. Pure silence. No arguments, or feedback. Just didn't hear nothing back and that didn't help my fresh out of university self-confidence.

Why is sleep not a choice. I have code to write but my body and mind wont let me stay up.

Too many projects so little time

No one to help 🙃

Sleep is really a devs enemy 🙆🏾‍♂️

Just had a class where we had to write a heap adding algorithm in Java to reduce rounding error for x amount of floats being added together

After an hour of writing code with no testing anything I finished. Ran the JUnit tests provided by the teacher and it passed all the tests!

Who says it can't work the first time?

Finished exams, in 3 days i have a flight to my parents house to see them.
Before that, thought about comming to my grandma's home, which has a beach nearby so i can spend 1-2 days relaxing.
Came here. No one is home. I don't have keys either. I'm hungry too.
Fortunately the wifi signal is ok.
Sat in front of the door, and opened my laptop.
Time to start migrating my projects from duck to static typing and practising my ability to write python code with type annotations until someone comes home.

How greedy can you get?

> boss takes half assed gdpr project : branch xyz
> branch xyz requires deprecated version of npm/node
> I re-install node this time with deprecated version
> Wow this node is configured with ant build
> ECMA 5, config but code is shit as fuck
> still I get the job done , cannot test it because code is shit as fuck and I will never any thing to fix that un healthy code
> code doesn't run on client side,
> no shit Sherlock
> get a call from boss, it urget look in it and fix it

Working for one of our oldest customer, in some serious old, ugly and outdated code(web service).
The dev db doesn't contain any relevant data.
The QA service points to production, so can't use it for any tests.
My contact, at the customer, is going on vacation tomorrow.
Their pm is going on vacation next Friday.
No time for refactoring, db data updates or otherwise do important and much needed updates.
They want it to be done yesterday.

FML.

I don't care about your good ideas.
If you don't code, don't art, have nothing to contribute to the work, and aren't going to pay me for my time, then there is no collaboration.

WOW Xcode is such a trash fucking application, I am so pissed at how much I have to fight this damn piece of shit program to get my work done

The time it takes to index my code is disgustingly long, I sit and sit and wait for it to FINALLY recognize I've added a new variable to the header file before it can begin to suggest autocompletions, but wait??? Why is it telling me there's errors about another variable? On a line of code that doesn't even fucking mention that variable??? BETTER WAIT IT OUT FOR IT TO INDEX SOME MORE, NO XCODE MY CODE ISN'T ERRONEOUS, YOU ARE YOU CRAP SHOOT!!

AND WHY WON'T YOU LET ME SPLIT VIEW YOU WITH ANOTHER APP??

Asked to do overtime so I do. Everyone has gone home and now it's time for me to go home, so I go to leave the office to find the gate padlocked. I'm stuck. There is a side gate for cars that has a security code but I have no idea what that code is. So I end up waiting around and stalk the cleaners car out of the gate 'sigh'.

Does anybody has an idea what to "code" when you have too much free time? I am done with school and waiting for my university acceptance. No Websites.

TL;DR
Project ideas?

So. It is that time again. The last week of the semester for college students. Paper due for all, presentations for everyone and their moms and final in a week for which no one had the time to study and I'm here wishing death so I can code in piece in the afterlife.

Refactoring/cleaning old code.. Found this gem:

$hour = substr($obj->hour, 0, - 3);

Turns out, hour was saved in the database as a TIME field(DATE was saved in another column) , and the previous genius dev was trying to output time in a H:i format...

No wonder php has such a bad reputation...

Agencies... Just hate when people are given only time enough for doig crap code, because "there is no budget". Hate even more to work on changes on top of it, because people just dont get why you take so long to do changes that supposed to be simple, ignoring the fact that previously they asked for some slap-dash shit. What do they think, that with time the code cleanup and tidy up itself?

Anyone who formats their code manually is a fuck there I said it.

Also stop using a tool that has no contextual understanding of your code. You're wasting more so much fucking time trying to guess shit that an ide would automatically know and doing stuff that an ide would automatically do.

So I just spent 3 days trying to write a custom WordPress query with WP_Query and limit the result set with tax_query. I wrote my own code, copied and pasted code from the docs and watched a couple of tutorials, no matter what I did my results just weren't right. Turns out I was calling my code too early so my tax_query was being ignored.

Time wasted or lesson learnt?
.... I'll take lesson learnt. Oh well.

My Gripe With Implicit Returns

In my experience I've found that wherever possible code should be WYSIWYG in terms of the effects per statement. Intent and the effects thereof should always be explicit per statement, not implicit, otherwise effects not intended will eventually slip in, and be missed.
It's hard to catch, and fix the effects of a statement intent where the statement in question is *implicit* because the effect is a *byproduct* of another statement.

Worse still, this sort of design encourages 'pyramid coding recursion hell', where some users will first decompose their program into respective scopes, and then return and compose them..atomically as possible, meaning execution flow becomes distorted, run time state becomes dependent not on obvious plain-at-sight code, but on the run time state itself. This I've found is a symptom of people who have spent too much time with LISP or other eye-stabbingly fucky abominations. Finally implicit returns encourage a form of thinking where programmers attempt to write code that 'just works' without thinking about how it *looks* or reads. The problem with opaque-programming is that while it may or may not be effortless, much more time is spent in reading, debugging, understanding, and maintaining code than is spent writing it--which is obviously problematic if we have a bunch of invisible returns everywhere, which requires new developers reading it to stop each and every time to decide whether to mentally 'insert' a return statement.

This really isn't a rant, as much as an old bitter gripe from the guy that got stuck with the job of debugging. And admittedly I've admired lisp from afar, but I didn't want to catch the "everything is functional, DOWN WITH THE STATE" fever, I'm no radical.

Just god damn, think of the future programmer who may have to read your code eventually.

Since ive started college my will to program has become non-existant. Im a self taught programmer since 12, it used to be MY thing and i loved it. I used to spend hours a day just programming personal projects because i love it. However since college has been getting serious with this being my junior year and having part-time contract work i dont "love it" as much. Im a little scared, i have no time to just code for fun and when i do have time it feels like work because thats the only other time i code.

What should i do guys, i dont want to fall out of love with programming, it's part of who i am and i can feel im losing it.

Now I didn't do this myself, but I've heard from a senior developer that you can modify C's if statement to require an ADDITIONAL 99% chance, making the code fail 1% of the time with no explanation.

Today I wrote the most epic code.

The kind that breaks your brain, but when you're done with it you know it's time to go home and kick back coz you've done good.

It used recursion, did backflips to avoid unnecessary db calls, featured no code repitition. Hell I even commented the business rules it was following in there to explain what was happening.

I hope it works tomorrow when I test it 😂😂😂

Stupid stupid university custom exam IDE... first thing select a few lines hit tab oops replaces code with tab character... compile is alt+C and run is alt+R (never seen that before) and you have to go save -> compile -> run.. instead of just hitting run and last but not least it syncs your code with the server so every save file takes 3-5s at which time the editor freezes

ALSO NO DEBUGGER OR JAVA CONSOLE...

My boss is being a stupid cunt. To give you a background we were facing issues with our Collections system. First week December 2019, I and a colleague of mine came up with a new efficient collections architecture. My colleague and I started to Code and create automation scripts mid December and completed it in First week of Jan 2020. This PoC version was supposed to be just between the Dev team(App Dev and Back end, also one from the Ops side to verify the data). I did not receive any feedback on the actual collections system and the data integrity but during this time all they’ve done is take meetings with no real outcome. I raised this and the only email I got is data is looking fine when I know it is not.Now in First week of Feb, he is stressing us to go ahead and deploy the architecture in Production and we have not done any Code Review, Static Code analysis, any real tests on Code and deployment scripts. Have not discussed any metrics for our dashboard and alerting. I have no idea how to handle this cunt. I have even asked for resources to atleast productionalize the code and move ahead the deployment and still no out come. I’ll go in a meeting with him in an hour, I will be very blunt and tell him that whatever he is doing is a foolish way and maybe resign in couple of weeks

Person : Today you worked for 18 hours. What did you accomplish?

Me : I did no progress in the code base.

Person : How is that possible? You were on the IDE all the time.

Me : When you have a huge package pulled in, that takes 3 hours to build, for every single change you do,

And the build path is screwed :D

Once I maintained one of the most used and fucked up codebases on the market with almost 1M+ daily users. (cannot say more, sorry).

It's written in PHP and is absolutely terrifying,
the first time I saw some lines of code I was about to scream and cry.

- spaghetti code
- no indentation
- random SQL query unoptimized
- unused vars
- Code is split among several files with no logical reasoning
- Mixed procedural and oop programming
- Unsanitised user input (yes, you got it right)

No test environment, no backup database, every commit goes straight to production.

It's a real disaster but the company prefers to keep it as it is without refactoring or anything else.

Just to make it clear:
It's not hatred against PHP, it's against the code's current status and the older programmers which used to work on it.

Moved to a totally new city to start a new job, thought it'll be amazing as the company is good. Came and saw a bunch of motherfuking smokers who smoke at the main gate of the office, the HR does not respond to my queries, doesn't have time to interact with a new recruit, and I have still got no company mail or email id. And oh, I have the entire GitHub access and the android code cloned on MY PERSONAL COMPUTER, the rights to which were given by the CTO himself.
Guess what, time to say bye to this shit. I'm moving back.

One of professors has an interesting philosophy in regards to how software is planned. He makes us forget that we dealing with a computer and has us write instructions as if we are teaching a human (no optimization, binary, or unnecessary numeral variables). Then we change it into code, then we optimize it. Every time. It freaks me out, but it gets us thinking. Not sure. If that is genius or insanity.

Tbh this is more about education in general... Introduce the same system i had, no fixed lessons just a project and a time frame. Eg : create your own MVC framework and a site to show it off

Time frame : 5 weeks

(dont expect fully fletched frameworks but a site that uses the MVC data flow and the code is reusable)

For some reason I keep over engineering stuff to the point I spend 2 hours thinking the best way to do something. I'm making the backend for a project of mine and I wanted somewhat decent error handling and useful error responses. I won't go into detail here but let's say that in any other (oo) language it would be a no-brainer to do this with OOP inheritance, but Rust does OOP by composition (and there's no way to upcast traits and downcasting is hard). I ended up wasting so much time thinking of how to do something generic enough, easily extendable and that doesn't involve any boilerplate or repeated code with no success. What I didn't realize is that my API will not be public (in the sense that the API is not the service I offer), I'm the only one who needs to figure out why I got a 400 or a 403. There's no need to return a response stating exactly which field had a wrong value or exactly what resource had it's access denied to the user. I can just look at the error code, my documentation and the request I made to infer what caused the error. If that does not work I can always take a quick look at the source code of the server to see what went wrong. So In short I ended up thrashing all the refactoring I had done and stayed with my current solution for error-handling. I have found a few places that could use some improvement, but it's nothing compared to the whole revamp I was doing of the whole thing.

This is not the first time I over engineer stuff (and probably won't be the last). I think I do it in order to be future-proof. I make my code generic enough so in case any requirements change in the future I don't have to rewrite everything, but that adds no real value to my stuff since I'm always working solo, the projects aren't super big and a rewrite wouldn't take too long. In the end I just end up wasting time, sanity and keystrokes on stuff that will just slow down my development speed further down the road without generating any benefits.

Why am I like this? Oh well, I'm just glad I figured out this wasn't necessary before putting many hours of work into it.

!!rant

Today I wanted to finish a feature in some Python code I. Working on instead I scope creeped myself a bunch times adding "other cool features" and refactoring working and readable code that didn't need refactoring. Oh and learning about random things on SO and finally giving up on making any more progress for the day and reading devrant.

ADHD Self:"Coding is love, coding is life. Plus I'm getting paid."

....

Responsible self: "Wait no, go home sleep, spend time with your wife"

Remembering self:" she's out with friends"

Responsible self: "ah, carry on, she's probably spending more money than you're making"