I used to use Firefox few years ago, but people around me called me fool and told me that Chrome was much better.
Now I use Chrome and you devRanters are making me feel like fool again.
Lesson Learnt: Stand straight on your decisions

I was offered to work for a startup in August last year. It required building an online platform with video calling capabilities.
I told them it would be on learn and implement basis as I didn't know a lot of the web tech. Learnt all of it and kept implementing side by side.
I was promised a share in the company at formation, but wasn't given the same at the time of formation because of some issues in documents.
Yes, I did delay at times on the delivery date of features on the product. It was my first web app, with no prior experience. I did the entire stack myself from handling servers, domains to the entire front end. All of it was done alone by me.
Later, I also did install a proxy server to expand the platform to a forum on a new server.
And yesterday after a month of no communication from their side, I was told they are scraping the old site for a new one. As I had all the credentials of the servers except the domain registration control, they transferred the domain to a new registrar and pointed it to a new server. I have a last meeting with them. I have decided to never work with them and I know they aren't going to provide me my share as promised.
I'm still in the 3rd year of my college here in India. I flunked two subjects last semester, for the first time in my life. And for 8 months of work, this is the end result of it by being scammed. I love fitness, but my love for this is more and so I did leave all fitness activities for the time. All that work day and night got me nothing of what I expected.
Though, they don't have any of my code or credentials to the server or their user base, they got the new website up very fast.
I had no contract with them. Just did work on the basis of trust. A lesson learnt for sure.
Although, I did learn to create websites completely all alone and I can do that for anyone. I'm happy that I have those skills now.
Since, they are still in the start up phase and they don't have a lot of clients, I'm planning to partner with a trusted person and release my code with a different design and branding. The same idea basically. How does that sound to you guys?

I learned that:
. No matter what happens, never ignore your health for anybody or any reason.
. Never trust in business without a solid security.
. Web is fun.
. Self-learning is the best form of learning.
. Take business as business, don't let anyone cheat you.

Lesson learnt :
Never ever do "rm -rf <pattern>" without doing "ls <pattern>" first.
I had to delete all the contents of my current directory.
I did "rm -rf /*" instead of "rm -rf ./*".

never mess with GRUB!
lesson learnt -.-"

Story #1: So I took a month of parental leave. And was planning to extend it a little longer to deal with my final exams. I was planning to spend lots of quality time with my wife and newborn son. Little did I know... It turns out that out of 5 OoO weeks I was looking forward I actually had 3 at most. The rest I've spent working remotely as I was insisted to deploy a brand new and poorly tested feature to PROD 2 days before my paternity leave. So I spent 2 weeks debugging things in PROD. Remotely. Needless to say that did suck.

Story #2: After story #1 I've learnt my lesson. This summer I took 3 weeks annual leave to renovate my apartment. I asked to not to be disturbed unless there's an emergency. And an emergency it was. One of our app users had a planned hi-load batch job lasting for 2-3 months. Hundreds of thousands of items had to be created and processed. It turns out the _processing_ algo had some flaws and was acting out. I was called out and asked to assist. I knew this sort of debugging is going to take a lot of my time so this time I put my conditions on the table: I will assist but I'll extend my leave by 1.5 the time I spend working now. They took the deal. Instead of 3 weeks I had 5 weeks of vacation!

I don't care that much about my salary. I prefer to exchange it for my time off hence I didn't ask for compensations.

Bottom line: NEVER EVER underestimate or undersell your time and effort. You are a valuable asset and if the team/client needs you on your day off -- make it count. Your time off is YOUR time. Never forget it.

