Rant
Why do shithead clients think they can walk away without paying us once we deliver the project !!!

So, here goes nothing..
Got an online gig to create a dashboard.
Since i had to deal with a lot of shitheads in the past, I told them my rules were simple, 20% advance, 40% on 50% completion and 40% after i complete and send them proof of completion. Once i receive the payment in full, only then i will hand over the code.
They said it was fine and paid 20%.
I got the next 40% also without any effort but they said they also needed me to deploy the code on their AWS account, and they were ready to pay extra for it, so i agreed.
I complete the whole project and sent them the screenshots, asking for the remaining 40% payment. They rejected the request saying my work was not complete as i had not deployed on AWS yet. After a couple of more such exchanges, i agreed to setup their account before the payment. But i could sense something fishy, so i did everything on their AWS account, except registered the domain from my account and set up everything. Once i inform them that its done and ask for the remaining payment.
The reply i got was LOL.
I tried to login to the AWS account, only to find password had been changed.
Database access revoked.
Even my admin account on the app had been removed. Thinking that they have been successful, they even published ads about thier NEW dashboard to their customers.
I sent them a final mail with warning ending with a middle finger emoji. 24 hours later,
I created a github page with the text " This website has been siezed by the government as the owner is found accused in fraud" and redirected the domain to it. Got an apology mail from them 2 hours later begging me to restore the website. i asked for an extra 10% penalty apart from the remaining payment. After i got paid, set an auto-reply of LOL to thier emails and chilled for a week before restoring the domain back to normal.
Dev : 1
Shithead Client: 0

I just did git branch in someone's repo and got this ..

master
master_backup
master_bckp
master1
master_aug17

I'm armed and ready .. !!
😐😑😐😱😩😡

Some 'wk306' highlights from different people:

Walk around the office in his underwear, because he forgot he left his trousers in the bathroom

Run a red light outside the office due to not wearing his required glasses. When questioned by co-workers, replied "I don't follow those facist rules"

Asking if we work less will we get paid more, because the project will take longer to do (while in a startup with no funding trying to secure some)

Tell a senior dev to stop testing in his spare time, as we won't be able to release on time if he keeps finding critical security bugs

Telling me "your timezone is not my concern", when asking for help with new tooling so we don't have to be online at the same time

Blaming my team for requesting too much help, leading to his team missing deadlines, in a meeting with very senior managers. When the reason we were requesting help was the handover doc we were given was filled with lies about features being finished and "ready to ship" and lacking any unit tests

Being accused of bullying and harassment to the CEO, because someone asked "did you follow up with X about the partnership they emailed us about". The person who was responsible, forgot 4 times, and saw it as an "attack" to mention it in team meetings

Telling an entire office/building mid November they've secured funding for at least the next year, then announcing in January after the Christmas break that its cheaper to move to India, so they are closing the office in 30 days

31st December 2016, I had signed up for devRant.

It's my cake day today. Feels so good to be part of this community, have learned so much, made some of the greatest friends here.

2021 was a mind fuck. Taxing and draining. Very little growth and even less learnings.

I realised that I am in a toxic environment.

Lately, no philosophy, therapy, supplements, activity, work, etc. has been helping me to get back to my original self.

I used to spiral down with a lot of negative self talk and playing the victim card.

Just day before yesterday, I decided to listen to some affirmations on the Tube and that actually helped me bounce back.

I started socialising and stepping out to attend gigs and just be outdoors as much as I could.

My surroundings changed and so did my thought process.

Hence, I made a decision to continue affirmations and slowly change my surroundings, even if that demand domestic relocation.

Things are starting to look positive after a long, loooooong, time.

I also need more sun exposure for my vitamin D3 deficiency and steady dose of serotonin.

I feel lot clear in head and heart. My goals are clearer and I am ready to start working hard and be my original past self again.

I love you all and I really wish you all achive all your wishes and dreams, be happier and healthier in 2022 with ton of success and money.

Manager: Here's the design for the next feature, we're ready to hand it over to the consultant

FullStackClown: Uh... okay... is it spec'd out with requirements?

Manager: Huh?

FullStackClown: Well, already look at this design and user flow, did you consider what happens when <insert edge case X here>, <insert edge case Y here>, or <insert edge case Z here>? How is the consultant going to know what to put in for business logic if you don't even know or define it yourself?

Manager: Huh?

FullStackClown: Sigh... yeah, I'm too busy right now to be a kindergarten teacher, come back in a few days once you understand how your own feature is supposed to work

Manager: ...

Dev: ...

Biggest challenge I overcame as dev? One of many.

Avoiding a life sentence when the 'powers that be' targeted one of my libraries for the root cause of system performance issues and I didn't correct that accusation with a flame thrower.

What the accusation? What I named the library. Yep. The *name* was causing every single problem in the system.

Panorama (very, very expensive APM system at the time) identified my library in it's analysis, the calls to/from SQLServer was the bottleneck

