First rule of debugging
Run it again

Thats me....

Don't update your pull requests half asleep, I repeat don't.

Now it's 2 AM, I am fully awake regretting my decisions.

Was part of a meeting where the TL was discussing ideas for a product based on a new technology, I had read and played a bit with it myself so added a few cents, here is what unfolded:

TL: Great that u know abt this why don't you build a poc.
Me: It's simple to get this poc working, but how will we monetize this?
TL: You don't worry abt that, build a poc.
Me the next day: Here is the poc you asked for.
TL: Great so this can work let's release a basic version soon, so any ideas on how we will monetize this?

Going through some pretty fucked up shit right now : a string containing an SQL query goes though a 100+ lines function full of if{} else{} with up to 5 levels of indentation, where it replaces some parts of the query with other words... 😱

My brain: Its a company that works with web technologies and the job is more of a devops job they wont expect you to know cpp compilation process.

Interviewer: Last question tell me in detail what happens when you compile a cpp program.

My current job makes me want to question my life choices.
Its a complete burnout.
I do 9 to 6 never 6 though its always 7 or 730 come home exhausted, and still on almost all days need to attend to customers after hours. Customer meeting at 8.30pm are quite consistent occuring. Being a developer, debugging meetings I can understand to a certain extent, but why the f i am preparing quotes and pitching products.
Want to prep for new job boom no time left to do so other than weekends.

When you make a typo in a command and spend 20 minutes googling why it isn't working trust me its time to sleep and reboot.

Senior dev: Complete task and raise PR immediately
2 week later: No review
FML

So I am a Software Engineer at a small scale company.
I need to coordinate with customers, understand the requirements and design and develope the solutions.
These sometimes include changing the current product a bit and customize it to fit the client needs or maybe creating a plug-in that could work with the current product and get the job done.

I love the research, design and planning part of the job, I would be super focused and will find solutions for complex stuff. Plan it all to the smallest things.
I know the solution so I can think of what code would be there what would be needede whats already there etc.

But when it comes to coding the solution my laziness kicks in.
My mind is like you already know the solution why you need to code it to.

Then I start procrastinating and end up putting myself under a pile of stuff when the deadline approaches.

FML

Today someone found a 0 day in our trialware which allowed some of the main features to work even after its expiry.
I mean what do you expect when you create a shady system for trialware.
It was fun to watch the lead dev of the trialware panic when it was confirmed.

Tomorrow's standup is gonna be fun.

Spent almost a month writing real time sync between two platforms for client. Changed it n times to fit their custom conditions. They tested it for real time sync.
Now suddenly their requirement is to have scheduled sync and it is "As we discussed in the beginning".

The js issue i have been fixing since yesterday was a database issue from the clients environment.

FML

I have been tasked with planning a feature retirement.
Basically the plan is to move this feature to another plan where it makes more sense and is more stable.
Now we don't have any data on how many or which customers are using this. And I need to plan a migration for them.
Fun times ahead...