One of our newly-joined junior sysadmin left a pre-production server SSH session open. Being the responsible senior (pun intended) to teach them the value of security of production (or near production, for that matter) systems, I typed in sudo rm --recursive --no-preserve-root --force / on the terminal session (I didn't hit the Enter / Return key) and left it there. The person took longer to return and the screen went to sleep. I went back to my desk and took a backup image of the machine just in case the unexpected happened.

On returning from wherever they had gone, the person hits enter / return to wake the system (they didn't even have a password-on-wake policy set up on the machine). The SSH session was stil there, the machine accepted the command and started working. This person didn't even look at the session and just navigated away elsewhere (probably to get back to work on the script they were working on).

Five minutes passes by, I get the first monitoring alert saying the server is not responding. I hoped that this person would be responsible enough to check the monitoring alerts since they had a SSH session on the machine.
Seven minutes : other dependent services on the machine start complaining that the instance is unreachable.

I assign the monitoring alert to the person of the day. They come running to me saying that they can't reach the instance but the instance is listed on the inventory list. I ask them to show me the specific terminal that ran the rm -rf command. They get the beautiful realization of the day. They freak the hell out to the point that they ask me, "Am I fired?". I reply, "You should probably ask your manager".

Lesson learnt the hard-way. I gave them a good understanding on what happened and explained the implications on what would have happened had this exact same scenario happened outside the office giving access to an outsider. I explained about why people in _our_ domain should care about security above all else.

There was a good 30+ minute downtime of the instance before I admitted that I had a backup and restored it (after the whole lecture). It wasn't critical since the environment was not user-facing and didn't have any critical data.

Since then we've been at this together - warning engineers when they leave their machines open and taking security lecture / sessions / workshops for new recruits (anyone who joins engineering).

Recently, our team hired an arrogant trainee-junior to the team, who turned out to be mean towards the other developers and in a habit of publicly mocking their opinions and going as far as cursing at them. He steals credit and insults others. He openly admits he's an offensive person and not a team player. When someone from the team speaks, he might break into laughter and say demeaning sentences like "that's so irrelevant oh my god did you really say that? hahaha". Our team consists of polite and introverted engineers who cannot stand up to bullies. Normally this kind of behavior won't be suitable even if you work in a burger shop especially not from a trainee. Let alone trainee, the rude behavior of Linus Torvalds was not tolerated, despite him being in the top position and a recognized star talent in the IT field.

I personally no longer feel comfortable speaking up during teams meetings or in the slack team chat. I'm afraid my opinions will be ridiculed or ashamed - likely will be called "irrelevant". I respond only if I'm directly addressed. We have important features coming up, requested by the customer, but I feel discouraged to publicly ask questions - I sort of feel having to regress into contributing less for the product. I also witness that other younger developers speak less now in meetings and team chat. Feels like everyone is hiding under the bed. Our product team used to have friendly working atmosphere but now the atmosphere is a bit like we're not a team anymore but a knot.

Lesson I learnt from here is: There is a reason why some companies have personality tests and HR interviews. Our proud short boarding process was consisting of a single technical interview. Perhaps at least a team interview should be held before hiring a person to the team, or the new hire should at least be posed a question: are you a team player? Technical skills can be taught more easily than social skills. If some youngster is unable to communicate in a civilized manner for even five minutes, it should raise some red flags. Otherwise you will end up with people who got refused from other companies which knew better.

!rant
I just attended a meet up yesterday and I learnt a life lesson by the speaker: "Never share two things is life. Toothbrush and database" 😂

I hardly use Windows, but had to book tickets using my friend's laptop who only had Windows.
So I switch on my mobile data, and the stupid shit just ate up all my data in updating Windows without even asking for permission 😣
Learnt my lesson

So one day on tech huddle my tech lead got frustrated, don't know why and told me - "the tasks you're doing can be done by interns"

I felt bad. Ofcourse I was putting my 100%.

That day I decided to put the resignation. I didn't discussed with anyone about it and sent the resignation email directly.

After serving 2 months of notice period I was able to land a better job successfully!

I called the lead on the last working day in that company and shared him the news about my offer letter and a little about the company.
His first question was - "Did you cleared all the interview process?"
In my mind - "That's only why I'm sharing the news here with you man! Stop thinking of me as a noob."
I replied with - "yes, if needed/the new company try to get feedback about me then please be honest atleast there by keeping your ego aside."

You shouldn't pull someone's leg if you aren't able to climb higher!!

Lesson I learnt;
DON'T STAY AT A PLACE WHERE THERE'S NO VALUE OF YOUR WORK AND THE DEDICATION TOWARDS IT!

Working in a startup isn't that easy, mostly for those where there's no work life balance.

Pro tip:

Make sure you can RECOVER from your backups.

It's all well and good backing this and that up, but make sure that when the shit really hits the fan you can recover.

I've now 4 days into recovering a raspberry pi that ran:
Pi-hole
Snort
DHCP
VSFTP
Logwatch
Splunk forwarder
Grafana

And serveral other things... I've learnt my lesson

Idiot people...
Today someone asked me how long I programmed for iOS, Told him I started really mastering iOS development since Swift was released, as I didn’t really focus on Objective C. He told me if I need any help, just ask him as he develops for iOS since two decenia... He calls himself a Senior web developer. First of all what has web development to do with iOS? And how the f*** can he program for iOS if it didn’t exist at that time.
It’s not because I’m a student I’m that thumb...
learnt the lesson not to believe everything everyone sais.

Lesson I learnt the hard way today: ticket every fucking task (including admin) to:

A. Cover your arse (if the tickets are not ready because they haven't given us enough information, push back on it before committing too much effort to doing it)
B. Better deliverable (what you output will probably be better quality because you worked out the requirements upfront + you know the audience)
C. You have something to show management when they want to try and overwork you some more

So I'm writing some multithreaded shit in C that is supposed to work cross-platform. MingW has Posix threads for Windows, so that saved already half of the platform dependency. The other half was that these threads need to run external programs.

Well, there's system(), right? Uhm yes, but it sucks. It's incredibly slow on Windows, and it looks like you can have only one system() call ongoing at the same time. Which kinda defeats the multithreaded driver. Ok, but there's CreateProcessA(), and that doesn't suck.

Fine, now for Linux. The fork/exec hack is quite ugly, but it works and is even fast. Just never use fork() without immediate exec(). First try under Cygwin... crap I fork bombed my system! What is this shit? Ah I fucked up the path names so that the external executable couldn't be run.

Lesson learnt: put an exit() right after the exec() in the path for child process. Should never be reached, but if it goes there, the exit() at least prevents a fork bomb.

Well yeah, sort of works under Cygwin, but only with up to 3 threads. Beyond that, it seems like fork() at some point gives two processes the same PID, and then shit hangs.

Even slapping a mutex around the fork and releasing it only in the parent process didn't help. Fork in Cygwin is like a fork in the ass. posix_spawn() should work better because it can be mapped more easily to the Windows model, but still no dice.

OK, testing under real Linux. Yeah, no issues with that one! But instead, I get some obscure "free(): invalid size" abort. What the fuck would that even mean?! Checking my free() calls: all fine.

Time to fire up GDB in the terminal! Put a catch on the abort signal, mh got just hex data. Shit I forgot to compile with -O0 and -g. Next try. Backtrace shows the full call trace, back to the originating line in my program - which is fclose() on a file.

Ahhh I remember! Under Linux, fclosing a file that is already closed makes the program crash. So probably I was closing it twice. Checking back.. yeah that's where it was.

Shit runs fast on several cores now!

Two years and a lot of money my company has been building a peice of software for a client, I spent the day yesterday talking and watching the client, our software doesn't even come close to matching their requirements. It barely matches the brief my boss wrote and *never showed me*.

The following isn't necessarily a lesson I've learnt, but rather solidified it very much: FOLLOW THE SODDING BRIEF AND ACTUALLY LISTEN TO THE CLIENTS.

Also don't hire low paid devs just because they're cheap because they WILL produce shocking, unmaintiable and unchangeable code.

I honestly think starting this again will be much faster.

Hard drive head crashed and corrupted my entire android app source code which took my 5 months to build. I was depressed for 2 days and then started working for it again and updated the app on the store in 3 months. It was a terrifying yet amazing experience. Definitely don't want to go through that again.
Now I keep backups on the cloud. Lesson learnt.

New project arrises says teacher, my mate and I go to the meeting and it seems alright, guy says he'll pay us $1000 each.
A couple weeks later, "Sorry boys cant get that much money need to pay you $500 each".

Now we have basically finished the whole thing he sends an email and it says, "We got a great fund of $333 for both of you."

Lesson learnt never work in a community project if your looking for money.

Talking to a second year student about what they've learnt so far, and what they should learn next:

"Cool, so what general topics would you say you know really thoroughly at the moment?"

"Oh, I've now learnt Java, C#, C, C++, Rust, Javascript, node.js, HTML, CSS, Angular, Vue, Erlang and probably a bunch of other stuff I've forgotten. What do you think I should concentrate on next?"

"Hmm. Probably best to take just one of those and learn it really thoroughly."

"...but I already know them all really thoroughly."

"Ok. Can you explain what an abstract class is in say Java, C# or C++?"

"Sure, I can create a new class called abstract and then use it for abstraction. I do that loads."

...🤷‍♂️🤦‍♂️

First lesson: Stop BS'ing. Might work for flexing to non-devs, but that's about it.

I remember the first time I had a code block, I sat on my desk for up to 18 hours trying to fix it. In the end realizing that my impatience is not helping me. It was all in vain. A tired mind did not help.

I finally came to realise that I was lacking on knowledge and a tired brain did not help. I did it the next day but learnt a huge lesson. When it's just not your day, it's not you day. A fresh mind will help next day. Relax, do anything apart from code.

Too much of code can drain you of ideas and smartness. You need to let your mind breathe. Life away from the PC is important too.

I remember a time during my internship in the field of web dev, my Bootstrap didn't seem to work, and since I was quite a beginner, I was having a painful time figuring out the bug.

Turns out, one of my seniors had purposely changed the CDN URL from bootstrap to bootystrap :|

He said, "and that's why in web dev, when nothing works, start by checking your imports"

Lesson Learnt xD

Lesson Learnt..
Never make decisions when lacking sleep and caffeine as well. I nuked my HDD today morning around 3 am, I got another reason to do a fresh start btw.

That awkward moment when u look svn history to find out which idiot wrote this stupid code and u leant it was you yourself. You feel so glad you didn't go all gun blazing criticising the guy to your colleagues before ur investigation.
Lesson learnt for future ha ha ha

A lesson to be learnt by every programmer!

Something I have learnt in the past month:

Never settle for a low salary no matter how good a company sounds (unless it's a really prestige company) if they don't realise your worth and don't care about their employees. Salary is important. You are important. And customers are important. Any company that just values money, income, profit and growth over their customer and employee experience is a huge red flag. If your work life is so stressful that it doesn't let you have a good work/life balance then avoid it. What comes above being a developer is being healthy and I think alot of people don't realise this. It may sound good to work as an engineer for a big platform but if they only value themselves you are just a cheap slave, move on and do something respectable and enjoyable.

Just my life lesson in applying for grad jobs.

Something isn't working, I play around with the code, and try all possible things in the code. Still it doesn't work. Spend a couple of hours reading each and every line but still in vain. Finally, I find out that I was editing the wrong file (same file at another location) the whole time!! This happened a couple of times when I was a newbie, one of my most annoying mistakes.
Lesson learnt: Now when anybody asks me to debug his code, I first edit/add a print statement to make sure this is the correct file. I thought I was being skeptical, but it has saved me a lot of time (mostly interns do this rookie mistake).

This is gonna be a long one....
A lesson I learnt the hard way - never go out of your way to help friends with their coding. I helped her always, sat with her on the phone and explained and taught and solved her problems for hourssss while delaying my own work, while losing my sleep, even during pregnancy, I helped somehow as much as was possible even when I was drowning in my own work, even when I’m was not okay myself. But, once in a while I am too full, I also have work, now I also have an infant to take care of as well, and yeah sometimes I CAN be too busy to help!!!!! I have my own life too!! At these times she says “oh you don’t help me anymore”. It’s so annoying seriously What the fuckkkkk and after this shit happened a few times, I expressed my annoyance and she says, oh it was a joke. But then repeated it. And I still feel bad in refusing to help when asked. But lesson learnt that I won’t put myself behind, I’ll help only when I have nothing else to do.

Lesson learnt. Never use vanilla bootstrap with react js

I was Just college fresher who completed his Engineering. My first week in the office. And a system was provided to me, since it was support project so I was given direct access to production database.

Fresher + Production Database + Access of Admin credentials = Worst Possible Combination

So it was my night shift, I was told to update new tariff plan for our client (which was one of the largest telecom service in India) .

If someone recharges for more than 200 Rupee, that person will get 10% or 20% extra talk time. Which was only applicable for particular circle (Like Bihar and Rajasthan).

Since I was fresher, I was told to update given query from my senior employee which he shared on the shared folder. Production downtime was in the mid night, so at that time I updated that query on the production database.

Query successfully updated. I completed my night shift, went home and slept.

When I woke up, I saw my mobile it had 200+ missed calls from different locations of India. They were Circle heads of that telecom service provider who contacted me. I realized something unexpected is expecting me.

Then at that moment my team lead called me and he asked me to come office right away.

Reminding you I was a fresher, I was shivering. What have I done there?

When I reached office, I came to know that the query I updated on production bombarded.

Every person who recharged that day (duration from midnight to morning 10 AM) got 10 times or 20 times more talktime.

A part of Query was something like this where error was made:

TalkTime = RechargeAmount + RechargeAmount * 10/100; (Bihar)
or

TalkTime = RechargeAmount + RechargeAmount * 20/100; (Rajasthan)
But instead of this query, I updated below one:

TalkTime = RechargeAmount + RechargeAmount * 10;
or

TalkTime = RechargeAmount + RechargeAmount * 20;
In a span of 10 hours, that telecom service lost revenue of 6.5 crore Rupees. Thanks to recovery team they were able to recover 6 crore but still 50 lakh Rupees were in loss.

One small query, and approx 1 million dollar was on stake.

Aftermath of this incident

My Mistake:

I should have taken those queries on mail. Or, there should have been mail communication regarding this.
Never ever do anything over oral communication. Senior employee who did this denied and said he provided correct query, and I had no proof of communication.
I told them, it was me who executed that query on production. Since I was fresher, and took my responsibility of that incident. My team lead rescued me from that situation.
Lesson Learned:

Always test your query and code multiple times before you execute or Go live it on production.
Always have email communication for every action you take on production.
Power comes with responsibility. If you have admin credentials of production never use it for update/delete/drop until you are sure.
Don’t take your job lightly.
I was not fired from that Job, but I have learnt my lesson very well.

After over two days of debugging, lesson learnt don't assume your table's prefix nor depend on other APIs for SQL injections

PreMature optimization is the root of all evil

Learnt a very important lesson today..

To add some context; I'm currently in my second semester of uni studying a Bachelor of Computer Science (Advanced), and started the year with no experience with any language.

Up until recently all my practical work has been guided by context sheets, now I have some freedom in what my program does.

Because of the very small projects earlier in the year I have built a habit of writing the whole program before compiling anything. This worked fine since the programs were small and at most only a few errors would be present.

Cut back to today, and I had been writing a program for a bigger assignment. After an hour or so of writing I began thinking I should probably test everything up to this point. I ignored it...

Fast forward 4 hours to having "completed" writing the full program. I knew by this point I was taking a massive risk by not testing earlier.

Lo and behold, I try compiling everything for the first time and countless errors prevent the program from compiling. I tried for quite some time fixing the errors but more just kept appearing as 1 was fixed.

I'm now left with no time to fix the program before the deadline with no one but myself to blame.

Lesson learnt :/

Lesson learnt.
Never argue about any type of OS (Desktop or Mobile) when sitting between Devs. Be it about features or development.

Learn the hard way:
Episode 1:
Struggled 4 hours building my package. Some dependent package was failing build. Tried everything and atlast, contacted that package developer. He checked and said: "It seems it's broken. You can use v1.1 instead."
Lesson learnt: Sometimes, it's better to ask instead of banging your head and debugging things out.

Forgot to bring me laptop to college, so had to use the age old Turbo C complier on college PC. So had to do some power calculation.. used the pow() function, forgot to include math.h...
And bamm!!! It compiled and I had no idea why the pow function isn't giving the correct value!!

Lesson learnt: never trust anything!!

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.

What I learnt after 3 hrs of debugging for a stupid issue today ?

Lesson 1 - Getting some unknown error even though your code ks right and no error in logs ? Check you SQL version and its rules.

Lesson 2 - phpmyadmin is fuckin shit ass software

Lesson 3- I need to learn JavaScript for backend ASAP

Debugging lesson learnt

The place where you think you can't make a mistake is the place you make a mistake.

Life(naive_person) {
While(lesson not learnt) {
Change characters;
Repeat story;
}
Return dead_person;
}

DO NOT EXPORT GPG KEYS _TEMPORARILY_ AND ASSUME THAT THEY'LL BE IN THE ORIGINAL LOCATION AFTER EXPORT!

I learnt this lesson the hard way.

I had to use a GPG key from my personal keyring on a different machine ( that I control ). This was a temporary one-time operation so I thought I might be a smart-ass and do the decryption on the fly.

So, the idiotic me directly piped the output : `gpg --export-secret-key | scp ...`. Very cool ( at the time ). Everything worked as expected. I was happy. I went to bed.

In the morning, I had to use the same key on the original machine for the normal purpose I'd use it for and guess what greeted me? - *No secret key*

*me exclaims* : What the actual f**k?!

More than half a day of researching on the internet and various trials-and-errors ( I didn't even do any work for my employer ), I finally gave up trying to retrieve / recover the lost secret key that was never written to a file.

Well, to be fair, it was imported into a temporary keyring on the second machine, but that was deleted immediately after use. Because I *thought* that the original secret key was still in my original keyring.

More idiotic was the fact that I'd been completely ignorant of the option called `--list-secret-keys` even after using GPG for many years now. My test to confirm whether the key was still in place was `--list-keys` which even now lists the user ID. Alas, now without a secret key to do anything meaningful really.

Here I am, with my face in my hands, shaking my head and almost crying.

Lesson Learnt: never quote a job without inspecting every single file with every single details -_-

[clarification in comments]

Learnt a lesson today:

Never try out new hotkeys in a SQL query editor window.

Or if you do, at least make sure it's not connected to anything important :)

I was trying out new hotkeys and accidentally executed a SQL deploy script to rename something in multiple stored procedures in a large system.

Thankfully - so I saw after my heart stopped - it was only our QA db so not too bad, just a couple of devs set back.

Who woulda thought ctrl-l would execute :O

Regarding my previous rant where I shit talked about ubuntu 17.10

So instead of downgrading I tried a last chance (why not, system was fucked already) by installing unity, yes the same shit that ubuntu team removed from ubuntu 17.10 as major upgrade.

Well, it turns out gnome shell was taking more than half of my cpu in idle state and this unity barely reaches above 10%

Life lesson learnt: not every upgrade is better

Same goes for android studio, let's save it for another rant

I had learnt my lesson about the reality of group projects in the very first semester of graduation.
And from then on till the final project in my postgraduation, I refused to have a team and worked on every project alone (except for a few times when I couldn't convince the professor and even then made sure to not depend on anyone else).

Android Studio upgrade

Over the weekend I upgraded my android studio and the project files of my current project and all went smoothly (as far as I thought).
I did not touch the project till today as was implementing some few features only for some few unexpected bugs to creap in.Been implementing that feature for some time and thought would be done in a flash only to my disappointment.
Turns after upgrading my SDK they were some conflicting dependencies that had no idea of.
To make it worse my fall to branch was way behind the active one and had to create a new project from scratch and copy paste files.
All this after spending hours in Stack
Overflow and scratching my head.

Lesson learnt to commit more frequently.

My web dev teacher was drunk almost every lesson, and my C++ teachers don't care about visiting our high school)) All we know is learnt by ourselves
Other teacher hates when we type
void smth(){
}
Instead of
void smth()
{
}
And wants to overwrite the code to fix these style errors))

When you work on something for few hours and then write a script to recursively replace strings in your project but forget to take into account the git index and end up corrupting it 🤦🏻‍♂️🤦🏻‍♂️

I know I should have pushed commits in between. Lesson learnt

Started out as an intern at my current employer, after a few months they made me create an invoicing system...

I should have said no.

I've had a lot of bugs with it in the past, but the data-loss one has been because I send a SOAP call to our (third party) accounting system and only if I get an ERROR do I log it....

Apparently, when you put line 1 before line 0, you get a warning, but no data is processed...

Had to write a script that updated 4 months of invoice data in one go, without errors, took me a fucking week...

Lesson learnt boys and girls, never let an intern make the fucking invoicing system!

I once wiped my Hard-disk.
By executing rm -rf / (I hit enter before specifying the directory/file) I was Linux Noob back then, & was literally in tears for weeks after the incident because I didn't backup the Linux installation with my files). I have learnt a very important lesson after that day!
Tldr: fucked my Ubuntu System by executing rm -rf / command and was resenting the decision for weeks to come.
*Edited typos.

Spent 4 hours playing the role of a designer and crafted some great UI and showed my fellow Dev's and we were all in agreement to implement.Eight hours later our lead designer crafts a totally new look that my boss is so into forcing us to redo the app
Lesson learnt keep your lane

So this month I had to do two major features which required unexpected refactors and I had to handle unexpected edge cases all over the place. Since I work in another timezone and time was of essence, I was kinda working around the clock to complete refactors as fast as possible because it was "important and critical". I have 7 other devs in my team but only half of the team are actually competent and even less are motivated to push through. Most of the team prefer to sit on low hanging fruit tasks and cant even get that fucking right.

So that resulted in me doing at least 100 hours of overtime this month. Best part all I got for pulling it off was a thank you slack message from teamlead and got assigned even more work: to lead a new initiative which seems to be even bigger clusterfuck...

So today I had a sitdown with my manager and I asked for 3 paid days off and told him that I did 50-60 hours of overtime. He okayed it as long as my teamlead was happy.

So I created a chat, adder manager and teamlead to it and explained my situation. That Im feeling burned out, I need 3 days off and combined with the weekend that should allow me to finally relax.

My fucking teamlead told me that these days are mine and he cant take them away from me. But then he started guilt tripping me that no one else will be working on the new initiative these days so we will have a very tight timeframe to deliver this (only until August).

Instead of having at least a drop of empathy that fucker tried to guilt trip me for taking days off for fucking unpaid overtime. What a motherfucker. Best part is Ive talked with manager and we actually have until end of August to deliver the new initiative, so fucker teamlead is gashlighting me with false sense of urgency.

I guess a hard lesson learnt here. Waiting for my fucking raise to be approved for the past 6 weeks (asked for a 43% bump which is on the way since I got very strong positive feedback).

So Im done. I proved myself, will get the salary of which I only dreamed about few months ago. Not putting any overtime anymore. If something is very urgent, borrow fucking decent devs from another team. Or replace half of our useless team with just one new decent dev. I bet our producticity would increase at least by 50%.

Its not my fuckint fault that 2-3 people are pulling the weight of 8 people team. Its not my responsibility to mentor retards while crunching under immense pressure just because current processes are dysfunctional. Fuck it. Hard lesson learned. If you want overtime, compensate with extra days off or pay. Putting my 7-8 hours in daily and Im not responding to your bullshit slack messages or emails after work. I dont give a fuck that you work in another timezone and my late responses might result in stuff getting done postponed by a few days or a week. Figure it out.

I had to import some resources into infrastructure-as-code ( IaC ) for a new project. I found the right tool for the job and started working on it.

But I had a lot of resources to import. I decided to use the API of the source provider and transform them into the configuration format required for the IaC tool.

After spending a good half of a day scripting with a combination of `jq` and `yq` and another bunch of tools, I finally completed the import yesterday.

Today, I had to refer to the documentation of the IaC tool for something else and I found that there was a built-in command for pulling resources from the target to the source ( basically what I did with my script ). 🤦‍

( I hope my manager doesn't find out that I 'wasted' half a day when I could have completed the job within around an hour )

Lesson learnt the hard way ( again ) : READ THE F**KING MANUAL even if it may seem trivial.

*thought to self* : YTF won't you learn this simple thing after so many incidents? RTFM!

A friend recommended Durrell's "The Alexandria Quartet" in 1982. I check it out from the library and read it. Over the intervening years I acquired a very nice softcover edition. Last Christmas I began reading it again. For some reason I was pissed off at the soap opera bassinet who haven't we bonked narrative that began the fourth book.
So I ripped up the softcover edition and threw it away. Now I'm re-reading the third book. I wanted to buy just that one. Except it's something like forty dollars. I learnt my lesson. Don't tear up good softcover editions of books just because you don't like them at the mo. It'll cost ya.

My first #hack is that I once opened my friends account on my computer using the Google recovery question which he kept as his favorite sport . Once in I changed the password and informed him that his account was hacked..lol you should see his face .later I told him he put his recovery question to be hard to be guessed ....lol I think he learnt the lesson the hard way...well after that I got to know about internet ethical rules and there ends the matter