We had one of Panorama's engineers on-site and he asked what (not the actual name) MyLibrary was and (I'll preface I did not know or involved in any of the so-called 'research') a crack team of developers+managers researched the system thoroughly and found MyLibrary was used in just about every project. I wrote the .Net 1.1 MyLibrary as a mini-ORM to simplify the execution of database code (stored procs, etc) and gracefully handle+log database exceptions (auto-logged details such as the target db, stored procedure name, parameter values, etc, everything you'd need to troubleshoot database errors). This was before Dapper and the other fancy tools used by kids these days.

By the time the news got to me, there was a team cobbled together who's only focus was to remove any/every trace of MyLibrary from the code base. Using Waterfall, they calculated it would take at least a year to remove+replace MyLibrary with the equivalent ADO.Net plumbing.

In a department wide meeting:

DeptMgr: "This day forward, no one is to use MyLibrary to access the database! It's slow, unprofessionally named, and the root cause of all the database issues."
Me: "What about MyLibrary is slow? It's excecuting standard the ADO.Net code. Only extra bit of code is the exception handling to capture the details when the exception is logged."
DeptMgr: "We've spent the last 6 weeks with the Panorama engineer and he's identified MyLibrary as the cause. Company has spent over $100,000 on this software and we have to make fact based decisions. Look at this slide ... "
<DeptMgr shows a histogram of the stacktrace, showing MyLibrary as the slowest>
Me: "You do realize that the execution time is the database call itself, not the code. In that example, the invoice call, it's the stored procedure that taking 5 seconds, not MyLibrary."
<at this point, DeptMgr is getting red-face mad>
AreaMgr: "Yes...yes...but if we stopped using MyLibrary, removing the unnecessary layers, will make the code run faster."
<typical headknodd-ers knod their heads in agreement>
Dev01: "The loading of MyLibrary takes CPU cycles away from code that supports our customers. Every CPU cycle counts."
<headknod-ding continues>
Me: "I'm really confused. Maybe I'm looking at the data wrong. On the slide where you highlighted all the bottlenecks, the histogram shows the latency is the database, I mean...it's right there, in red. Am I looking at it wrong?"
<this was meeting with 20+ other devs, mgrs, a VP, the Panorama engineer>
DeptMgr: "Yes you are! I know MyLibrary is your baby. You need to check your ego at the door and face the facts. Your MyLibrary is a failed experiment and needs to be exterminated from this system!"

Fast forward 9 months, maybe 50% of the projects updated, come across the documentation left from the Panorama. Even after the removal of MyLibrary, there was zero increases in performance. The engineer recommended DBAs start optimizing their indexes and other N+1 problems discovered. I decide to ask the developer who lead the re-write.

Me: "I see that removing MyLibrary did nothing to improve performance."
Dev: "Yes, DeptMgr was pissed. He was ready to throw the Panorama engineer out a window when he said the problems were in the database all along. Didn't you say that?"
Me: "Um, so is this re-write project dead?"
Dev: "No. Removing MyLibrary introduced all kinds of bugs. All the boilerplate ADO.Net code caused a lot of unhandled exceptions, then we had to go back and write exception handling code."
Me: "What a failure. What dipshit would think writing more code leads to less bugs?"
Dev: "I know, I know. We're so far behind schedule. We had to come up with something. I ended up writing a library to make replacing MyLibrary easier. I called it KnightRider. Like the TV show. Everyone is excited to speed up their code with KnightRider. Same method names, same exception handling. All we have to do is replace MyLibrary with KnightRider and we're done."
Me: "Won't the bottlenecks then point to KnightRider?"
Dev: "Meh, not my problem. Panorama meets primarily with the DBAs and the networking team now. I doubt we ever use Panorama to look at our C# code."

Needless to say, I was (still) pissed that they had used MyLibrary as dirty word and a scapegoat for months when they *knew* where the problems were. Pissed enough for a flamethrower? Maybe.

TM: Hey, do you have a moment?

Me: not really, I'm already overtime and have enough work for the whole year.

TM: Yeah, we know. Just a quick meeting to discuss something awkward.

Me: Hmkay.

...

Later that day:

TM: Yeah. To make it quick - we're confused and bit dissatisfied with how project X turned out. The staging server is blazing fast, but the devs machines seem to be extremely slow... Some devs complained.

Me: No wonder. I said from the beginning that the devs shouldn't do X and Y, and that the dev machines need to be redone after staging is done - as we need to gather hands on experience first, cause no one could explain to me what resources the project actually needed.

TM: Oh. I wasn't aware of that.

Me: I guessed so. You were on vacation at the beginning and I didn't had the time to lead another team...

TM: Yeah... So the dev machines get replaced?

Me: They _could_ be replaced, but the devs would need to reset up their environment, as I and won't transfer the environment of the dev user.

TM: Ah... So they would have to retransfer their personal modifications, if they made any?

Me: Yes. As always, the basic setup just provides the necessary services, settings etc. - stuff like remote IDE settings on the machine, configuration etc is left out and we don't transfer it as it is usually too much of a hassle and risky, as every dev does have his / her own preferences, and we don't want to support every possible configuration out there.

TM: Just out of curiosity... Staging was ready like... Last year?

Me: Beginning of December, yes.

TM: Sigh.

Me: The jolly of having a kinder garten full of toys that no kid wants to clean up...

TM: No comment. The kinder garten Kids might make me a Pinata otherwise.

Me: If only they'd fill us with chocolate first instead of just beating us.

...

Tales of lazy devs, to be continued...

I’m fucking done….
I don’t even know what to tell.
I’m a CTO in a startu. We have pretty good traction, my salary is about average senior dev salary (plus 10%).
I’m good financially.
But I have no more pleasure in work. Like at all.
“This API call performance is bad”
Yeah I know, maybe you shpuldn’t try to call it for 1000 objects at the time ?
“We need to reduce Azure cost”
Yeah I know, but are you ready to live with performances downgrade it will generate ?
“I don’t understand on what thing you worked past week, where is a devops card ?
Fuck you, I’m in extenuating fire mode, I don’t have time for a fucking devops card
“We should migrate whole stack to modern technology, like JavaScript”
Thank you for your imput, Blazor WAS created to avoid JabaScript
“The client has only 1.000.000 records and API doesn’t return them all”
Use fucking paging moron. And BTW, I’m adding “number of authorized requests” shortly.
I can go on and on and on for hours. But the idea is : I completely lost the will or motivation to do anything. I’m considering just to quit and go back to be Junior dev for a random company.

Worst collaboration experience story?

I was not directly involved, it was a Delphi -> C# conversion of our customer returns application.

The dev manager was out to prove waterfall was the only development methodology that could make convert the monolith app to a lean, multi-tier, enterprise-worthy application.

Starting out with a team of 7 (3 devs, 2 dbas, team mgr, and the dev department mgr), they spent around 3 months designing, meetings, and more meetings. Armed with 50+ page specification Word document (not counting the countless Visio workflow diagrams and Microsoft Project timeline/ghantt charts), the team was ready to start coding.
The database design, workflow, and UI design (using Visio), was well done/thought out, but problems started on day one.
- Team mgr and Dev mgr split up the 3 devs, 1 dev wrote the database access library tier, 1 wrote the service tier, the other dev wrote the UI (I'll add this was the dev's first experience with WPF).
- Per the specification, all the layers wouldn't be integrated until all of them met the standards (unit tested, free from errors from VS's code analyzer, etc)
- By the time the devs where ready to code, the DBAs were already tasked with other projects, so the Returns app was prioritized to "when we get around to it"

Fast forward 6 months later, all the devs were 'done' coding, having very little/no communication with one another, then the integration. The service and database layers assumed different design patterns and different database relationships and the UI layer required functionality neither layers anticipated (ex. multi-users and the service maintaining some sort of state between them).

Those issues took about a month to work out, then the app began beta testing with real end users. App didn't make it 10 minutes before users gave up. Numerous UI logic errors, runtime errors, and overall app stability. Because the UI was so bad, the dev mgr brought in one of the web developers (she was pretty good at UI design). You might guess how useful someone is being dropped in on complex project , months after-the-fact and being told "Fix it!".

Couple of months of UI re-design and many other changes, the app was ready for beta testing.

In the mean time, the company hired a new customer service manager. When he saw the application, he rejected the app because he re-designed the entire returns process to be more efficient. The application UI was written to the exact step-by-step old returns process with little/no deviation.

With a tremendous amount of push-back (TL;DR), the dev mgr promised to change the app, but only after it was deployed into production (using "we can fix it later" excuse).

Still plagued with numerous bugs, the app was finally deployed. In attempts to save face, there was a company-wide party to celebrate the 'death' of the "old Delphi returns app" and the birth of the new. Cake, drinks, certificates of achievements for the devs, etc.

By the end of the project, the devs hated each other. Finger pointing, petty squabbles, out-right "FU!"s across the cube walls, etc. All the team members were re-assigned to other teams to separate them, leaving a single new hire to fix all the issues.

Manager: How's (insert dumbass task that they assigned literally 1 hour ago) going? 😊

Dev: We have JIRA for a reason, you'll see it will be moved to demo / review when it's ready.

Manager: ...

Dev: ...

Why do my colleagues insist on HOURLY messages like "any update on X?" or "did you fix Y yet?"

REST ASSURED, WHEN IT IS DONE AND READY TO BE DEMOED, I WILL MESSAGE YOU, AS I HAVE FOR ALL PAST FEATURES AND BUG FIXES.

sheesh talk about too much time on your hands...

- Be me
- Been in a new job for 2 months
- Was excited because of 50% salary increase and better position

- Have a new team of 6 devs including me. All new guy
- Market crash
- Top management demands a trim down to all divisions
- Will be left to 3 devs next month

- All the while being asked to
- Deliver a shopify like marketplace from end to end
- Deliver integration with partners for data inventory tracking
- All within 2 months

- Furious when target is not met
- Demands a micro management to every single person on the team on what their day to day schedule
- Demands everybody to live by hustle culture and ready to work non stop even nights or weekend

- Be me
- Been working non stop for at least a month
- Sacrificed weekends and holidays

Beginning to think that maybe the money and position isn't worth the hassle

Me: “here’s a demo of the backend functionality you requested. We’ve got more work to do to make this production ready. Let me know your thoughts or if we need to make any changes, otherwise I’ll hand this off to the UX team, we’ll be ready to go live next month after other they deliver the front end”

PM: *telling stakeholders* “The new thing is done and ready for go live”

Me: *privately to PM* “who told you that the thing was ready for go live?”

PM: “You did”

Me: “I suggest you go read what I wrote a little more closely”

Most successful? Well, this one kinda is...

So I just started working at the company and my manager has a project for me. There are almost no requirements except:
- I want a wireless device that I can put in a box
- I want to be able to know where that device is with enough accuracy to be able to determine in which box the device was put in if multiple boxes were standing together

So, I had to make a real time localization system. RTLS.
A solo project.

Ok, first a lot of experiments. What will the localization technique be? Which radio are we going to use?
How will the communication be structured?

After about two months I had tested a lot, but hadn't found THE solution. So I convinced my manager to try out UWB radio with Time Difference Of Arrival as localization technique. This couldn't be thrown together quickly because it needed more setup.

Two months later I had a working proof of concept. It had a lot of problems because we needed to distribute a clock signal because the radio listeners needed to be sub-nanosecond synchronous to achieve the accuracy my manager wanted. That clock signal wasn't great we later found out.

The results were good enough to continue to work on a prototype.
This time all wired communication would be over ethernet and we'd use PTP to synchronize the time.

Lockdown started.

There was a lot of trouble with getting the radio chip to work on the prototype, ethernet was tricky and the PTP turned out to be not accurate enough. A lot of dev work went into getting everything right.

A year and 5 hardware revisions later I had something that worked pretty well!
All time synchronization was done hybridly on the anchors and server where the best path to the time master was dynamically found.

Everything was synchronized to the subnanosecond. In my bedroom where I had my test setup I achieved an accuracy of about 30cm in 3d. This was awesome!

It was time to order the actual prototype and start testing it for real in one of the factory halls.

The order was made for 40 anchors and an appointment was made for the installation in the hall.

Suddenly my manager is fired.

Oh...
Ehh... That sucks. Well, let's just continue.

The hardware arrives and I prepare everything. Everything is ready and I'm pretty nervous. I've put all my expertise in this project. This is gonna make my career at this company.

Two weeks before the installation was to take place, not even a month after my manager was fired, I hear that my project was shelved.

...
...

Fuck

"We're not prioritizing this project right now" they said.

...

It would've been so great! And they took it away.
Including my salary and hardware dev cost, this project so far has cost them over €120k and they just shelved it.

I was put on other projects and they did try to find me something that suited me.

But I felt so betrayed and the projects we're not to my liking, so after another 2-3 months I quit and went to my current job.

It would've so nice and they ruined it.
Everything was made with Rust. Tags, anchors, RTLS server, web server & web frontend.

So yeah, sorry for the rambling.

Everything about the company is a mess. The only thing that is decent is the people. And by that I mean they aren't shit.
Workflows are fucked.
Clients are fucked. You're pressuring me to get this shit production ready before new year's eve and you still don't know what the text should say and want to make changes to the UI? The fuck?!
Design is a complete shit show. There is a design team. They only make a fucking psd to show clients how an interface would look like. No mobile version (but it's still expected to work!), no markup. Resolution is fucking inconsistent and whenever a change is requested, they are nowhere to be seen so I have to actually do designing on top of having to use this worthless fucking framework I hate it so much.
Codebases are turbo-fucked because of said framework.
Databases are an inconsistent, fucked up mess. No foreign key constraints because every single fucking table is using the MyISAM engine.

And the thing that really makes me incredibly angry is all the "custom systems" look the fucking same at the database level. Like 30 fucking useless tables made for stupid HR workflows that make no fucking sense.

I don't know how managers are planning deadlines and counting December as a full working month!

Most companies that I worked with, count either half a month or push the deadline until the end of January when the workforce is back but not here.

Our division manager has promised the customer that the production environment will be ready on the first week of January, without even consulting the team or checking the schedule like WTF!
The person responsible for setting the infrastructure was on vacation for 2 weeks and he didn't hand over the access to production or share the progress done.
Fast forward, the manager went to slack and pinged the whole company with full caps message that the production should be done today.

Fun times :/

Stories from Gary #000

Short background info:
So I'm working as a game dev for 3 years now and by now I can say that I've seen some shit. Mostly because of one of our game designers, let's call him Gary.

So Gary, from here on called GDG (Game Designer Gary), is a regular game designer (GD). His job is to come up with new game ideas, commission the assets, make sure that translations are done, etc. - simply put, he has to get a lot of shit together before we can start working on a new game.

Would be no problem at all if GDG wasn't lazy as shit and would work for once in his life. No dev really wants to work with him anymore, since he's known for calling a game or any issue "ready for development" even if half the assets or specs are still missing.

Let's move on to a particular situation that happened a couple of months ago.

I had an issue assigned to me, which was about implementing the translations for a new game. As I read the issue and checked if everything I needed was given, I noticed that the most important part was in fact missing - the keywords for the translations.

-.-

So, I called GDG and asked where I could find the keywords, to which he responded "Oh, I'm working on them right now... and by the way I got a weird bug with the translation program. Can you come check it out?". Sigh. I went over to his office, rambling about how I should be able to help him with a program I rarely use and which was written ages ago.
As soon as GDG saw me coming roundbthe corner, he started explaining how the keywords aren't ready yet, since the program to create translations and their keywords won't let him name a translation.

"I can create new translations, but I can't assign a keyword to them."
"Okay, show me what you did", I told him, eager to leave.
He started to type the keyword, which turned out to be huge ass long and immediately I noticed a little counter, like "x/50", directly beneath the text field started to count up with every new character GDG typed. See where I'm going with this? HE WASNT ABLE TO RENAME A TRANSLATION BECAUSE HE WAS TOO LAZY TO FUCKING READ AND CONCENTRATE FOR ONCE. Sorry for that, but even thinking about it gets me angry again.

To some this might sound like nothing, but it really got to me at this point. Maybe it will become more understandable as I post more GDG stories.

tl;dr: A 40 something year old man, who's been working in his job for over 10 years wasn't able to use a program which he daily uses and asks me for help, only to find out he's a complete dipshit.

A long long time ago ( 2007 I think ) I worked for a company that made landing sites, so basically an email campaign would go out, users would be sent to a 1 page website with a form to capture their data, ready to be spammed even more. You know how it was back then.

So I worked with a guy who we had just hired, I didn't do the hiring but his CV checked out, so I gave him one of my tasks. Now most pages were made with js and html, with a PHP backend ( called with Ajax). Now this guy didn't know PHP so I was like all good, ASP works too at the end of the day we don't judge, we do like 2 or 3 of these a day and never look at them again. So he goes of and does is thing.

3 weeks later, the customer calls up to me they still haven't received their landing page. Ok so he probably forgot to email the customer np, I tell him to double check he has emailed the customer. Another week goes by end the customer calls back, same problem. At this point I'm getting worried, because we're days away from the deadline and it was originally my task.

So I go back to the guy and I tell him I want that landing page so I can send it myself, half thinking to myself that we had a freeloader, that guy that comes in to companies for 3 weeks, doesn't work, but still cashes his pay. But no, this was much worse.

So he tells me he has finished yet. I ask him why, what's the blocker ? You had 4 weeks to tell me you were blocked and couldn't progress. And his answer was simply, because I wasn't blocked I have been working on it this whole time. So I tell him to zip his project up and email it to me. We didn't do SVN or git back then, simply wasn't worth it. So he comes back to me and says the email server is telling him attachments can't be bigger then 50mb. At this point I'm thinking he didn't properly sized the art or something, so I give him a flash drive to put it on.

When I then open the flash drive, the archive is 300mb, thinking to myself, the images weren't even that big to begin with.
So I open it up, and I don't even find any images, just a single asp page. About 500mb. When I opened that up and it finally loaded, I saw the most horrendous things ever.

The first 500 lines was just initializing empty vars. Then there was some code that created an empty form with an onChange event that submits the form. After that.. it was just non stop nested if's. No loops, no while, for, foreach, NO elseif's, just nested if's, for every possible combination of the state the form could be in. Abou 5000 of them, in a single file. To make matters worse, all the form ( and page ) layout was hardcoded in the if's. Includes inline css, base64 encoded images, nothing but as dynamic, based on the length of the form he changes the layout, added more background etc. He cut the images up for every possible size of the page and included them in the code.

I showed it to my boss, he fired the guy on the spot. I redid the work from scratch, in under 4 hours. Send it to the client. they had no ammends to make, happy as Larry. Whish I kept the code somewhere.

Morale of the story, allways do a coding test on interviews, even if small things just to sanity check.

Me: I've not done this before, so any guess would be pure assumption.

Client: Okay, but still, you would have some idea, right?

Me: It might get done in 3 days or may take even 30.

After 3 days:

Client: But you said that it will be done in 3 days. Now you are saying there MVP is not ready. Do you even know, your part is the most critical one in the project. We believed in you. We trusted you. This is insane. It was a wrong decision to choose you.

Me (in my head): Didn't I say, this is the first time I am trying to scrape Coles? It might take time?

Me (in actual): I understand, it is getting delayed. Am trying to get this up ASAP....

Anyone else experienced toxic clients but still didn't lose their cool?

I keep seeing the word “privileged” thrown around, and this one, I actually understand to be right.

But if you have a mental disease or another serious incurable condition, kick like 5000 points off your privilege scale.

Money and medication don’t always help. I’m ready to give a very, very thick stack of money to anyone who can actually cure what I have. I wish I could do it.

I'm definately an alpha male.

Give me a couple more revisions and I might be ready to enter closed beta.

FUCCCCKKKKKKKKKK!

I need to get off this frustration out of my system.

I have a autistic retarded sister who has less than a half brain cell.

Evolution from fish to humans was faster than completion of a task assigned to this faggot.

I fucking hate her. Why was I born in this family. Fucking why!!!!!

Autistic narcissistic cunt. Horrible human.

Doesn't have any friends, no family member cares for her, entitled bitch, earns less than $75 a year.

Whenever we meet, she makes sure to belittle me in front of our parents and gives advices and gyaan on how superior she is and how much waste of oxygen I am.

Constantly mentions that my career choices are stupid, whereas she is doing great (in reality she isn't even able to score a simple degree and no one is willing to hire her).

Acording to her, I have zero financial literacy and she is a genius (in reality I am managing the entire family finances and providing for everyone).

Even when I ask her about something, she says that I am asking stupid questions where as in reality she is an anti vaxxer. God damn fuck!! She was stopping my parents to get vaccinated. Fucking bitch.

There's a simple 20 minute task regarding some tax work and she took more than 2 weeks to even comprehend my request and now screams at me for raising the request on the last day. Bitch WTF! I told you well in advance and now you fuck me up entirely.

My parents are so fucking biased and will blindly side her because she is a girl and using this argument they have destroyed me emotionally over years.

Yes, I no longer care for any of these maniacs and want to leave this place asap.

For now, for the life of me, I am ready to pay more than $3500 extra in taxes than deal with this woman child.

Ok soooo boss asks me: "When is the website going to be ready?"
me: today i'll be through
----------------------------------------
4 hours later:
Site 90% done
- messed up theme
- try reinstalling theme
- 2 try
- 3rd try
- 4th try
- 5th try: success , time 6:00pm
-----------------------------------------
SENDING DAILY REPORT:
Site is 90% complete and waiting for content from client
- projects
- logo
- images

Okay, wait, is it a common practice to push changes to master that you KNOW break some other features? I always assumed that that's what branches are for and master should be the "to the best of our knowledge it should be production ready"? But apparently in this company you need to hunt for the right revision, interrogating people why suddenly nothing works on your end and half the time it's "oh, this guy has been working on something and it broke half of the stuff others have been working on and isn't covered in tests yet. Use revision 21xkcd7a"

I think I've had an account there for 10 years now, and now, every couple of weeks it seems, I get an email from them saying:

"Soon your profile will stop being shown"

So I have to log in, spot that there is no one within 500 miles of me, still, and log out again..

Why make folk log in unnecessarily, its really annoying !

I didn't make all these accounts all over the place, so I would have to register again if I need them, no I just want them to sit ready in case I do.

So, stop closing accounts just because someone is in hospital, prison, travelling the world in 80 days, etc.

Got some detailed feedback from Booking.com, upon asking.

I answered all the questions right. But they said I am not ready for a Sr PM role (which might be true).

Here are three points that I captured from the feedback:

1. Focus on details
2. Clear and better reasoning for WHY
3. Realistic over idealistic scenarios

While it makes me feel low that I didn't make it but this feedback will surely help me overcome the challenges and clear interviews in future.

On to the next one now. Let's see what comes my way..

One thing for sure, there is lots and lots to learn for me yet.

One thing I surely lack is articulating my thoughts and keeping things crisp while conveying the information aptly.

Anyone has any tips/resources on how to improve in this area?

I have severe OCD. What I do and what I make should be perfect. When I went to being a teacher as a side hustle, two days a week, three hours a day, nothing serious, my brain was like "teaching is a noble mission, Janusz Korczak was a teacher, and he dropped that Teacher Banner when he stepped into a nazi gas chamber to not let his students die alone, and now you are the one who caught that banner, and now you are carrying it, and you must not bring the shame to it", then I wasn't sleeping because for every class I SHOULD be READY, everything should be checked and prepared, there should be not a single case of me not knowing the answer for anything students ask, let alone being late

Ready for another look into my JIRA life?

Ticket Title: "The 'Selected photos' setting will result in users being able to select only one photo at a time."

Ticket Description: "This is not directly a bug, because this problem is caused by the selected setting. Here one would have to consider to give this option no more and/or with an error message the user on it to make attentive, how he can change the attitude."

I don't even have to worry about NDA in this one because it makes absolutely no sense.

BTW, we don't have a single text in the app with the words "selected photos"

99% sure the creator of this ticket wrote it when they were high, drunk, or both

Probably everyone at least once had situation when they receive a meaningless screenshot with 500 page, a message "Application doesn't work fix it" and 0 info whatsoever.
Here is my tip that saved me a lot of trouble.
I display error id in the center of the screen, large enough so no matter how small and blurry the image is (yes users, send us photos of theirs displays) , It is always easy to ready it so we can start investigation without talking to those monkeys.

I fucking hate managers who go out spouting things have gone to shit and production is broken, when a single feature is missing from the application. It's your fault for not making sure the specifications were correct or not testing in QA before going to production! Just because one minor feature is missing does not mean production is broken you dimwit! It just means you suck at your job and we have to fix your fuck ups. It would also be really helpful if you morons accepted the fact that the teams want to do daily releases and continuous development, instead of having to deal with your insanity of pushing releases to a specific date so we have everything ready from marketing to Steve the janitor

There is that meme "I've no idea what I'm doing" and there's the meme "it's fine *in a fire*". Currently I feel like a combination of those two. I'm in unexplored waters and nobody knows what's going on anyway, so I just make sure my part is technically correct according to specifications and when everything comes together I'm ready to respond to the expected disaster..

I tried to spread awareness of the coming disaster but nobody listens so I'll just wait and see what happens..

I have a complex about my nose. I was about to bite the fucking bullet and do something about it. Literally just waiting for the procedure room to be ready, when I kept asking myself wtf I was doing. Then looked at my nose again and realized that it really wasn't that big a deal. Not when compared to dealing with internal bleeding and pain for weeks, plus a painful procedure.

Even after all these years, all these accomplishments, all this experience, I'm still a dumb fuck.

Now then, I'll go put some of the money I didn't waste to good use. Like videogames, hookers, and blow. Probably just the former.

Old old organization makes me feel like I'm stuck in my career. I'm hanging out with boomer programmers when I'm not even 30.

I wouldn't call myself an exceptional programmer. But the way the organization does it's software development makes me cringe sometimes.

1. They use a ready made solution for the main system, which was coded in PL/SQL. The system isn't mobile friendly, looks like crap and cannot be updated via vendor (that you need to pay for anyway) because of so many code customizations being done to it over the years. The only way to update it is to code it yourself, making the paid solutions useless
2. Adding CloudFlare in the middle of everything without knowing how to use it. Resulting in some countries/networks not being able to access systems that are otherwise fine
3. When devs are asked to separate frontend and backend for in house systems, they have no clue about what are those and why should we do it (most are used to PHP spaghetti where everything is in php&html)
4. Too dependent on RDBMS that slows down development time due to having to design ERD and relationships that are often changed when users ask for process revisions anyway
5. Users directly contact programmers, including their personal whatsapp to ask for help/report errors that aren't even errors. They didn't read user guides
6. I have to become programmer-sysadm-helpdesk-product owner kind of thing. And blamed directly when theres one thing wrong (excuse me for getting one thing wrong, I have to do 4 kind of works at one time)
7. Overtime is sort of expected. It is in the culture

If you asked me if these were normal 4 years ago I would say no. But I'm so used to it to the point where this becomes kinda normal. Jack of all trades, master of none, just a young programmer acting like I was born in the era of PASCAL and COBOL

I hate power cuts..

I have an UPS though, so, I don't hate them so much..

Except for ones that last longer than the battery life of the UPS..

Then it means I have to turn off servers..

And guess what, one of them won't turn on again !

I do have a backup server, but it isn't as powerful, and will only cover the basic's..

So, lesson there, always have at least one running spare server as powerful as you need, ready to take over when another server decides its not going to play nice..

This is why I don't like powering things down, ever !

Not even the weekend yet and I’m feeling this. So ready to retire. But still too early in my age.

Learn Rust and Elixir because of my hopefully new and exciting role. I want to become production ready developer for these languages as quickly as possible. But more than anything I want my new role not making me hate my profession.

And also I would like to start a long duration relationship. Can’t have it all though.

One of our team mates is based out of the US office. We are physically distant, but after our manager's departure, we lost touch because our scope of work was different.

Me and two other team members work closely with each other from India and dude is alone, working out of the US.

Super smart, very polite, and a fun person to work and be with. Even when our interaction was less, I learnt so much from him.

Since, I am facing some challenges, I decide to use it as an excuse to connect with him for a coffee and also seek his guidance because he is senior to me.

Some things he mentioned,

1. Our new line manager asks him to do things on spot with no heads up. He has to drop everything and complete the ask.

2. Often times, poor guy, is asked to join meetings on immediate basis. Even while he is having his lunch.

3. He never got support from our new manager. Infact, based on the conversation, I realised that the manager supports me more.

4. He is facing same, if not more, issues with tech. And he didn't have any guidance on how to handle the issue.

5. A lot of times he is facing process and system problems which he isn't able to solve because the org culture is that of working in Silos. And he doesn't get any support from manager.

6. Tech has clearly pushed him back when he asked for help and other teams never respond to him.

My man was still smiling bright and was looking things from a positive lens that all of this is interesting and adds to the learning experience which will be valued when we decide to move on from this job.

These are the people who inspire me. Smiling in the time of adversity.

Even when he had his own challenges, he was ready to guide me and hear my frustrations. I offered him help and will make sure to stay connected so he doesn't feel left out and alone in the team only because we don't work together in physical space.

One thing I have learned over time is, while I am facing problems, someone out there is facing more and difficult problems then me. I always tend to blow up my problems out of proportion then what they actually are.

I am the dumbest person that I know and mark my words, I'll die because of my empathy. I wish I could help my team mate in any possible way.

Boss needs certain stats pulled from database once a year for board meeting. This time I delegate it to a junior dba/sysadmin. He looks at my 3-year-old docs that I hastily jotted down and pasted and included my rambling notes with results from way back then. Mostly they were just to jog my own memory, not to be a really neat, clean instruction guide. He does the queries correctly, but in ticket for boss he pastes also all my notes from the docs. boss gets confused, "what is this other number, I don't get it?!" We have to have a meeting of the 3 of us and waste an hour or so just to figure out what went wrong, finally I realize what junior guy accidentally did. Moral of story: to avoid baffling the nontechs, always simplify, simplify, simplify. Alternate moral of story: before delegating a task that seems old hat to you, always review your notes/docs and make sure they're ready for someone else to use them.

So exams are coming up and I’m not even ready at all :,,) I Need and want to study But At the same time i want to draw and animate. When i think about these two stuff my brain becomes soggy and very slow so in the end I don’t do anything and it’s bad :,,) I really suck at planning stuff out, do you all have any good schedules that work? :DD

I dont know how to timeline projects. I tell clients that it will be ready in one month. But the project will be so big that it takes lot of time to actually code it and do all the procedures around it. I m just giving them timeline based on the speed of my mind.

Started a side project.
Learnt flutter and firebase.
Started coding app.
Four months pass by.
App is mostly ready.
Wakes up on Saturday morning.
Updates Android Studio and SDK because, why not?

Build failed!
Dependency depreciation warnings!
Java errors!
Firebase errors!
Emulator stopped running!

Wify is angry with me as we planned shopping but now this. Fortunately, she's also in IT, so she understands..

FML! Spent the entire day stackoverflowing and fixing errors!

8PM evening, I am back to Friday's status. My shoulder and neck hurts but my mind is chilled.

3 weeks ago
Client: when can we go in production, we want x and y
Boss: 13/12

Absolute Silence

Today 8/12
Boss: how long will it take for bringing this in production on 13/12?
Me: I'll do my best to get it ready on time
Boss: Why will it take 2 workdays?
Me: because client asks x and y
Boss: so?
Me: x and y is not ready
Boss: x and y can' t take two days, it must be ready now
Me: You said 13/12?
Boss: client wants to test before production
Me: ... 😡

Where did things go wrong here?

I don’t understand why people hate windows, especially windows 11??

Running Windows 11 on a Dell Latitude 3520 with an 11th Gen Intel Core i5 processor, I was able to go from the computer completely shutdown to a new 3D unity project fully loaded and ready to go in only 1 minute and 25 seconds!!! That’s from completely shutdown!

I haven’t overclocked the PC or anything and have used half of the 465GB storage!

Seriously Vlang is so cool . But it still in beta. Started to contribute. I will start building packages for the jitsi SDK after the VPM (package manager) is ready Because I want to try something.

Haven’t been active on devRant in a few months, spread across different platforms and university work. Just finished a class working on a portfolio piece and that took a lot out of me combined with several life events in consecutive weeks. Just doing the bare minimum homework and had my nose stuck in video games the past couple weeks since finishing that portfolio class. Feeling a lot better going into this new week though and ready to get back to working on another portfolio piece while learning some advanced NodeJS and MVC architecture.

Microsoft Windows can burn.

I have this feature where I configure a remote API via some endpoints and the API pushes data back to some webhooks in my API.

Yesterday I set everything up for the final test; fired up my own API with some test data, added some configuration and started trace logging to ensure that everything works as expected when the remote site tries to send me data.

I was ready to collect ! Enter this morning: Windows have forcibly rebooted to install an update and shut everything down.

inb4 install Linux; No, I can not. Windows is company policy and I am required to use shit that is only designed for Windows.

let's say i want to host my own local search engine, i have the application ready.
now i want to activate my crawlers to scrap and index the web.
would i be in hot water for doing this? is there any implementation level rule that i can check other than robots.txt?
any thoughts or inputs on the subject other than it being a huge waste of time and resources :D.

Question about scrum in terms of developer/QA workflow. We have a problem in our team: basically when a dev submits an MR it needs to get 2 approvals from devs and then task is marked ready for qa. Now problem here is that qa takes 2-3 weeks to get to the task and when they do usually MR has merge conflicts and since QA are quite new-ish they have to wait for dev for conflicts to be resolved, ergo rendering the MR unable to be tested until dev resolves the conflicts.

Our teamlead proposes to solve this by forcing devs to rebase everyday (even if QA will get to working on the task 3-4 weeks later). Problem with that approach is that each conflict resolve removes approvals. So I had a situation where in 3 weeks I rebased like 15 times and 5 times I had resolve coflicts and because approvals were lost I had to annoy all devs and ask for reapprovals. And this is only with 1 MR. Now imagine all devs doing rebasing daily and spamming each other for reapprovals. Its not efficient.

Anyone could advice how to solve this issue?

Be me, a ret***

Already 3 months in a new position. (check my previous rant)
Storm have passed for a while but another storm is brewing.

C levels are having disagreement with each other.
Caught in the crossfire as one the of C's hire.
Have some chit chats with both side of C, each telling different stories.

C#1 told me there was a demand from C#2 to force tech guys (not defined who or how many) to resigns.

C#2 told me there is no plan to close the whole tech team. But there's a distrust brewing in the tech team especially on the C#1

Be me, C#1 hire...
Me telling them IDK what their real intentions are but there's a high probability for my reputation to be tarnished on the job Market.

I've always had good review amongst peers and confident I did and do a satisfactory job for my previous employer.

Be me:
Resorted to flexing my connection to high ranking (think of C suites) reference who I've worked and have good relations with.
Connected them to my C#2.
Dunno how the C#2 thinks of me and what my value to C#2 are.

Don't know what the future hold for me.
Tried doing one interview but topics of my reputation comes up because of me jumping to executive position without having "Manager" ever in my resume.
Got a bit too defensive on that and it might eff up my chance to have a backup ready in case I urgently need to jump ship.

Depression and impostor syndrome hits like a truck every day.

Are you gies ready for WW3?

I don't - I live and am ready to face the consequences if I'm ever found out not to be the best of myself everyday.
(That shit is reserved for family and friends - can't buy my smile)

so i was having snack time at my preschool, right after nap time guys, and this was recently btw. and then this IDIOT named jack comes over and steals some of the crackers, before snack time is even ready!! and he gets away with it, the fucking bastard he is and then i try it, and get in trouble BUT THE THING IS, THE TEACHERS WERE LOOKING AT HIM WHILE HE DID IT. THATS WHAT PISSED ME OFF!!! FUCK THAT BASTARD NAMED JACK!!!

How I Get A Job When I Have Not Sufficient Knowledge About Backend And The JavaScript Language. JavaScript Also Very Disturbing Language, I Love To Do Programing But Sometime I'm Frustrated About How Much It Takes Time To Learn Job Ready Programming

Any boot camps worth it to become market ready. Still seeking proper degree but I’d like to work during that time as well. Thoughts?

Tomorrow I'm going to my first international travel, and it isn't just that, I'm also going to work there.
Am I nervous? A lit lot hehe
Am I ready for it? I'm not sure, even my bag isn't ready for it.
But I hope that everything will be alright and in the end of day, if nothing goes well, I'm gonna know that it is going to be a great experience

"Nuxt 3 is currently in beta, keep in mind that it is not yet production-ready."
How about I use it in production anyway, huh? You can't stop me anyway and the client pays too little to care about resiliency of the app compared to my fun of learning, thenks.