Good Morning!, its time for practiseSafeHex's most incompetent co-worker!

Todays contestant is a very special one.

*sitcom audience: WHY?*

Glad you asked, you see if you were to look at his linkedin profile, you would see a job title unlike any you've seen before.

*sitcom audience oooooooohhhhhh*

were not talking software developer, engineer, tech lead, designer, CTO, CEO or anything like that, No No our new entrant "G" surpasses all of those with the title ..... "Software extraordinaire".

*sitcom audience laughs hysterically*

I KNOW!, wtf does that even mean! as a previous dev-ranter pointed out does this mean he IS quality code? I'd say he's more like a trash can ... where his code belongs

*ba dum tsssss*

Ok ok, lets get on with the show, heres some reasons why "G" is on the show:

One of G's tasks was to build an analytics gathering library for iOS, similar to google analytics where you track pages and events (we couldn't use google's). G was SO good at this job he implemented 2 features we didn't even ask for:

- If the library was unable to load its config file (for any reason) it would throw an uncatchable system integrity error, crashing the app.
- If anything was passed into any of the functions that wasn't expected (null, empty array etc.) it would crash the app as it was "more efficient" to not do any sanity checks inside the library.

This caused a lot of issues as some of the data needed to come from the clients server. The day we launched the app, within the first 3 hours we had over 40k crash logs and a VERY angry client.

Now, what makes this story important is not the bugs themselves, come on how many times have we all done something stupid? No the issue here was G defended all of this as the right thing to do!

.. and no he wasn't stoned or drunk!

G claimed if he couldn't get the right settings / params he wouldn't be able to track the event and then our CEO wouldn't have our usage data. To which I replied:

"So your solution was to not give the client an app instead? ... which also doesn't give the CEO his data".

He got very angry and asked me "what would you do then?". I offered a solution something like why not have a default tag for "error" or "unknown" where if theres an issue, we send up whatever we have, plus the file name and store it somewhere else. I was told I was being ridiculous as it wasn't built to track anything like that and that would never work ... his solution? ... pull the library out of the app and forget it.

... once again giving everyone no data.

G later moved onto another cross-platform style project. Backend team were particularly unhappy as they got no spec of what needed to be done. All they knew was it was a single endpoint dealing with very complex model. There was no Java classes, super classes, abstract classes or even interfaces, just this huge chunk of mocked data. So myself and the lead sat down with him, and asked where the interfaces for the backend where, or designs / architecture for them etc.

His response, to this day frightens me ... not makes me angry, not bewilders me ... scares the living shit out of me that people like this exist in the world and have successful careers.

G: "hhhmmm, I know how to build an interface, but i've never understood them ... Like lets say I have an interface, what now? how does that help me in any way? I can't physically use it, does it not just use up time building it for no reason?"

us: "... ... how are the backend team suppose to understand the model, its types, integrate it into the other systems?"

G: "Can I not just tell them and they can write it down?"

**
I'll just pause here for a moment, as you'll likely need to read that again out of sheer disbelief
**

I've never seen someone die inside the way the lead did. He started a syllable and his face just dropped, eyes glazed over and he instantly lost all the will to live. He replied:

" wel ............... it doesn't matter ... its not important ... I have to go, good luck with the project"

*killed the screen share and left the room*

now I know you are all dying in suspense to know what happened to that project, I can drop the shocking bombshell that it was in fact cancelled. Thankfully only ~350 man hours were spent on it

... yep, not a typo.

G's crowning achievement however will go down in history. VERY long story short, backend got deployed to the server and EVERYTHING broke. Lead investigated, found mistakes and config issues on every second line, load balancer wasn't even starting up. When asked had this been tested before it was deployed:

G: "Yeah I tested it on my machine, it worked fine"

lead: "... and on the server?"

G: "no, my machine will do the same thing"

lead: "do you have a load balancer and multiple VM's?"

G: "no, but Java is Java"

... and with that its time to end todays episode. Will G be our most incompetent? ... maybe.

Tune in later for more practiceSafeHex's most incompetent co-worker!!!

*came in this morning to see this conversation in slack from the remote teams*

Dev: Hey guys, I'm trying to push to the develop branch, telling me its locked. Is there a new process?

Lead dev: Yes I locked it because the repo is now dead, the last release that went out is the last for this year and ever for this app. Were merging this app with another, starting from the last release's code. We'll all have to swap over to the new repo soon.

Dev: ... eh ok I didn't put anything in the last release branch as it wasn't urgent. Normally our process is anything in /develop goes out in the new year. I've been merging to /develop for the last few weeks ... is that code now gone?
*14 question mark emoji reactions*

Lead dev: Yes
*27 angry emoji reactions*

Engineering manager: WHAT? when was this decided? When was it communicated?

Lead dev: oh I assumed my product counterpart had been spreading the messages around, have they not?

Several teams: no, nope, first i'm hearing of it.

Lead dev: Ok, i'll ask them what happened. Be aware then that most of the stuff thats going into develop now, most likely won't be allowed in until March. They want to prioritise releasing this new merged app and don't want anything to impact it.

Dev: So wait, i'm working on stuff now. What do I do? Where do I base the branch? Where do I merge?

<no response>

*My team comes into the office*

Dev: eeehhh ... what does this mean for our past 4 weeks of work? and all the stuff needed to go out in January?

Me: not.a.fucking.clue

Worst meeting I've been in?

The one where I was told by my lead and the senior that my new colleagues were having trouble speaking to me because I'm a "strong, independent woman" and that I need to make sure I don't scare them when I approach them.

-_-

So i've been a dev manager for a little while now. Thought i'd take some time to disambiguate some job titles to let everyone know what they might be in for when joining / moving around a big org.

Title: Senior Software Engineer

Background:
- Technical
- Clever
- Typically has years experience building what management are trying to build

Responsibilities:
- Building new features
- Writing code
- Code review
- Offering advice to product manag......OH NO YOU DON'T CODE MONKEY, BACK TO WORK!

Title: Dev Manager

Background:
- Technical
- Former/current programmer
- knows his/her way around a codebase.

Responsibilities:
- Recruiting / interviewing new staff
- Keeping the team focused and delivering tasks
- Architecture decisions
- Lying about complexity of architecture decisions to ensure team gets the actual time they need
- Lying about feature estimations to ensure team gets to work on critical technical improvements that were cancelled / de-prioritised
- Explaining to hire-ups why we can't "Just do it quicker"
- Explaining to senior engineers why the product manager declined their meeting request

Title: Product / Product Manager

Background:
- Nothing relevant to the industry or product line what so ever
- Found the correct building on the day of the interview
- Has once opened an Excel spreadsheet and successfully saved it to a desktop

Responsibilities:
- Making every key decision about every feature available in the app
- Learning to ignore that inner voice we like to call "Common sense"
- Making sure to not accidentally take some advice from technical staff
- Raising the blood pressure of everyone below them / working with them

Title: Program Lead / Product Owner

Background:
- Capable of speech
- Aware of what a computer is (optional)

Responsibilities:
- Sitting down
- Talking
- Clicking random buttons on Jira
- Making bullet point lists

Title: Director of Software Engineering

Background:
- Allegedly attended college/university to study computer science
- Similar to a technical product manager (technical optional)

Responsibilities:
- Reports directly to VP
- Fixes problems by creating a different problem somewhere else as a distraction
- Claiming to understand and green light technical decisions, while having already agreed with product that it will never happen

Things have been a little too quiet on my side here, so its time for an exciting new series:

practiseSafeHex's new life as a manager.

Episode 1: Dealing with the new backend team

It's great to be back folks. Since our last series where we delved into the mind numbing idiocy of former colleagues, a lot has changed. I've moved to a new company and taken a step up as a Dev manager / Tech lead. Now I know what you are all thinking, sounds more dull and boring right? Well it wouldn't be a practiseSafeHex series if we weren't ...

<audience-shouting>
DEALING! ... WITH! ... IDIOTS!
</audience-shouting>

Bingo! so lets jump right in and kick us off with a good one.

So for the past few months i've been on an on-boarding / fact finding / figuring out this shit-storm, mission to understand more about what it is i'm suppose to do and how to do it. Last week, as part of this, I had the esteemed pleasure of meeting face to face with the remote backend team i've been working with. Lets rattle off a few facts to catch us all up:

- 8 hour time difference to me
- No documentation other than a non-maintained swagger doc
- Swagger is reporting errors and several of the input models are just `Type: String`
- The one model that seems accurate, has every property listed as optional, including what must be the primary key
- Properties go missing and get removed at the drop of a hat and we are never told.
- First email I sent them took 27 days to reply, my response to that hasn't been answered so far 31 days later (new record! way to go team, I knew we could do it!!!)
- I deal directly with 2 of them, the manager and the tech lead. Based on how things have gone so far, i've nick named them:
1) Ass
2) Hole

So lets look at some example of their work:

- I was trying to test the new backend, I saw no data in QA. They said it wouldn't show up until mid day their time, which is middle of the night for us. I said we need data in our timezone and I was told: a) "You don't understand how big this system is" (which is their new catch phrase) b) "Your timezone is not my concern"

- The whole org started testing 2 days later. The next day a member from each team was on a call and I was asked to give an update of how the testing was going on the mobile side. I said I was completely blocked because I can't get test data. Backend were asked to respond. They acknowledged they were aware, but that mobile don't understand how big the system is, and that the mobile team need to come up with ideas for the backend team, as to how mobile can test it. I said we can't do anything without test data, they said ... can you guess what? ... correct "you don't understand how big the system is"

- We eventually got something going and I noticed that only 1 of the 5 API changes due on their side was done. Opened tickets. 2 days later asked them for progress and was told that "new findings" always go to the bottom of the backlog, and they are busy with other things. I said these were suppose to be done days ago. They said you can't give us 2 days notice and expect everything done. I said the original ticket was opened a month a go *sends link* ......... *long silence* ...... "ok, but you don't understand how big the system is, this is a lot of work"

- We were on a call. Product was asking the backend manager (aka "Ass") a question about a slight upgrade to the new feature. While trying to talk, the tech lead (aka "Hole") kept cutting everyone off by saying loudly "but thats not in scope". The question was "is this possible in the future" and "how long would it take", coming from management and product development. Hole just kept saying "its not in scope", until he was told to be quiet by several people.

- An API was sending down JSON with a string containing a message for the user with 2 bits of data inside it. We asked for one of those pieces to also come down as a property as the string can change and we needed it client side. We got that. A few days later we found an edge case and asked for the second piece of data to be a property too. Now keep in mind, they clearly already have access to them in order to make the string. We were told "If you keep requesting changes like this, you are going to delay the release of the backend by up to 2 weeks"

Yes folks, there you have it, the most minuscule JSON modifications, can delay your release by up to 2 weeks ........ maybe I should just tell product, that they don't understand how big the app is, and claim we can't build it on our side? Seems to work for them

Thats all the time we have for today,

Tune in for more, where we'll be looking into such topics as:

- If god himself was an iOS developer ... not
- Why automate when you can spend all day doing it by hand
- Its more time-efficient to just give everything a story point of 5
- Why waste time replying to emails ... when you can do nothing instead

See you all next week,
practiseSafeHex

I finally got a new job!! 😃
Actually i’v been working here for 3 months, but i was in trial mode so i didn’t want to post it yet but it looks like im staying 😃
They are the most talented team i ever met, they host all our local gamejams, have their own internal game engine and a gamer bar where the company’s devs have 30% off from the prices.
Their projects are exciting (even if i’m not currently on a game project) and my team lead is awesome!
I’v been wanting to work here for about a year 😃

How I went from loving my job to wishing i dont wake up tomorrow just to avoid it.

Ive been a backend dev in the company im at for 2 years now.

First year was a blast, i loved my work so much, I used to get so many random features to do, bug fixes, campaigns, analytics, etc..

Second year i started getting familiar with the part of the code that has to do with Search in our music streaming app. Nobody wanted to work on it, so i wanted to take initiative and start doing a few tasks.

A few tasks turned into sprints, and sprints turned into months worth of sprints. And because the code was the definition of tech debt, and because it was so messed up that changing one thing can blow up everything else, working on Search was not too fun.

However, people seemed to be happy search tasks are no longer piling up and someone is handling them so that used to make me feel good about it. They also gave me so much freedom and i felt like my own manager because no one told me what to do (not even my actual manager) they just let me be and were happy i was handling the part they want nothing to do with. I was also given an intern to mentor and have her work on Search tasks with me which turned out amazing.

During the last few months, I completely rewrote search, made it 10 times more performant in such a neat way, made an inhouse dashboard to automate certain tasks so we wont need to waste developers on them (all of which were extra effort on my own time without being asked), all meanwhile still tending to the fixes of the old implementation.

I felt so accomplished, and in a way, i felt like a lead (even tho im not managing any employees, i had so much freedom and I was literally responsible for everything about Search and if i decide to play with the sprint task order i can even do that).

Then 6 or so weeks ago my manager left the company, and while i thought id be a standalone team / person (single person teams are not uncommon in the company) i was instead put under someone else. Someone who likes to micro manage the fuck out of me. I have been happy working on shit code because it was my baby, my project, no one interferes and no one tells me what to do and everyone would call me the search lead (unofficially). now if i dont report to that guy every two hours he calls to see if im working. preplans sprints i no longer have a say in, and im the only dev who knows the code so all tasks go to me. I feel i got demoted so fucking much. I felt like a lead on a project and now im back to being a normal code minion. From deciding everything about a project to blindly following a some irrelevant manager's opinion. (who btw is making Search worse) And after all the extra effort i put in, after actually caring, after actually embracing Search as my responsibility i get rewarded with losing everything i liked about my job...My Independence. From feeling like a lead to feeling demoted. I am so demotivated.

I love the company, but this is hell for me and this made me hate a job i always loved. I am thinking of talking to the CTO asking to work on other stuff because i no longer want this. If i am to be a code minion at least let it be on code i like, let me go back to dealing with PMs, fuck my new manager I dont wanna work with that guy he can take the project along with all its poopoo.

If all you have is a hammer, everything looks like a nail!

This was something which my tech lead used to tell me when I was so obsessed with nosql databases a few years back. I would try to find problems to solve that has a use case for nosql databases or even try to convince me(I didn’t realise it back then) that I need to use nosql db for this new idea that I have, without really thinking deep enough whether the data in question is better represented using an sql schema or not.

Now, leading a team of young developers, I come across similar suggestions from few of my team members who just discovered this new and shiny tech and want to use it in production projects.

While I am not against new and shiny, it’s not a good practice to jump right in to it without exploring it deep enough or considering all the shortcomings. The most important question to ask is, whether some of the problems you are trying to solve can be solved with the current stack.

Modifying your stack requires more than just a week’s experience of playing around with the getting started guide and stack overflow replies. This is something which need to be carefully considered after taking inputs from the people who would be supporting it, that include operations, sysadmins and teams that are gonna interface with your stack indirectly.

I am not talking about delaying adoption by waiting for long list of approvals to get some thing that would bring immediate value, but a carefully orchestrated plan for why and how to migrate to a new stack.

Just because one of the tech giants made a move to a new stack and wrote about it in their engineering blog doesn’t mean that you need to make a switch in the same direction. Take a moment to analyse the possible reasons that motivated them to do it, ask yourself if your organisation is struggling with the exact same problems, observe how others facing the same issue are addressing it, and then make an informed decision.
Collect enough data to support your proposal.
Ask yourself again if you are the one holding the hammer.
If the answer is no, forge ahead!

We hired a new team lead. On his first day he wore green leather elf shoes. Yeah, the pointy kind.

He also ended up being one of my favorite people ever, but also one of the weirdest.

Seven months ago:
===============
Project Manager: - "Guys, we need to make this brand new ProjectX, here are the specs. What do you think?"

Bored Old Lead: - "I was going to resign this week but you've convinced me, this is a challenge, I never worked with this stack, I'm staying! I'll gladly play with this framework I never used before, it seems to work with this libA I can use here and this libB that I can use here! Such fun!"

Project Manager: - "Awesome! I'm counting on you!"

Six months ago:
====================
Cprn: - "So this part you asked me to implement is tons of work due to the way you're using libA. I really don't think we need it here. We could use a more common approach."

Bored Old Lead: - "No, I already rewrote parts of libB to work with libA, we're keeping it. Just do what's needed."

Cprn: - "Really? Oh, I see. It solves this one issue I'm having at least. Did you push the changes upstream?"

Bored Old Lead: - "No, nobody uses it like that, people don't need it."

Cprn: - "Wait... What? Then why did you even *think* about using those two libs together? It makes no sense."

Bored Old Lead: - "Come on, it's a challenge! Read it! Understand it! It'll make you a better coder!"

Four months ago:
==============
Cprn: - "That version of the framework you used is loosing support next month. We really should update."

Bored Old Lead: - "Yeah, we can't. I changed some core framework mechanics and the patches won't work with the new version. I'd have to rewrite these."

Cprn: - "Please do?"

Bored Old Lead: - "Nah, it's a waste of time! We're not updating!"

Three months ago:
===============
Bored Old Lead: - "The code you committed doesn't pass the tests."

Cprn: - "I just run it on my working copy and everything passes."

Bored Old Lead: - "Doesn't work on mine."

Cprn: - "Let me take a look... Ah! Here you go! You've misused these two options in the framework config for your dev environment."

Bored Old Lead: - "No, I had to hack them like that to work with libB."

Cprn: - "But the new framework version already brings everything we need from libB. We could just update and drop it."

Bored Old Lead: - "No! Can't update, remember?"

Last Friday:
=========
Bored Old Lead: - "You need to rewrite these tests. They work really slow. Two hours to pass all."

Cprn: - "What..? How come? I just run them on revision from this morning and all passed in a minute."

Bored Old Lead: - "Pull the changes and try again. I changed few input dataset objects and then copied results from error messages to assertions to make the tests pass and now it takes two hours. I've narrowed it to those weird tests here."

Cprn: - "Yeah, all of those use ORM. Maybe it's something with the model?"

Bored Old Lead: - "No, all is fine with the model. I was just there rewriting the way framework maps data types to accommodate for my new type that's really just an enum but I made it into a special custom object that needs special custom handling in the ORM. I haven't noticed any issues."

Cprn: - "What!? This makes *zero* sense! You're rewriting vendor code and expect everything to just work!? You're using libs that aren't designed to work together in production code because you wanted a challenge!?? And when everything blows up you're blaming my test code that you're feeding with incorrect dataset!??? See you on Monday, I'm going home! *door slam*"

Today:
=====
Project Manager: - "Cprn, Bored Old Lead left on Friday. He said he can't work with you. You're responsible for Project X now."

DO NOT let employers demoralize you into staying with the company.

I've been with this one company for about 2 years. Everything was great, despite being underpaid, and having a lot of responsibility (I was the only front-end developer maintaining 4 big eCommerce sites).
One day about 2 months ago, I got a better offer. Better pay, more freedom, and way less stress (Customers screaming in your ear vs. no customers at all).

I talked to my team lead since I wanted my company to have a fair chance to counteroffer - I was fairly comfortable after all, and I felt like it would be a nice gesture.
If my team lead had just said "No, sorry, we can't counter that offer", there's a big chance that I would have stayed with them anyway. Instead, I got a fairly uncomfortable and personal rant thrown back at me.

He basically said that I should be happy with my salary, that he didn't feel like I had much responsibility, and that "I wasn't the type of person companies would hire for that salary".
He ended by saying I might as well stay, as there was no going back if the new place didn't work out - basically trying to tempt me with job security.

I told him that I would think about it. The worst part is that I actually did, since his rant really made me feel somewhat worthless as a developer. Luckily I came to my senses, and sent my resignation the next day.

I talked to an old coworker today, and they are still unable to find a developer who wants to take the job. I see that as justice :)

tl;dr: If a company tries to make you stay by demoralizing you - Run.

Private chat pops up. (- separator for new message)

Hello
- (1 min)
Can you help me?
- (2-3 mins)
Please it's urgeeeent!!!!!
- (1 min)
Come on you're online, I see the green dot.
- (5 mins)
Ok then I won't be able to work. Will write this down in the ticket.

- (15 mins) - new private chat pops up
Hi, we need to talk.
- (3 mins)
Regarding ticket XY, why aren't you responding? It's really urgent.
- (5 mins)
Please notify me as soon as you're available, it's really important!!!

- (20 mins, new private chat opens)
Hi mate, I think the devs are up to mischief. Said you're not reachable, I'll try to poke them with the stun gun.

- (60 mins, message in the official and only endorsed support room)
@all We broke staging, <Me> never responds and <Team mate who tried to use the stun gun> wasn't helpful either.
We really need this now!!!!!!!

- 30 mins later... la me:
@all I was in a meeting with the stakeholders as we had an priority meeting... What was so important that you not only ignored the rule of not messaging privately and even ignored <team mate>s instructions?

- 5 mins later, answer
no need to be so unfriendly.... We broke staging as we had to test stuff out for next week's sprint review [something which is still 3 days away or sth like that]. We really need to take a look in the team at it and for that we must have staging working now!!!!
- (La me)
If you need it urgent now, you didn't plan ahead. And if you didn't plan ahead, you have to wait for others. The sprint review and all other important days are planned ahead for a reason.
- (Silence)

- (20 mins later, private chat, team lead)
Will you finally fix staging now?

- La me
If it could wait 3 hours now and you / your team ignored all netiquette, it can wait till next day, too. We had this discussion more than once, I don't think I need to explain this further.

(Silence)

All in all, the joys of communication...

Now the fun stuff is when this not only happens with 1 team, but many teams....

Having 35 - 40 private chats and chat window looking like a christmas tree thx to the immeasurable amount of notifications and colors... Yay...

Did I mention that I hate the ego some programmers have -.

To my ex manager

you left to berlin, and left me to rot

my new lead sucks, i kid you not

it was ok if I slacked off, You used to be chill

But my new lead is uptight, he's on my list to kill

I wanna run errands in work hours, is that so bad?

was doing so for years, now i lost what i had

I cant drive in peace, coz i know he'd call

so i had to cancel plans to go to the mall

its like 10 to 6 is now constant work

I hate my new lead, he is such a jerk

I was recently hired as a lead devops to a giant shit show. The CTO said he needs someone to do things correctly instead of quickly. This is a conversation I just had this morning

HR: We want you to interview a potential new DevOps engineer
ME: okay, when?
HR: Tomorrow
ME: I won't be able to create interview tests and materials for tomorrow. How's next week
HR: This hire is urgent! It has to be tomorrow
ME: Then you'll have to do the interview without me
HR: We need you to interview them because we've had a few bad hires in the past that we don't want to repeat
ME: The best way to filter out bad hires is with technical tests, which will take time to develop. I can be ready by next week.
HR: We can't give you a weeks notice for each hire, we are in urgent need for more devops.
ME: ...

I'm the lead dev at a tiny startup and was asked to write the job description for our open junior dev position since the new hire will directly work with me everyday. Since posting the opening online 2 weeks ago I've had 2 different recruiters contact me telling me about how my resume perfectly lines up with the job description ... no shit Sherlock, that's because I wrote the job description to find someone with my skill set.

So I've been messing with these recruiters. I told the last one I was interested so when he asked my salary I told him what I make but said I would settle for a lot less to get this job. Eventually he asked for my updated resume so I sent it clearly showing that I work for the company the opening is at. He called me back saying he's not sure what's going on so I told him I wanted to pursue the opening because I wanted to be my own boss. We both laughed but his was that nervous "I don't get it" laugh ... how sad for him.

Never have I been so furious whilst at work as yesterday, I am still super pissed about going back today but knowing it's only for another few weeks makes it baerable.

I have been the lead developer on a project for the last 3~ months and our CTO is the product owner. So every now and then he decides to just work on a feature he is interested in- fair enough I guess. But everything I have to go and clean up his horrendous code. Everything he writes is an absolute joke, it's like he is constantly in Hackathon mode "let's just copy and paste some code here, hardcoded shit there and forgot about separation of code- it all goes in 1 file".

So yesterday he added a application to the project and instead of reusing a shared data access layer he added an entirely new ORM, which is near identical to the existing ORM in use, for this one application.

Being anal about these things, the first thing I did was delete his shit and simply reference the shared library then refactor a little code to make it compatible.

WELL!! I certainly hit a nerve, he went crazy spamming messages on Slack demanding I revert as it broke ONE SINGLE QUERY that he hadn't checked in (he does 1 huge commit for 10 of everyone else's). I stuck to my principals and explained both ORM's are similar and that we only needed one, the second would cause a fragmented codebase for no benefit whatsoever.

The lead Dev was then forced to come and convince me to revert, again I refused and called out the shit quality of their code. The battle raged on via the public slack group and I could hear colleagues enjoying the heated debate, new users even started joining the group just to get in on mine and the cto's difference of opinion.

I even offered to fix his code for him if he were to commit it, obviously that was not taken well ;).

Once I finally got a luck at the cluster fuck of shit he had written it took me around 5 minutes to fix and I ever improved performance. Regardless he was having none of it. Still the demands to revert continued.

I left the office steaming after long discussions with the lead Dev caught in the middle.

Fortunately my day was salvages with a positive technical discussion that evening at a company with whome I had a job offer from.

I really hate burning bridges and have never left a company under bad terms but this dictator is making me look forward to breaking the news today I will be gone in 4 weeks.

From Bauhaus to Jessica Walsh, all the previous design experience and vision of the entire civilization lead to this.

This monstrosity is apple’s new battery icon in Big Sur.

I’m speechless.

Fuck my life...

Okay, so I’m working on a web app with a small group... the app is basically a lead generator for new business in another country. We just need contact details cause they’re a fucker to buy.

Step 1: prototype to the investors, working with the ceo to make this thing look shiny AF.

Goes well as fuck.

CEO: “when can we get this out?”

Me: “it’s basically done mate, get your guys to look at it and we can talk about marketing”

Que a shower of 10 or so bellends with senior in their title going into a room and coming out with:

Bellends: “so on this page we want the user to confirm and accept the contract”

Me: “cool, makes some sense, that’s what it’s already doing.”

Bellends: “afterwards we want to show them the price and have them put in their banking details.”

Me: “Wait, you what when?”

Bellends: “Yeah, well Jenny says we should have as few clicks as possible to get to the final stage and have the customer accept.”

Me: “Jenny’s on fucking crack, moving the contract formation phase to after the contract acceptance stage is not an option”

Bellends: “Oh it’s okay, Andy in legal said that would be okay”

Me: “Andy’s a fucking moron, tell him that online contract formation laws were updated 2014/2015 and you can’t do that anymore”

Bellends: “No, andy’s legal, surely he knows”

Bellends: “We want all of this above the fold”

Me: “OH FUCKING SUCK A DICK YOU ABSOLUTE BAND OF FUCKWADS... which one of you, which one hasn’t looked at a website this millennia!?”

Needless to say I ignored all their shit, got the lead generator out and told the CEO those ten people are certifiably fucking useless.

Bonus round; recent, but “it has to be on internal infrastructure”

“Why? It’s a mobile app sending rest calls to a third party saas.”

“It just has to, we have this thing called the private cloud and w”

“Wait... you what son, priv 🤦🏼‍♂️ private what mate?”

“Private cloud”

“You... you mean a server rack?”

“Nah we spent £2mn on it, it’s brilliant”

“Hahahaha you fucking dick, you blew £2mn on server infra with fuckall to put on it!?”

“No, no it’s the private cloud”

“Fucking idiot, aye son, where’s the fucking bean stalk you prick!?”

“It has to go on internal infr”

“Shut up, that won’t work”

Ahhhhh devrant... long time no see.

I just need to get something off my heart. The past two years, I worked for the same ISP in Germany, but now as a devops engineer. Well, popo hit the fan really quick lately..

First a good friend, team lead for one of five areas in Germany, quit his job. He was one of the nicest persons I knew, and he believed that all that five areas should work together and share dev resources. Thats why I work mostly in other areas as developer.

Shortly after, his deputy quit as well. I heard that this specific area, the management were a bunch of dicks, but wow!

A short while later, I learnd the hard truth, why those two good friends quit, and that brings me to this story. In a meeting I readied myself up to present my new plattform - a social room - to management. I got a lot of positive feedback from others and we thaught managment would approve of the project. But nope. "We can buy from external, we dont need to program ourselfs. In fact lets stop spending money on internal programming, we should outsource everything!"

I was baffeld... Wtf did i just witness? My team lead didn't say anything, and afterwards I didn't dare to question it, but I told most of my close dev friends and we all realizied, that the rumors were true... We will be shifting into project managment.

At this point, I realized that I wasnt having it, and made a linkedIn account, not because I wanted to switch jobs, but because, meh you never know.

One week ago, one of my bestest buddies said he will quit and join his team lead that left eariler this year, I was heartbroken. Me and our other buddy are devestated, because now we have to do everything he had done. Management didn't listen as we told them that nobody can maintain his code. I have so many projects, I can bearly keep up with them. Now I got a lead role for creating the server infrastucture for a huge project my buddy was working on. Only as specialist and not PM, but his Team Lead thinks I am replacing him!

Last week I got a message on LinkedIn, a consulting firm reached out to me to aquire me as a new consultant or devops engineer. They look great, only less vacation (26 instead of 30 days), 40h shifts instead of 38h and only slightly more base payment. I currently receive about 53.000€ a year, the new firm only grants up to 60.000€ a year for anyone. Otherwise, they look great.

With all my buddies quitting around me, work getting more while time developing decreasing, I don't know what the right thing to do is... There is no way I can get a payment increase in my current position. I always say "my workplace is save, but my work isnt". I don't want to do project managment.

Today I have a meeting with my team lead, she is really nice btw. This is an annual meeting where we discuss my future in the company etc. Shortly after, I have a meeting with the new firm to discuss a bunch of questions I have.

I dont know what to do...

Edit: I missed you, devrant

> Bang head against issue for days
> Finally get help from lead
> Watch them bang their head against it on video for 40 minutes
> Watch them shake their head in disbelief at how difficult to follow and objectively wrong the existing code is
> Talk through approach to fixing it and patching in the new functionality
> Listen to a short recap
> Ask question, get answer
> Chat about next company meet
> Meeting adjourns
> Jot down implementation notes before I forget
> Remember answer to question, forget everything else

FFFFUUUUUUUUUUU 😭

Recruiter: Hi practiseSafeHex, I’ve looked at your LinkedIn profile and you look like a perfect fit for my new client. The role is a lead Java developer with experience in .......

Me: Where on my profile have I listed or mentioned Java in any way?

LinkedIn Notification: a person who chose to remain anonymous, with the title “Recruiter” just viewed your profile.

Wow, I wonder who could it possibly be? I’m stumped!

Also probably the first time he did look. Getting fed up with these asshats

I don't want to write clean code anymore :(

I read Clean Code, Clean Coder, and watched many uncle bob's videos, and I was able to apply best practices and design patterns
I created many systems that really stood the test of time...

Management was kind enough to introduce me to uncle bob clean code in the first place, letting us watch it during work hours. after like one year, my code improved 400% minimum because I am new and I needed guidance from veterans...

That said, to management I am very slow, compared to this other guy, they ask me for a feature and my answer would be like "sure, we need to update the system because it just doesn't support that right now, it is easy though it would take 2 days tops"

they ask the same thing for the other guy : "ok let me see what I can do", 1 hour later, on slack, he writes : done. he slaps bunch of if-statement and make special case that will serve the thing they asked for.

oh 'cool' they say -> but it doesn't do this -> it needs to do that -> ok there is a new bug,-> it doesn't work in build mode-> it doesn't work if you are logged in as a guest, now its perfect ! -> it doesn't work on Android -> ok it works on android but now its not perfect anymore.

and they feel like he is fast (and to be fair he is), this feature? done. ok new bugs? solved. Android compatibility ? just one day ... it looks like he is doing doing doing.

it ends up taking double the time I asked for, and that is not to mention the other system affected during this entire process, extra clean up that I have to do, even my systems that stood the test of time are now ruined and cannot be extracted to other projects. because he just slaps whatever bools and if statements he needs inside any system, uses nothing but Singleton pattern on everything. our app will never be ready-for-business, this I can swear. its very buggy. and to fix it, it needs a change in mentality, not in code.
---------------

uncle bob said : write your code the right way, and the management will see that your code generates less errors, with time, you will earn respect even though they will feel you are slow at first.

well sorry uncle, I've been doing it for a year, my image got bad, you are absolutely right, only when there is no one else allowed to drop a giant shit inside your clean code.

note: we don't really have a technical lead.
-------------------
its been only two days since my new "hack n' slash" meta, the management is already kind of "impressed" ... so I'll keep hacking and slashing until I find a better job.

#feature request

Anonymous rants!

Let me explain, many people here have chosen meaningless usernames to them, to be completely anonymous, many others didn't... For example if you Google Etrunon I guess that you'll find me in less than 5 minutes...

So I believe that this may lead to less and less hateful, frustrated and liberating rants. Mainly because of three reasons: fear to be discovered from the outside(boss, etc) , fear to be discovered inside (colleagues or friends invited here) and the latter is the community building aspect of this app.

So what I am asking (knowing that should be a lot eheh) is the capability to post new rants either signed or anonymous... This to prevent being discovered let us having rewarding rants to read while on the same hand being able to connect and getting in touch a little bit with each other :)

What do you think?

@dfox @trogus

!rant

It's been months since I last posted in here, but I finally get to share good news for once!

I quit my current job and took an offer at a much better company in a senior developer role.

I no longer have to put up with an idiot tech lead who cannot either prioritize tasks or follow simple processes, a self-absorbed senior developer who keeps deleting my code for his because he prefers tables over divs for layouts, and an incompetent HR manager who is more concerned about his image than the welfare of us employees.

I felt pure bliss when I handed in my resignation. I feel focused and ready to tackle my next challenges at my new job in January. I can't wait.

My personal learning here is that while good things come to those who wait, it still needs you to take that first step yourself and without hesitation.

I played a lot of Command & Conquer when I was younger, and I remember going through the files for C&C: Red Alert. I found one that had all the units names and properties, and wondered what happened if I changed a value. So I changed grenadiers attack speed to something ridiculously fast, and found that it actually changed it in the game!

The light bulb went off in my head, and I then created new units:
- Albert Einstein that shot electricity
- Attack dogs that launched missiles

Granted the animations didn't exist for these so it defaulted to playing their death animations when attacking, which was amusing.

That was the ah-ha moment for me that lead me to pursue programming. It was just so much fun!

Day 1:

Me: 'Hi'

Middleware guy: 'Raise a Jira. We have always been so accommodating. Contact your manager.'

*Jeez*

===

Day 2:

Me: 'Could you please start the server in dev environment? I am a new joiner. I don't have access. Here is a jira.'

Middleware guy: 'Deadlines may be for you. It is not for me. Wait until tomorrow.'

*Damn, did he get a divorce recently?*

===

Day 5: *An urgent delivery asap* 'Hi, could you please do the configuration of the new app in staging?'

Middleware guy: 'So, here is the split up...
Task 1
Task 2
Task 3
Task 4
Task 5 & 6
Your app will be configured by tomorrow first half hopefully.. Oh and you can escalate if it is too late..
'
*What a b...*

===

Day 8:

Me: *Doing late sit for pushing a task* 'Hi, we have an issue. The server is not starting. Could it be due to..'

MW guy in 'second' shift: 'Oh, we don't extend support on unusual hours'

Me: 'But this is second shift.'

MW guy: 'Yeah, but I have to go home early now...'

====

Day 10:

Team Lead: 'Any innovative solutions?'

Me: 'Let's go SERVERLESS!' :D

!rant

I got the job!

Yesterday morning I got a call from the wonderful recruiter I’d been working with, to say they were giving me a decent competitive offer 😄

After handing in my notice, backing my colleague, trying my best to look after the current employer... it paid off, I have the job that I wanted.

The guys at the new place really impressed me out the gate, clever, decent people doing some interesting stuff.

Senior is going back in my title where it belongs.

Basically it all worked out in time for Christmas 😄

I’ve been tracking this little saga on a tag but if you want to know what lead me down this route my previous rants are there. I’ll continue to rant as I finish in the current place and move on to the next 😄

Client: We want an application such that our users can view the 3D rendering of the building we are constructing for them
PM: That's quite easy, we'll get it done
Client: Oh, and the output should be a PDF document, such that they can view the 3D rendering on a PDF reader on the go
PM: That's not a problem, it'll be done

--Right back at the office--
PM: Hey guys, this is our new project....(rants on)
Lead Dev: (in a world of indescribable world) You mean you agreed to that? That's impossible
PM: Just get it done

I wish non coding PM's asked their devs before agreeing to some alien like features

Lead Dev: Just use jQuery, it'll save us from adding a whole new directive in Angular.
Me: 🤦‍♂️
Coworker: 🤦‍♀️

Ugh, fxk. I got a promotion, I'm now a team lead for 4 developers, and I fxking hate it.

They never asked me if I wanted the position, they just threw me into it this week. They ripped me away from the team I had great chemistry with and put me on this other team with people I have no connection with.

To make matters worse, I'm also responsible for production servers of the clients of this team, one has malware even.

On top of all of this, they made me move desks for a new developer to fill my spot.

How do you demote yourself? Why would a company want someone to perform poorly (on purpose, I don't care) than to just keep their employee happy?

/end rant

I started this new freelance project where I am building some android libraries for the client. Anyways, during meeting I was about to present my results and suddenly backend seemed to be down. I looked into the round "are your servers down?"
Team Lead: "Yeah our cto, also our only backend dev, is developing a new feature."
Me: "Okay but why is production down?",
Team Lead: "Ah dont worry we always test on production. We have a pretty solid hardware, we will even upgrade it soon!"
Me:"... How about you just separate your stage environments and have a develop environment?"
Client: "see, this is where our strength is. We dont need a develop stage we have very strong hardware and our backend is fully in PHP"

Thanks God I'm a freelancer

What the fuck!!!!!

Never thought I'd have to rant so soon joining my new org.

Guess the honeymoon phase is over earlier than I anticipated.

1. This company is awesome and employee friendly. They made me kickass deal which I couldn't refuse. However, upon checking glassdoor, I realised they still managed to low ball me. Lol.

But I have no complaints and I am pretty happy with whatever they are offering as of now. My next point is the primary reason I disabled my app blocker to rant out.

2. A junior is leaving and so is my lead. Damn! Fuckkkkkk!!! My lead is super awesome. There's so much dependent on her.

Entire organisation is watching the product line she and I am working on. It's the heart of the entire product.

It's just been a month I joined and so much responsibility on me already. Well, I am not fearing that.

What I am afraid of and rather uncomfortable with is that they are going to hire someone else in a different time zone who'll lead this entire thing and they might map me under that new person who'll be a senior level executive.

Fuck that shit. I don't want to leave my current manager for she is awesome too. With departure of my lead, it's just me and my manager that are left in the team.

I am not sure what the future will be but I know that there are lot of learnings coming my way.

One thing I wish for is that they relocate me for short or mid term to UK or EU. Then a lot of things will be solved for me.

For now, I am just keeping my head low and doing what best I can, which is focusing on work.

Hope they promote me with an amazing salary hike.

At a former job, the company decided to replatform to Salesforce. The entire dev team was laid off. But it would take an outside agency a year to build the Salesforce site. The company wanted the devs to stay for an additional year.

The only severance was something they called a stay bonus. It was 30% of our gross income but it was still contingent on performance. And if they decide to let you go earlier, it gets prorated if you still qualify for the bonus. Not a good deal.

Each month a dev left. By the time I secured a new job and left, all that remained of the dev team was a junior frontend dev and two team leads (one FE and one BE) with no team to lead. Well, there were contractors, but they were only brought on after the Salesforce replatform announcement. I’m pretty sure the company had to hire even more contractors. No idea how much that cost them.

For me, I think it was serendipitous that I gave notice during their busiest time of year. They actually tried asking me to extend my notice. Karma was coming back to bite them. Not just for the Salesforce thing. But also for their lack of support when I was blindly accused of being both insubordinate and incompetent.

I was laid off right before Christmas because my manager would not give me any work (bully.. possibly discrimination). I asked for work to do for 2 weeks, even coming up with things to contribute on my own. My contributions were rejected and the lead developer agreed with me that it was fucked up but did nothing. The little work that I was given was always completed above standard and the lead dev had made comments praising my self tasked contributions but each rejection I was told it would be shelved for version 1.2.

Finally fed up, feeling as though I was being completely ignored, I told the lead dev I was going home half day early if there was nothing for me to do. The next day the CTO fired me and even lied to my recruiter telling him that I had not shown up for work for 3 days (easily disproven).

It's now the first of the year, probably not the best time to be looking for a new job, and my current outlook is that I am not going to be able to pay my rent at the end of the month.

My motivation has diminished, my confidence is gone. Job prospects are few. I don't know how to proceed.

Company: your hired, lead our X dev team.
Me: yay.

-- three months later --

Company: we arent supporting X anymore.
Company: gonna offload all X clients in 90 days.
Me: oh.
Company: but you should stay around, learn new tech
Me: is this a charity case?
Company: yes, but we both win.
Me: how?
Company: you can keep your salary.
Me: deal.

#First

I joined a start up and worked after college hours as an intern over there. I would usually bunk my college and go to my internship. I had limited knowledge at that moment. I worked very hard over there because I wanted (still want) to gain practical knowledge.

Almost a month into it and I had to take a break from it because I had college work. Rejoined the same start up during my vacations. Worked quite a lot and learnt quite some stuff. I continued the internship after my one month vacation for another month once my college started. All this while I was not being paid, not even a little bit of allowance. But that didn't matter because I wanted to learn

Fast forward six months to November 2016. I have been placed in an MNC through my college placements. One day I get a call from this start up owner(we had become good acquaintances by then) if I was willing to work as a paid intern while I was working on the projects that the company landed (so I guess as a free-lancer) and as an unpaid intern while I was working on the company projects. I agreed. Jump to December. I have joined and started working on an Android project of this very big company.

At time point, I should inform you'll that I'm not very good at Android and that the company size is very small. Company owner plus the tech lead in one city (where I'm from) and another two full time employees in another city. Out of which one quit to start his own company apparently. The start up would primarily employ interns and provide exposure to them while getting their work done.

Back to the story. The tech lead vaguely assigns everyone their work. Everyone over here includes new interns and previous interns like me who will get paid some amount. 3-4 days into the project, the tech lead quits. The tech lead and the company owner call three of us and says that one of you will have to be a project manager for this project. And then both of them and 2 of my colleagues look at me. And I don't know what to say. I hesitate initially because it's too much responsibility but agree to it finally.

The next day I come to office and read about the project thoroughly and catch up with my colleagues about the progress. The entire day I'm panicking about what I'm going to do. In the evening, my boss tells me that we have to go for a meeting with the client for whom we are doing this project. At this moment, the shit out of me has been scared. Mostly because I don't know what the fuck am I going to do over there apart from being stupid and asking dumb questions. So we reach the client's office and wait for him. The entire time I'm thinking to myself that I'm going to drown this company by opening my mouth. Surprisingly, all the questions that I asked seemed legitimate and I asked a lot of questions. And so I didn't drown the company after all...phew!

It's been more than a week. And holy fuck! What a pain it is to manage people. Half of my time is spent on updating excel sheet about their progress, where are they stuck and what is needed. And the other half about thinking what the fuck am I doing or how am I gonna do it.

So to sum up, intern-turned-freelancer-turned-project manager who has no idea what the fuck is going on. Seems pretty crazy, don't you think.

Started working on a new project. One test failed, after unsuccessful tries to fix it, I ask the team lead for advice and help.
The guy takes a look and just deletes the test and says "There, done!"

Today I quit my job lol.

In my two previous stories I told you guys about a job offering I got, and after a few more incidents in my old job, I decided I take it.

No, this is not an april fools joke, though it felt quite bad to tell my team lead that I quit on april fools day.

Due to notice period I'll begin my new work at first of july this year, can't wait <3

You know you're fucked when even the lead dev can't think of a decent solution for your problem which is...
.
.
.
.
.
.
.
.
.
.
... the most difficult challenge devs have ever faced:
.
.
.
.
.
.
.
.
.
.
What should be the name of the github repo for the new module?

I'm a tech lead for a digital agency.

Digital agencies are universally known for being shite. Why? Because they typically push through sub-optimal code with very little testing over tiny deadlines for maximum profit. Maybe I've just had bad experiences but this is the 5th digital agency that I've worked at that does this bollocks.

I am currently sitting on a Teams call at 8:39pm because the fuckwit project/account managers are unable to face up to the big scary client and ask them terrifying questions like "Is this bug a blocker for the deployment?" or "We don't have enough time to fix/change these things, can we delay another day?". They just assume that A - We will work into the evening, and B - that all the issues are P1 and that we should all 'pull together' as 'team players' to get this done in time.

No, Me and my team have to work into the evening for seemingly free because these pricks can't do their jobs properly.

The funniest thing of all? When I speak to the CTO about overtime payment he tries to make me feel bad about "we don't typically pay for overtime..."

Fuck Everyone.

Time to find a new contract.

My Love I am writing to you from the front lines roughly 1 month into Microsoft Access. I hope you are doing alright and no harm has found you.

You might have heard the news that it has not been going well for us. The truth is we were not prepared in any way for this. We are constantly facing problems with the code and when we understand one function another two are referenced inside of that function.

The high command does not provide us guidance, truth be told I do not think they know what their application is doing. I am surprised we got this far. Our new objective is to focus our primary forces on the if/else and cases. The name for this assault is "Operation Logical Function" and I fear for my life as I do not know what is in those cases or where the road will lead.

Morale is very low, many of the soldiers spend time writing letters to their loved ones, recreating their blog for the 5th time or just daydreaming when they were free from this tyranny of legacy war.

For now , I long to be in your arms and smell your lilac and gooseberries cologne I love so much

My love and thoughts always with you , your John

**Overheard new intern struggling with git talking to lead developer

Intern: "I am having trouble with the git repo on my local machine, can you take a look?"

*** Looks at code for three seconds

Lead developer: "Yeah, I suggest you just delete and reclone the repo."

Manager: I want the front ends to be more dumb, too much logic is happening on the frontend.

Me: both of the sites are just multi step forms, I’m confused about the complexity part.

Manager: yea but don’t we have a bunch of third party api calls?

Me: we have 4 and they are public facing apis.

Manager: yea, make a new api and move this api calls to the backend and I want both frontend teams to send the same shape payload.

Me: but…

Manager: oh and I don’t like how the business team does the a/b testing and splitting traffic, let’s move that to the backend as well.

Me: but… that a/b testing platform they use in ran by another team and they have a full set of features for business analytics…

Manager: yea let’s just replicate those features and move them to the backend.

Me: but it’s a product!

Manager: look! You are the best backend engineer we got! I know you can do this!

Me: I lead the frontend teams…

Manager: ….

Manger: good news we are giving you a promotion with raise you are now a senior engineer.

Me: I confused but happy… I think..

I had a huge epiphany on Friday... not all developers enjoy coding.

Discovered when they brought down 2 of our environments, well told them what was wrong with the changes in their code that caused the environments to break, gave them links directly to the file in the gitlab repo that needed to be updated, and...

They fucking went home. The change would’ve taken all of about 30-45 seconds to update and they fucking left.

This person’s team lead come storming in pissed off because her manager is furious about 2 environments going down and preventing everyone else from being able to deploy their changes.

We provide the exact same details to the team lead about what needs to be changed, and advise that her team member took off....

30 mins later, her manager is storming up to us (devops/sre) livid as hell.

Explain the situation for a third time... manager is like, why can’t you guys fix it?

Look here you dense motherfuckers, we can fix the code. We can be the plumbers that clean up your shit. But what value do you gain as a developer if you don’t understand how the systems work and you keep pushing shit in?

Made the changes, fixed the environments, done right? Wrong.

The original developer made more changes not knowing what would happen and thoroughly fucked the environments again.

This dumb-fucking dumpster fire of a dude then sends us a slack message. “It’s down again, can you fix it?”

Our manager steps in and tells us to send him a link to the logs and have him fix it himself!

Thank goodness we have a badass manager.

Send logs, send repo file links (again), and send line numbers in the logs to try and help just a bit more. Dude goes almost the whole day without fixing it, environments are down, other devs are pissed, we throw this dude to the wolves. His manager starts to head over and was about to talk with my team lead when our manager steps out of his office and tells him the in’s and out’s of the situation and that our job isn’t to play log parser/error fixer for the developers. This dude that’s breaking the environments needs to be the one to fix the issue and his team lead should be aware of the problems and should have been able to correct his errors before it ever came to us.

The amount of hand-holding we do is ridiculous.

(Disclaimer, this one guy making some mistakes doesn’t sound too bad, but this is actually a common occurrence for like 40% of all of our developers)

We literally have interns still in college running circles around some of our full time devs. I know I’m not a developer, but for anyone that’s new-ish to developing, when you see shit like that please don’t lose hope. Those ass-hats got into programming purely for a paycheck, not because of passion.

Stick with it and your greatness will know no bounds 👍

As for you craptastic dipstick lickers, FUCK YOU!!! Go back to school and learn how to give a damn.

An old company contacted me, seemed remorseful and said I probably didn't want to work there again but kept pushing. Eventually he said a high salary and I figured ok they had easy projects and the overpaying would beat the underpaying they did while I was there, right?

The new lead dev at the place took a month to give me work, tried to pressure me by saying she was going to tell management they are behind because of me, and then progressively stopped assigning tickets to me and assign-then-reassign them from me according to my schedule/predictions I revealed during the daily stand-ups. Why hire me at all. Then they said they changed their business direction at 3 months and let me go. What a waste of everyone's time.

A colleague named Sam was really pissed off today at an out sourcing firm from India.

My Boss outsourced an application to India based firm. Sam was the one handling the project after the handover. Sam coded a feature 2 weeks ago and moved to staging server for approval. After the sign off from the lead developer of the outsourcing firm, he moved the feature to production. For the past 2 days the application was crashing over and over again so Sam went to check and found out that the feature he coded was causing the issue. When he pulled the feature to his computer and had a look at the code, it wasn’t his code. The code he wrote was commented out and the lead developer of the outsourcing firm wrote new code.

When Sam emailed to him regarding this he replied that he re-wrote his code to fix issues with the feature. Sam and outsourcing firm lead developer had heated argument about this. It’s turns out that the outsourcing developer re-wrote the code without anyone’s approval and on production server.

The lead developer of the outsourcing firm was fired.

Oh boy.

I've been partially on-loan to another team that's relatively new at the company for a couple of weeks now, mostly to help them get some testing sorted out, and had scheduled a call with their lead the other day. The call basically started like this:

Lead: Hi
sudo-woodo: Hey
Lead: Okay, so let's talk about <subject>, but I guess you've been told the news
sudo-woodo: What news
Lead: I'm putting in my notice

I love listening to seniors because they always drop some wisdom, but this was some serious wisdom. Guy sounded exhausted at everything, talking mad shit about the company and certain people and I'm just here like 🍿. Seems understandable, a lot of butting heads with the higher-ups and not being able to do his job properly.

Unfortunately we all kinda needed him to do his job because his job involved juggling fifteen different things that the project (and like 90% of my backlog to be honest) depends on.

shit's fucked 🙃

Dear recruiters and so called "startups".

If you want to attract me by starting with the phrase: "Mobile lead role in Startup" and you go on like...

"We are a startup with offices in Shanghai, Hongkong, Vancouver, San Francisco, New York,... "

or

"We are a startup and also the 6th biggest phone network in the world... "

No thanks, enjoy your startup themed cubicles and fuck off!

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.

Funniest meeting ever!

Some years ago, there was the regular department meeting where useless news from upper management were handed down. The team I was in was also there: team lead, co-worker and me. The team lead had a new girl and was daydreaming of their nights, my co-worker wasn't quite back from the football match on the weekend, and I was playing chess on my mobile.

Department lead was blah blah blah and when can we do this on your rig? We looked at each other and instantly realised that none had been paying attention.

My co-worker was the fastest to recover and straight-facedly turned to me: "Well Fast-Nop, that's your domain."

I picked the ball up before team lead could say something: "Sure, but schedule appointment is for our lead."

Our lead couldn't contradict us and then had to negotiate a schedule while trying to find out what it was about. *LOL*

Sprint planning meeting, two hours trying to plan what to do with a new feature we wanted to add to one of our systems.

The boss gets out of the meeting room to get a phone number to make a call (we needed to ask something to one of our clients).

5 minutes later, the boss comes back and saw that the lead dev was going to his own desk.

Boss: Where do you think you’re going?
Lead dev: I’m bored :v

😂😂😂😂😂

Felt so awkward today. Bare in mind I am still a junior. I was on a pull request reviewing session on a repo I use. I was being super super pedantic with variable names, data types etc as the people who wrote it are brand new to the company. I then realise I had just reviewed the companies lead developers PR to a different repo. Every time someone comments on a PR on this repo all developers in the company get an email notification. I sat there litrually sweating, bright red with the words 'oh ****' on an infinite loop in my head, staring at the screen waiting to see what was to happen.

Thankfully he was ok with the comments. But now people keep calling me the lead developer (teasing) fml I hate anxiaty

Welp. The startup I'm working for is going under. Ceo gave us zero hints.

I'm the lead dev and been working here for 6 months. Always built features before deadline, zero bugs, and going an extra mile. Can't say the same about the sales and marketing guys.

Kinda scared its gonna look bad. Oh you led a failed startup? Must be your fault.

Guess my side business is becoming full time now. Until new job.

#startup #9/10 #icebergahead

Fucking idiot lead dev who’s 10 years younger then me doesnt know fucking respect. Dumbass comes with every new framework there is:
- ow we should try abc.js
One week later
- now we should totally get in def.js. It’s soooo much better then abc.js!

Screwing up projects, asking for an extra pair of eyes and then asking wtf is this code.

Im out of here if we’re hiring toddlers for lead developers because they are willing to work 50 hours a week. I better get that raise soon.

Long time lurker, first time poster. This site has been a huge source of fun and laughs for me on bad days.

So dear fellas,

I've been a software engineer for about 5 to 6 years which was intense as fuck and I've been burnt out multiple times. My highest rank was a senior software engineer so far.

I was offered a new job recently as a Technical lead for a small team which would mean I have to make architecural decisions on top of good ol grunting out the code. I took up the offer but I'm more worried than happy.

Impostor syndrome has kicked in heavily ever since I agreed to the job. What if they realise I don't know certain things that engineers are supposed to know? What if I get in an embarassing situation where somebody asks me a question and I'm not able to answer? What if people who I work with laugh behind my back cos I'm not a rockstar engineer?

I'm depressed and scared as fuck right now. Usually I had someone senior to ask my questions or get my doubts cleared with, now it looks like I'll be making those decisions and getting things done and I'm shitscared and worried as fuck.

Does anyone have any pointers, tips or anecdotal advice that might help me? It would be much appreciated.

Sorry for the incoherent rant. Have a good one y'all

Dogecoin hit USD $0.40 recently, which means it's time for the Crypto Rant.

TL;DR: Dogecoin is shit and is logically guaranteed to eventually fall unless it is fundamentally changed.

===========================

If you know how Crypto works under the hood, you can skip to the next section. If you don't, here's the general xyz-coin formula:

Money is sent via transactions, which are validated by *anybody*.

Since transactions are validated by anybody, the system needs to make sure you're not fucking it up on purpose.

The current idea (that most coins use today) is called proof-of-work. In short, you're given an extremely difficult task, and the general idea is you wouldn't be willing to do that work if you were just going to fuck up the system.

For validating these transactions, you are rewarded twofold:

1) You are given a fixed-size prize of the currency from the system itself. This is how new currency is introduced, or "minted" if you prefer.
2) You are given variable-size and user-determined prize called "transaction fees", but it could be more accurately called a "bribe" since it's sole purpose is to entice miners to add YOUR transaction to their block.

This system of validation and reward is called mining.

===========================

This smaller section compares the design o f BTC to Dogecoin - which will lead to my final argument

In BTC, the time between blocks (chunks of data which record transactions and are added to the chain, hence blockchain) is ten minutes. Every ten minutes, BTC transactions are validated and new Bitcoins are born.

In Dogecoin, the time between blocks is only one minute. In Theory, this means that mining Dogecoin is about ten times easier, because the system expects you to be able to solve the proof of work in an average of one minute.

The huge difference between BTC and Doge is the block reward (Fixed amount; new coins minted). The block reward for BTC is somewhat complicated compared to Doge: It started as 50 BTC per block and every 4 years it is halved ("the great halving"). Right now it's 6.25 BTC per block. Soon, the block reward will be almost nothing until BTC hits it's max of 21 million bitcoins "minted".

Dogecoin reward is 10,000 coins per block. And it will be that way for the end of time - no maximum, no great halving. And remember, for every 1 BTC block mined, 10 Doge blocks are mined.

===========================

Bitcoin and Dogecoin are now the two most popular coins in pop culture. What makes me angry is the widespread misunderstanding of the differences between the two. It is likely that most investors buy Dogecoin thinking they're getting in "early" because it's so cheap. They think it's cheap because it isn't as popular as Bitcoin yet. They're wrong. It's cheap because of what's outlined in section two of this rant.

Dogecoin is actually not very far off Bitcoin. Do the math: there's a bit over 100 billion Dogecoin in circulation (130b). There's about 20 million BTC. Calculate their total CURRENT values:

130b * $0.40 = 52b
20m * $60k = 1.2t

...and Doge is rising much, much faster than BTC because of the aforementioned lack of understanding.

The most common thing I hear about Doge is that "nobody expects it to reach Bitcoin levels" (referring to being worth 60k a fucking coin). They don't realize that if Doge gets to be worth just $10 a coin, it will not just reach Bitcoin levels but overtake Bitcoin in value ($1.3T).

===========================

It's worth highlighting that Dogecoin is literally designed to fail. Since it lacks a cap on new coins being introduced, it's just simple math that no matter how much Doge rises, it will eventually be worthless. And it won't take centuries, remember that 100k new Doge are mined EVERY TEN MINUTES. 1,440 minutes in a day * 10K per minute is 14.4 million new coins per day. That's damn near every Bitcoin to ever exist mined every day in Dogecoin

> Last year wrote a unittest - I was asked to delete it
> no design patterns. Not a single one
> no encapsulation
> fucked up inheritance [I had no idea it was possible at all...]
> generics every-fucking-where
> I could go on...

this month the lead dev was not in and I had to make a new feature. Guess what I did :)

tdd [coverage >90%], a couple of builders, a factory or two, two composites, one decorator, only a few generics - only where really needed. Private fields, not a single @Autowired field [they were fucking my tdd], nicely abstracted integrations, and so on. Everything is writen according to clean code: max 10loc methods, <140col lines, reusable constants and utils, SOLID as a rock, etc.

Due date is next week. Took me 3 weeks to craft it.

Guess who's gonna be piiiiiiiiiiiiisssedd 😁

the best part - I don't even work there, our company was hired for xx hours as helping hands 😁

that's not all. They have like 6 envs and their deployment is all-fucking-manual. Will try to learn how to dockerize that app and deploy it on docker. Gosh I wish I could see his face when he's back 😁

p.S. From ethical point of view, he's the only dev who believes his code is perfect. No other dev in the team agrees. AND he once said: 'it's gonna be my way or no way at all'. So I don't think I did wrong... Did I? :)

When the new keyboard you ordered arrives at work (it's for at home) and your team lead remarks 'that is a big dildo you got there'. I did fire back by asking him if he was jealous which led to sudden silence. Still disappointed in him, we do rib each other all the time but this feels sexist and inappropriate. I'm used to it and laugh it off but I'd still expected better of him.

I once worked at a small dev shop with a team of about 5. I was the lead but I was also the only backend developer. Since it was such a small company I also managed the Datacenter... which we had in our building. It was messy, but impressive. Although I seemed to be always stressed and felt like my job was always on the line... I do miss how excited I got when I learned something new. I was then able to talk to my boss about how excited I was to learn it and I can't wait to learn something new. I'm sad because I don't get that excited anymore. Now, I'm not really learning anything new, I'm just posting my skills as a developer. It really bums me out. I only wish that I had a degree in computer science so I can become a teacher and see my students get as excited as I was.

After 3 months and around 5 projects at my new job, I've finally come to the realisation that the developer in charge and I disagree on everything, all tech stack/browser compatibility decisions are made completely blindly and no matter what, the lead (full stack) dev refuses to take any of my frontend expertise/knowledge on board.

how did a startup become this rigid and terrible?

I already want to quit.

it was 12am when we are ready to launch our new web design which requires a lot of hardwork and routing processes. my team lead was the one who pushes the button to production using "cap production deploy" command. everyone in the room (including PM) was like counting down like launching a rocket to space. the feeling is great knowing that everyone was sleepy at that time. im glad it went smooth and everyone congratulates each other.

Part 3: today has become a blog post.

WARNING: this is loooooooooooong

Background is my boss and I were talking about hiring the right people, also generalists vs specialists.

Essentially John and I are the specialists. When something goes wrong it ends up escalating to either him or me. But this is not sustainable as I can't handle the stress and most likely he eventually won't either.

And this goes back to general hiring standards.

All the good people leave and the remaining ones are stuck with all the problems and eventually for one reason or another they leave as well... or the code keeps getting worse... until someone decides to scrap everything and build a new one... But now the only people left to lead teams are monkeys.

Now current problem is the only person that can replace me is John and the only person that can replace John, at least in handling issues, is me...

It's a certain type of person, people that have a growth mindset and can pick things up.

Google and strong tech companies are full of these types of people where if needed there's always someone that can step in and help. They have the background and the ability to quickly learn. This also lets them innovate and identify and solve new problems.

I think that's what the technical interviews are for, to find these types of people.

And you really can't train this. I'm not sure how effective our "new" training program on high quality development is but I'm guessing it's not. Excellence has to be in the culture and it's not something that can be built overnight or by randomly hiring people.

So in a sense, tech companies aren't really paying well, they're paying cost to what their hires are really worth, after they've verified it, and enough to keep them from leaving.

Okay, seriously, are there some secret question-asking ninja skills i am lacking, or does some people just insist on confusing people and wasting time?

I was working on this small bug. Super tiny. Basically a counter that was way off since it counted some duplicate values. Simple, right?
I decided to ask a clarifying question to the lead dev, since i am still new to the company. Really simple. Do we remove duplicate values, do we ignore them in the count when they occur, or is it actually working as expected?

He decides to answer with a long message on what the issue is. That is not what I asked, so I ask again in a slightly different way, thinking he didn't understand the question.. and he answers the same, in a slightly different way.

We go back and forth like this for 30-40 minutes, until I got tired of it and directly asked "I am asking what solution we want, not what the issue is"..
He finally picks option A. Fine. I made the adjustment and pushed my code. He checks it out, and apparently it's wrong.

After a long series of questions (again), it turns out the solution he now describes is exactly what I listed as option C...
A bug that should take 10 minutes to fix ended up taking over 2 hours. Awesome waste of time.

Forgot to close() connection to the postgres and opening the new connection was inside of the query loop... So I successfully overfilled all the possibie 100 connections to 5 dbs out of 6. I have no direct access to them so I cant delete them. I'm still on probation and I have to go to lead dev and tell him that I messed up...

My most satisfying bug fix?

I found a core concurrency issue in this gnarly homegrown ORM and reported it to the lead devs, who (very defensively, having written the damn thing) argued that it would never pop up in a prod environment and I was stupid for even bringing it up. Theoretically, this bug could cause pretty much every foreign key to be assigned to the wrong parent, but only if multiple instances of the application were open/running at once. They were so certain it would never happen on live that they explicitly instructed me not to fix it. After all, this bug had been active for many years on a previous project and nobody complained.

Problem was, that previous project was something that only a single user had open most of the time (think: a manager). The new project was something that would be used by multiple people at the same time (think: all the employees). Once we released this new-project-with-old-orm, it didn't take long at all for our customers to start complaining.

After that, they let me fix the bug. :)

Writing the new software dev test for our incoming interview process.

Me: And here is where we ask them to parse HTML with regex.

Lead developer: You are fucked up and the villain of this movie, multiverse and everything in between, fk u.

CMS Admin: And I thought Palpatine was evil. That is legit fucked up, fk u.

I was working on a team with people with various employment statuses. Contractors, employees of the client, and me as a regular full time employee of the company that “owned” the contract. My HR manager gave us a presentation about our reporting structure. I had at least seven managers for different reasons across various projects.

I got a new position so needed to resign but I had no idea which managers were the ones I should notify. I looked at the org chart that the HR lady showed. I sent my resignation to five managers that would be affected by my leaving. Unknown to me my project manager was actually a contracting manager hired by the client. He let his employer, the client, know that the lead dev quit.
Apparently it destabilized the contract for my employer. If I hadn’t just issued resignation they would have fired me for telling a customer about a significant internal staffing change. They didn’t fire me because the optics would have been worse for them.

Just joined a new team at the organisation as senior dev.

Team lead keeps singing about how we need unit testing and good standards.

I implement domain pattern on the backend supported by unit tests.

It passes QA and then get an earful about the code not being 'restful'. What does that even mean?

Well, it matters not since team lead changes the whole feature in the release branch and all unit tests obviously fails. Builds start to fail.

The solution? Comment out all unit tests. In the sprint retro, we hear the same old adage 'we need 80% code coverage'

Do as i say, not as I do. FML.

Feeling sick as fuck. Stayed home instead of going to work but I am already upstet about what is happening whilst I am not there.

The manager was gracious enough to task the other developers with creating the templates for one of our projects. I submitted a document before stating our design guidelines and how under no circumstances they should not use bootstrap for the design since none of them know how to manipulate the source code enough to deviate from the standard bootstrap design. The lead developer, even tho I love the dude, has an attitude against new tech. He is primarily and only a php developer still in love with just jquery and php with no real knowledge of proper design methods. He is the kind of dude that would tell you that pdo is a waste of time and that why should we create models and use oop to separate our code into manageable files.
Today I get "why should we not use bootstrap" and shit like that.

Sigh.....i really don't want to see the shitstorm waiting for me tomorrow.

Funny how our cms administrator is eager to learn the list of technologies i proposed. They both gor Programming Ruby, the pickaxe holy book of Ruby and the dude is already halfway through it while the other developer is still asking why should we even bother when we have php.

I get the idea of if it ain't broken don't fix it and being proficient with one stack and whatnot. But that idea of i dont want to learn something new is precisely what shuts down progress.

We hired a new senior dev. The lead architect is going over basic bit branching and commits with him. This new job already feels like a dumpster covered in petrol.

Oh boy... something just happened I'd have never expected.
Remember my rants about the PHP CMS Of Doom™?
Guess what... the boss of said company just called me to offer me a job as their new tech lead. WTF.

I'd rather slowly impale myself on a rusy pickaxe.
I'd rather tattoo my face with a giant, pulsating, uncircimcised shlong.
I'd rather take a swim in a pool of Hydrogen fluoride.
I'd rather work 80h/wk on pimple extraction.

I think there is such a thing as "getting too comfortable with the people you work with".

My boss came over and wanted to show me how to do a new process. We start going through the steps and a question arises. I then IM my team lead, because he's the one who would know the answer, and all I get back from him is sarcastic comments and profanity (he doesn't know my boss is sitting at my comp with me). So I keep trying to get him to be serious, and he just keeps his mouth (well, fingers) going. (He is remote - not in our bldg). I want so badly to shut him up because what if he says something about my boss while she is sitting there? Not that he does that, but at the pace he's going, it no longer would surprise me.

There should be some sort of code to hint to your team to STFU and give a fucking answer when one is needed. Sort of like what kids do to hint that a parent is in the room, but for work?

Hi Lead Architect,

Oh? You want me to explain how database clustering works? I guess you're just testing me because I'm new and junior.

Oh, and also explain how load balancing works? And what a bastion host is?

What's the architectural intent of this project? Let's have a look at the documentation and diagrams you have been creating of your designs.

You don't have any? That's okay, you've only been leading the architect team on this project for a year now.

Why don't you just keeping asking the most junior dev on the team about how the fuck you are supposed to do your job. As if I know how to do your job when I have zero training and am just expected to know everything.

Oh, its 3pm and you're heading to the pub. That's cool, I'll just guess what I need to build.

My team lead be like when we're in a meeting with the boss:

He: I'll have a working session with her, we'll brainstorm on how to come up with a better design and improve such and such feature, once that's done, we would call you to have another meeting.
Boss: sounds good, I'm looking forward to it.
Me: *internally rolls eyes...*
He: thank you everyone.
.
*meeting done*
.
.
.
couple of minutes later, I get a message from him:

He: hey, it turns out I'm busy and I can't have that session with you, do come up with a new idea/design and share it with me.
Me: .... *fuck you, like you didn't know you were busy before making that fake promise*
.
.
.

The fucker will take credit again for things he didn't do.

Not sure if this is necessarily a prank, but I was working on a team that was split in 2. We had a group of senior devs in one country, and junior devs in another (god only knows why, and yes I complained about this a lot).

The "lead" of the juniors was very stubborn and refused to adhere to the official standards, as his way was better.

I was working on an app with him, I was fed up with how badly the app was working, how hard it was to find files etc. So I waited for him to be off on holidays and pulled some extra hours to completely re-do the folder structure, rip out his persistence layer and a few other things.

When he came back he lost his shit and complained to the architect. The architect (also fed up with his shit) told him that we don't have the time to invest in reverting back everything, and loosing all the new features I added on top, especially since the app is now adhering to standards.

Never felt such satisfaction in my life.

The Return of Mr. Gitmaster:
So there is this colleague I already ranted about several times. After my previous team lead had confronted him about not doing much work, there was some irritation because he showed not up at work, but it turned out the external training he did was just a week earlier. Then he was ill a week, another week vacation so we didn't see him much. Not that his pre- or absence makes much difference to our repo: When his and my team lead looked at his commits of the past three months they found like the one copy-pasted HTML-form that wouldn't even show.
Fast forward to now, where we have a new team lead and we were going to lunch with Mr. gitmaster. So we got some more hero stories from the great work he was doing in the previous company. How he was graphically monitoring the heap fragmentation that stupid glibc was causing to their search engine, and how much better it became with tcmalloc.
I still don't understand how he bridges that cognitive dissonance from all the superior tech knowledge he displays to not actually writing any code at all. Not that I would not have experienced some states of feeling low, in paralysis unable to write a single line of code... but he seems so full of confidence, always commenting how trivial and easy all these tasks would be, as if it's all so lightyears below his abilities. Maybe he should just become a manager - but not mine.

It's my end of probation and I just got demoted, from originally "Senior dev" to "dev".

My manager found it a bit difficult to tell me but funny enough, I am completely fine with it apart from the little dent on my pay check. Let me talk about the bad first: money. I believe I have been on the lower end of the market pay range anyways so this step-back gives me about 5% cut, which is acceptable and fair enough.

And the good? Quite a bit. When I got this job offer 6 months ago, it was when everything literally went to shit. I was upset with a somehow not so smart but stubborn tech lead and I desperately wanted to quit. Then I got the offer, which even after 2 interviews I still didn't recall it was a job ads for "technical lead". The manager thought I was not there yet but wanted to keep me as a senior dev. Then, this pandemic almost took away this job. My manager brought my case to the CEO and convinced him to keep me, by saying a lot of good things about me (which I think might not be true for the tech side...)

Throughout the whole 6 months I have been working remotely from home. WFH is not new to me, just this time it's very challenging as I was starting a new job. I have been struggling to keep my pace. All people in the team are nice. However if I don't reach out, no one would notice I need help. And with zero knowledge for this job, I got stuck with "I don't know what I don't know". This ranges from company culture, practice, new tech.. everything. So, that's how this 6 months feels long, but also short.

In our review meeting I think my manager finally realise this. Otherwise he would have gone for the "terminate employment" option. Taking away the "senior" title also takes away the expectation of "I should know XYZ", which I don't. I told him I am kinda happy with it because this sets me up for a more comfortable position to catch my breathe. He told me he noticed my improvement along the way. I told him yes I have been putting in efforts but just given the situation it's not as quick as anyone would expect. We're on the same page now.

So compared to my previous job, I got paid less. But in return, I get many more opportunities to expose myself to new tech. I get a good team who are respectful and open-minded. This is exactly what I was looking for and the drive for me to quit my previous job.

Not to mention I got a reality check. This is also an indicator for me starting to become an imposter, which is the thing I despise most in the industry. I don't want people to value me for how many years I have got in my career. I want to prove myself by what I am capable of. If I'm not there, I should and will get there.

And the last thing which I'm not very keen but it's 100% worth mentioning, is that my manager said I should aim for taking the "senior" role back. He said the salary raise is waiting when I get there. But... Let me just take my time.

Blabbering co-worker rant.

So this bonker who speaks non-stop for 15 minutes without even a breather break is more annoying than I thought.

1. She used to work for a project A and then they moved her to my project. She kept cribbing she wants to continue working on A because that's where her expertise are. So management hired a new team member so she can continue on A and new member can work with me.

Now next week, the new member is joining us. As we prepare the onboarding plan, bonker comes crying that she wants to work on my project and NOT on Project A. She is forcing us to give Project A to new team member.

Manager upfront rejected her proposal and told her that she'd be working on A.

2. She literally gives orders. Her tone is rude and blunt. The other day ordered me to review her presentation and kept following up even when I said I was busy. Same tone and attitude with manager.

Then she complained about my behaviour saying I was a bossy person even when I used the most polite tone (because I have actively worked on and built my social skills).

3. Knows shit about the product, has no skill set, asks the same question 10 times, and isn't able to deliver bare minimum.

And then evidently everyone follows up with me because I am on top of everything (because I have to as bonker can't function).

4. She lied to me that company gives good hikes and easy promotions.

She was kicked out of her previous project because of her incompetency.

Fortunately or unfortunately, my manager saved her ass. But she literally is the most stupid person I have worked with me in my entire career.

5. She has no communication skills, something that is highest valued skill in my profession. And when I do my normal, it pisses her off. She keeps complaining that I am overstepping.

If I don't then product will just fall apart and everyone might get fired because of no work.

And that is causing her insecurities and she starts fear mongering about both of us being fired.

I told our manager upfront that I want to lead the product and she was more than happy about the proposal. What sucks is that my manager is leaving this month end and I'll have to build trust with my new line manager.

Ugh!! She is annoying..

At the first company I worked for out of college, the CEO was a bit like a child. Whenever he came up with a new feature he wanted to add to the product, it had to be done asap otherwise we were going to "miss the boat." Every single time.

So rewind to a few years ago. It's a normal day at work and then suddenly my team lead and the CEO call my team into the conference room. The CEO starts telling us about this industry conference (we were in online dating) that was happening and this flashy new company dating company was going to be showing off this awesome search feature.

Naturally, our CEO concocted a Hail Mary plan of how our company was going to upstage this company and get all of the press to write about us instead. Basically, the "plan" was for us to build a brand new search feature of our own, in the week before the conference, and then he stated that the press would "have to write about us because ours will be better."

Everyone on my team knew it was ridiculous but we were pretty young and naive so we busted our asses to get this search feature out the door in the short week. The Friday before we stayed until like 2 AM. It was a little bit fun because the people on my team were cool, but the whole situation was absurd and no one, except the CEO, thought this had any chance of working.

Annnnddd in the end we didn't get an ounce of press, the search feature was pulled from our site, and the "awesome" company that we were so worried about getting all the press is out of business. But hey, we did get it done!

tldr:
first year in college we programmed 24 hrs straight to fix somebody's mess before the deadline. Decided not to screw him over, instead he claimed to have done everything and we failed the assignment.

Long version:
var group= new[]{"Mike", "Gavin", "Gus", "I", "Ben" };
var client = "Jack"';

First year of college we had an assignment to make a web program for somebody.
Ben wanted to join our group and he already knew a client so we let him join.

After joining Ben wanted to be project lead, but we already decided Mike based on his experience.
Ben claimed to be much better in every way than Mike at and kept coming with stuff the following weeks why we should make him project lead. He kept pointing out when Mike did something wrong and he even came with an audio file where he clearly made jack say that he wanted Ben to be project lead .
After that we were all a bit pissed and told him that he should get it in his head that he was not going to be project lead and just start working on his part of the assignment.

We also found out that Ben was a documentation addict, what we could write in a small paragraph, he wrote a whole page about it. No joke, I rewrote a page of his in 5-6 rows with the same information in it.
No problem you thing, wrong! Because of this he kept bothering us arguing and claiming that our documentation was wrong because it was to short.

In the week of the deadline we asked Ben if he was also done, and told us that he was done for a while now.

The day before the deadline we came to school thinking we only had to do some merging and finishing up documentation.
Then we found out that Ben has almost nothing, and what he had the IDE was screaming that it was incorrect, spaces in Id's and css class names for instance. A really good programmer, my ass!
We were so pissed off at this point, but we had 24 hrs and needed to come up with a plan to fix it.

We decided that Mike and I were going to fix Ben his shit in the coming 24 hrs and Ben was going to make our last bit of documentation because we would not have the time for that, Especially if we had to argue with him like we had to do for each bit of documentation. Gus did not have time and Gavin could not program on his own yet, he wanted to help, but helping him help us would cost more time than we had.

We all went home after that and Mike and I started to program 24 hours straight while in a Skype call, making what Ben had 2 months for. Shortly before the deadline Mike looked at our finishing up documentation received from Ben and told me it was "Okay" and zipped everything up and uploaded it to school with a few minutes to spare.

After that we thought everything was good, we made Ben's part work and delivered it in time. We also decided not to throw Ben under the bus, because this would hurt all our grades because we did not work good as a group since we should have noticed it earlier.

A few weeks go by till the assessment.
The assessment start with asking if we want individual grades or as a group when you all think you did equal amount. We choose as a group, because if we chose individual not only Ben but also Gavin would get a lower grade and we did not think that was fair because he tried so hard.

We demo the product and the teachers are positive. When the teachers start about the documentation, the first thing they tell is that they found something interesting in the documentation, and they read it to us:

"I, Ben, have made all the documentation because my group did not want to."

That was so far from the truth, we all did make our documentation about the parts we made. Yes he did do overall a little bit more because every single bit of documentation we had to argue with him, so every time he volunteers to make it, we would all agree. And he made Mike's and i's last bit of documentation.

Telling the teachers on that point would not have mattered, it would only have hurt is in another way, so we did not and all failed the assignment. And we all felt like to strangle him.
This is now a few years back, but i still want too.

that moment when you were still new to git commands and just typed in random commands while thinking of a stupid dog meme saying I have no idea what im doing then accidentally pushing something in prod and had no idea what to do cause the lead dev was not around... aahhh those were the days

Spending all weekend on research and testing for a new feature, finding the perfect framework for it, going trough the API just to come Monday to work and get told by Project Lead: we can't use it, it is not in our stack.

How can it be in our stack!? We've never done anything like that before!

F*CK...that feeling when you were working as a junior UI/UX designer for about 3 weeks in new company, you were on a project which is almost finished and delivered...

1 and half week Later (after technical issues - check my older rants)......

you have noticed one quite importat mistake in the designs, which were done by senior designers, which can lead in future to a huge Ux problems - so huge, that users will probably leave/close the app and will not purchase the product via that app... ( We can say than whole design solution was a waste of money for the client)... On that designes was working a team of 4 people, about 3 Months (and the app (prototype) had to be ready already 2 Months back)...

the deadline was pushed 2x already...

And your boss (senior designer) tell you that this is not such an issue.. But thx for your opinion.....

1 week Later by user testing 4 out of 4 people were asking about that stuff I told to my boss that is missing...

And I was ignored...

In less than 1 week Later after the testing I get fired from the company without no reason...

Or better - the reason was:

I have too little experiences for this job...
Dont know if I should laugh or cry🤦‍♀️🤣/😭

Lead messed up the Git workflow (New repo), ask me to fix it. And when I said that we better do it from first properly, asked me if I even know git 🙄 Feel insulted.

when I graduated my dad would 'help' me in my job hunt by cutting out postings from the New York Times for "Lead Software Engineer" positions at Microsoft, Google etc despite the fact that I really was just trying to get a junior level position...

Got demoted, got a pay raise and don't know how to feel about it. A story of how not to drink with your coworkers?

The story begins roughly 8-9 months ago. Me and this coworker (let's name him Tim) go out drinking after a Friday party at the office. We do some rounds and we're both smashed. Tim starts telling me how he's happy with life and that he's earning a nice salary right now. He told me his salary. It was the same as mine. Which was weird - He codes in a more hardcore languages than me and has almost double the time in the company as me. I think after some more drinking I've confessed that I make the same as him. This part is sort of a blur (drinking). I've gotten a pay raise(+30-40%) roughly a few months ago from that point backwards because another company gave be a much higher offer. The company I work for matched to keep me. Anyway, 3 months or so after the drinking,Tim is promoted to team lead, and me and a few other people are added to his team. Conversation slips and he told me his new salary - quite a bit more than me.I think it's safe to assume what happened.

The problem with that is that I was a team lead of 1 person (me) at that time, and I was managing my own time and my own tasks, was working with people individually. I was part of the weekly meetings with the CEO and other team leads. Being stripped of this title wasn't a problem at the beginning, as people still contacted me because of their problems, suggestions, whatever. A few more months pass (to now) and less and less people are contacting me - instead they are talking with Tim, and are asking of his opinion on tasks I should do, where he has no experience and roughly 0 lines in the programming language I code in. This is starting to piss me off.

There are a couple other things to take into consideration as well - The company is hiring a lot of people right now. The whole structure for team leads changed a bit, more team leads then ever right now and new roles added pretty fast.

I've gotten a pay raise a few weeks ago though(10%~).

I'm not sure on how to react to this. Should I comply and just keep on working on these tasks? Or should I still keep contacting people directly on their requests and talk to them directly, take credit for the projects I complete publicly and the stuff I do as I was previously doing? Part of me wants to reroute all of the stupids questions people have to Tim, as he is now responsible for these tasks and get this weight off my shoulders.

I'm starting to shift to learning a new programming language and thinking of jumping ship. Thoughts?

My Team Lead: Hey do you know goofy?

Me: What is it?

TL: It's a new programming language

Me: *being suspicious* show me what are you dealing with

TL: *Shows me a Groovy code snippet*

Me: Yeah!! Your goofy is pretty good!! Enjoy! 😡

When your new team-members don't commit their code end of day Friday and you end up working the whole holiday weekend to fix their shitty work while they're away for the week....
Joys of being a team-lead..

One of my ex-trainees, mid-level dev at the time of the story, from the previous job asked me and insisted to work with me and if it's possible to open a position for him at my new employer (i was a team lead). We were also somehow friends, spending a lot of time together - including our girlfriends - outside of work.

He went to the interview, passed it and he received an approx. 1500 euros salary, jumping from around 1k euros. He was very happy with it and accepted the offer.

One week before starting his new job, my manager came to me and asked: "hey what happened with X?". I was like: "what happened?". "Don't you know? He sent an SMS this morning to announce us that he doesn't want the job anymore."

I had absolutely no idea about that. The second thing that I did was to give him a call and ask him about his decision. His argue was that "my current employer made my another offer: 1550 euros". I said something like "ok, have fun".

I got back to the manager to tell him about that. He offered to make another offer of almost 2000 euros to the guy, but I refused.

My designer just had an user interview where the user is a developer and my designer showed him the mock-ups of a no code tool that we are building, asking the dev for his input.

She literally had a session with a guy announcing him that we are building a tool that will put him out of work and moreover asked him for inputs so that we miss no use case.

And in another story, one of my dev lead decided to decommission an entire feature and replace it will a hacky solution because the devs in her team were not comfortable using the current design in their development stage. Hence, without user research, any strong use case, or considering business implications, she went ahead and drafted the entire approach on how to fuck everyone.

I am out of my honeymoon phase at my new org and I am scared. Shit scared.

Brain storming with senior lead developer. We try to add new tables in our database. But the Google spreadsheet goes wrong

Working in a startup company acquired by some €^%€*^^ from singapore, second month no sallary(the first Local CEO) paid us.. now nothing...
I went to new interviews today.. HR and later 2 hours C# Coding test... definitely I was fucking good in the test, they called me hours later with positive feedback and new interview tomorrow , and they want me to team lead now 👍🏻👍🏻👍🏻👍🏻 positive vibrations guys🙌🏻🙌🏻🙌🏻🙌🏻

I'm halfway in on a six-month disaster contract where I'm converting a massive site written over 7~8 years to a new system. Manager has had us restart about 4 times and there are other departments who want to take over. The deadline is so tight that I've stuck with the original plan and kept my code flexible to be changed if the manager wants to go with the other teams' ideas. ("Okay, manager: here's a clone, tell the other team to prove that works") The lead dev, to my horror, didn't write any code and was let go in November.

Manager hired a new dev part-time whose commitment is on something entirely separate that is required in order for the deadline to be pushed to Summer. (new thing for old thing)

New dev has an attitude, basically wants to start over, and is already acting like I'm his subordinate, very patronizing, very dodgy when asked to explain a strong opinion (THIS IS A SECURITY PROBLEM!!!1). I really have no idea what my manager promised to him. Also found out that manager hired an agency to create a roadmap of the project (WHY?!!! WHY NOW?!). I've been burned once already with the previous lead, and I'm not wild about working with yet another person who wants to burn the whole thing to the ground and start completely over, especially not someone who wants to engage in a dick-measuring contest.

Do you guys have any advice? I mean, other than quitting? I'm going to see this through, but I'm burned out.

!rant, but some kind of story

I work as a lead dev on a gmod server of a pretty big german community. With the fun stuff, there come the duty‘s to help Jr. Devs or even help people get into Developing. The part, where you help junior devs is always fun, but what I find interesting is the part where you help people learn coding. It’s not easy work, but you learn more every “lesson”. I catch myself exploring and learning something new, even if I know the topic. For me it’s a new journey every time.
Not sure if there are many people who can relate but I just wanted to tell my side on it.

I quit this startup side job coz I was over worked and under paid for 3 years and I decided it wasn't worth the mental fatigue and anxiety. Plus I didn't feel like it added any value to my life other than stress. Gave them at least 2 months notice (since February effective April 30th) coz as the only server side engineer+team lead, I did ALOT. Now they brought this hot shot new CTO who wants me to basically rewrite the entire app before I go while maintaining the existing system and making sure everything functions smoothly (there is a ton I chose to optimise to make things easier for the new dev who they have not hired and I have 4 weeks to go) . The app was built in mongo db now he wants it in mysql. Can't believe ask me this after breaking my neck and falling in and out if depression for this job?!! I want to laugh and scream at the same time.

Started a new job and our tech lead doesn't know how to use GIT in a team environment, has only ever used it while working by himself on one person projects. Kinda worried...

Nope, definitely not going to work for that customer anymore. Fuck this shit. At least for this week.

My background: mid-30 years old, some kind of business & IT consultant / lead dev working for a mid sized CRM consulting company, with approx 15 years of experience in development and software architecture, most of the time "thinking" in C#, still learning new languages, being a cloud evangelist and team lead. We usually have customers with customers (B2B/B2C).
Personality type "campaigner" (ENFP-A).

Today the project lead of my client (a big corporation in the energy industry) told me that he still didn't order all the necessary resources for the cloud project. Just to be clear: He's on the client side. We (the architects, one internal and me) told him one month ago what we need for the beginning. Just a few things - an Azure subscription, a license for the CRM platform, and our dev tools.

And now let's guess when the project is planned to begin? Yeah, right: 1st of April. NO APRIL'S FOOL. And guess what? Next Tuesday we'll do the onboarding for the new (external) devs, and NOTHING will be ready. Yeah, just let us build stuff in our minds, and on the whiteboards, because it's an AGILE project, right? We don't need any systems and tools...

And now he sent me the questionnaires which need to be answered before any cloud service can be ordered by the corporate IT. And yes, he didn't answer a single thing, and just meant "Those are architecture questions" (they are not) and (of course) "please provide the answers until Monday morning, so we can FINALLY order the services."

Yeah, you fucktard. Of course it's MY FAULT now. Maybe I should write an email to your boss asking how we can speed things up a little bit...

My first project it’s an emotional roller coaster. I was a little trainee/ junior dev at my job with a little more than a month learning RoR and one day my tech lead receives an email from the big boss saying: “We got a big client who wants a total redesign of his web and we said yes we can do it in a month, so please check if anything it’s reusable”, after reading my tech lead said to me “Do you want to help me with this ?” And well, we spend like 2-3 hours checking all the controllers, views, assets, etc. We conclude that the project was mostly front end changes and the back end will stay the same, so yeah it can be done in a month. The next day in a meeting with all the team I was nominee to be the person in charge of that project, because it was an easy project and all my teammates hate to do front end stuff, so I take the challenge. After that I met the Project Manager, another guy who recently start as PM about a month, so yeah we were two new guys who need to handle the project of a big client, nothing can go wrong. We did the planing, I give an estimation ( first one in my life ) for the tasks and added like 4 hours in case anything goes wrong. Then the first sprint came by, and I couldn’t finish it because the time given to some features was to low and the “design” was a mockup made by the PM, ok, no problems, we add more time to the tasks and we ask for a real design. At the half of the sprint the client start adding more and more stuff, the PM doesn’t talk back, just say yes yes yes. Then in a blink of an eye the easy project became a three months projects with no design at all, two devs ( a new guy who recently begin as dev enter the project ), just mockups and good hopes. But somehow we did it, we finish it! Nope. The early Monday of the next week I received an email of the PM saying we would have a second version and the estimation of the tech lead was a minimum of six months ( that became 8 months). This time was hell, because the client doesn’t decide what the hell he wants so a task would take a couple of days more or so, the PM became the personal bitch of the client, but it wasn’t his fault, because we later knew that the company became partner with this client and because of that the PM didn’t have too much choice :/, the designs were cool, but they weren’t on time ever, our only design guy had to do designs to our project and another 5 projects of the company, so yeah, we weren’t the only ones suffering. At the end we survive, the project was done and the client somehow was happy. Of course the project didn’t end and it was terminated half a year later, but I’ll always remember it because thanks to this project I was given the opportunity to work as a Front end dev and I’m happy still working as one.

Why can't managers understand that functionality changes and UX changes should be two separate epics? There's a huge fucking difference between composing an UI from existing components vs. having to figure out new components while at the same time paying attention to 12234234 new scenarios while at the same time duplicating existing components because existing portion of the app has to keep old UX.

And then they say bullshit like "we need solutions, not problems". Fuck you. Solution is to keep existing UX and focus on functionality, and do complex UX changes when functionality is well-defined and STABLE. But no, you fuckers won't listen even when the fucking lead dev tells you to.

Well today I feel like shit so I called in sick. Found out the lead developer called in sick as well.

The thing is, there was something really important to be done today that he fucking new that if he was not to be there I was going to get shit from everyone. He is going through some shit right now and I get it, so I would normally cut him some slack.

But fuck man, at some point you got to man the fuck up and deal with your job, if anything do it for your fucking coworkers/friends. He fucking new that I was going to get a fuckload of bullshit over something that he takes care of.

Nevermind that there are only 2 fucking developers for the entire fucking campus(2 campuses actually) and we were told last friday that we were needed. Normally, one would put up with the bullshit and make a presence, but that one of us is always me. Today I said fuck it, its too cold, don't feel good and I don't want to take my daughter to the daycare.

Today I sit at home, go over my OS books, play Skyward Sword with my daughter, watch movies with her and I don't think about work for one second.

On another note, the reason why I need to go through my OS books is that a good portion of my masters degree(which I am to start on August) covers OS development, it seems that the entire curriculum will be C/C++ galore which makes me FUCKING STOKED! finally a break form web development that I can probably use to get me out of web development professionally as well.

First rant from my new job.
I got a position as backend-dev in a startup and for now i'm learning angular. Yes, you read that correctly, because the frontend-team is short-staffed i decided to switch teams. We are 3 people and neither one has sufficient angular-experience (the framework was a management decision).
First of all i got confused because we use slack and trello but the frontend-lead decided to do some stuff via google-spreadsheet too. Then we didn't have any code in our repository until yesterday. I tried to check out the repository after that, did an npm-install but when running ng serve i got an error "css-file not found". It turns out you had to download some files from the official website and put them in the unversioned node_modules directory. It was the teamlead's decision to do so and me and my coworker got really annoyed when we tried to set up everything on our end. But that's not all, yesterday the other dev's merged their first versions of the project. But not via git, that is way to mainstream. The coworker had to upload his code into the cloud and the teamlead copied the files into the project folder.
Aside from that the code already isn't the best, some things should be done differently imo and we have credentials in the code (not in some separate files, but in an if-else-clause that checks node.env.production).

We'll have a discussion about this tomorrow, let's hope things can be straightened out.

WOOOP-DE-FUCKING-DO I HATE MY ISP (well actually the company which is reliable for the cable networks which lead to my/our new home).

WhAtEvErYoUmEaN and I moved yesterday to a new flat. Not spectacular at all except that mentioned company cancelled the appointment ON THE SAME FUCKING DAY! "We're so sorry. No internet until Thursday. At least"
Dickheads.

Well, so we are here in the middle of nowhere without internet. Time for old school books i guess😅

I told my lead, "I am creating a new Algorithm" instead of "I am trying to fix this", and instantly I am a programming wizard :D :D :D

I don't know what you did yesterday, but i did make my company throw away 2 months of progress.
It all started in the beginning, since that i've made numerous complaints about the workflow or code and how to improve it. I've been told off every time, and every time i either told the boss who agreed in the end or wrote code to prove myself. Everything was a hassle and my tasks weren't better.
Team lead: you'll do X now, please do that by making Y.
Me: but Y is insecure, we should do Z.
Team lead: please do Y
Later it turns out Y is impossible and we do Z in the end...
Team lead: please do W now
Me, a few days later: i've tried and their server doesn't give http cors headers, doing W in the browser is impossible
Team lead, a few days later: have you made progress on W?
Me: * tells again it's impossible and uploads code to prove it *
Team lead: * no response *

After that i had enough. Technically i still was assigned to do W, but i used my time to look over the application and list all the things wrong with it. We had everything, giant commits, commented out code, unnecessary packages, a new commit introduced packages that crashed npm install on non-macs, angularjs-packages even though we use angular, weird logic, a security bug, all css in one file even though you can use component-specific css files...

I sent that to my boss, telling him to let the backend-guys have a look at it too and we had a meeting about this. I couldn't attend but they agreed with me completely. They decided to throw away what we have already and to let one of the backend-guys supervise our team. I guess there will be another talk with the team lead, but time will tell.
It feels so good having hope to finally escape this hellish development cycle of badly defined task, bad communication and headache-inducing merges.

During our last Sprint Planning we have chosen to use internal codename Solid Snake for this period (yes, we change it every sprint).

Our Tech Lead likes to draw current name (adjective and animal name) on a whiteboard. As soon as new name has been voted down he refused to draw a new one because

Drum rolls

He doesn't like Metal Gear series.

I'm not sure I want to work in this company anymore...

So our new hardware guy who is being managed by our lead embedded developer had the task of designing me an expansion board for my Linux board. The Linux board uses the 40 pin expansion like the raspberry, bananna and orange pi family and as you all know there are many different types of expansion boards for this.
I said at the start come to me and tell me what you want to connect to before deciding which pin you connect to so it is less work for me with Linux board configs and drivers.............
No no no we will sort it all... erm.....
So today they come ask me if they can use an SPI port for GPIO and I am like erm... why there is plenty of GPIO...
It turns out they have been designing the board based on the pin outs of an expansion board and not the actual connector of the Linux board.. I mean seriously WTF!

We are 2 people working as remote android devs for this startup in another country. 6 weeks ago a new person joined onsite to work directly in startup HQ. I'l refer to him as an newguy.

Last week we started new sprint (of 2 weeks) to work on a new feature.

Newguy was responsible for gathering all the specs and planning, so this is how our sprint is going so far:

Day 1:

We have 10+ tickets in jira (tickets have only titles) no one knows what to do and we don't even have specification. I started pushing everybody onsite to get their shit together. We NEED UX/UI specs, we NEED backend to be ready, or at least start working paralelly so that once wer'e done with frontend backend would be ready. I mean cmon guys this feature is already 70% done on iOS, why cant you send us the specification?

Day 2:

We had a meeting on Zoom and talked about missing specification and project manager promised to send us the specs. Meanwhile the idea of feature became clearer so I agreed with the newguy to start researching about best way to implement our solution.

Day 3:

We received the specifications. I provided my research for the feature to the newguy. Turns out the he knew about specification 4-5 days before.

Instead of sharing information with us, he decided to create his own library to do what we want to do and blatantly rejected my research input.

Now he showed his implementaton (which is shit by the way) and presents it as the only way to proceed forward. He offers for us to work paralelly with him on this (basically he wants to write library alone, and we are supposed to somehow implement and test it, but how the fuck we can implement if backend is not ready and library is just a bunch of empty interfaces at this point?)

I talked with one of the teamleads in the startup and told him that this is not the way things were being done here before and new guy is becoming a dictator.

Teamlead talked with new guy and found no issue. Basically newguy defended his sole decision by saying that he did research on his own, there are no libraries that do what we want and he knows better.

Teamlead tells me to STFU because new guy seems competent and he will be leading this feature. Basically from what I gathered teamlead doesn't give a single fuck and wants to delegate all project management to this new guy.

Day 5:

End of the week. New guy claims that his lib is done so we can start implementing properly. I tried implementing his lib but its fucked up and backend is still not ready.

Day 6:

Backend is still not ready, no one is doing anything just waiting for it to be ready.

Day 7 (Today):

Today(Backend is still not ready, no one is doing anything just waiting for it to be ready.

So what can I say? His plan was to probably prove his self worth and try to lead this feature by giving us information at last minute. At the point were we should start implementing instead of researching.

What happened? Motherfucker doesn't know shit about backend, has been notified about backend issues multiple times but his head was so deep up his ass with that new library of his that he delayed the rest of the team.

Result? 7 working days wasted. Out of 3 developers only 1 was actually working (and his fucked up code will have to be rewritten anyways). Only 50% of feature done. Motherfucker tells me that this is how we will work in the future, "paralelly". The fuck is this mate? If you would have worked on this feature alone you would have done it already now, but instead you wait until we remote devs will login and fetch you the test input and talk with backend guys for you? The fuck is wrong with you.

You fucking piece of shit, learn to plan and organize better if you want to lead the team. Now all that you are doing is wasting time, money and getting on everyboys nerves. Im tired of fucking spoon feeding you every day you needy scheming office politics playing piece of shit. Go back to your shithole country and let us work.

When I was responsible for sprint planning I figured out what to do before start of the sprint and remote devs were able to do week's work in 1-2 days and have rest of the week off. This is how it's supposed to be when you work with a remote team. Delegate them separate features, give them proper specs ahead and everyone's happy. Don't start working on frontend if you dont even fucking know when backend will be ready. It's fucking common sense.

Now I need to spoon feed this motherfucker who can't even get information while sitting on his ass onsite in HQ. Fucking hell.

I changed my job, after 7 years at the same company going from dev to senior to lead, I'm now moving into a new role as a lead..... Thats scary.

All the experience in the world doesn't ease that imposter syndrome

New on HS Robotics team (we went to worlds last year —> we’re good). I come from France.
The lead programmer say that we are gonna stop coding the robot in Java and start C++ this year, so naturally I’m excited!

Lead programmer just told us we’re actually staying with Java... fuck.

Recently I receive a ton of mails from cool/hip/rockstar startups. They all run like this:

"We are a innovative Startup based on a [insert some random stuff or buzzword] blockchain! If you're a student with skills and experience in blockchain, machine learning and AI willing to change the world with our sick technology and make it a better place..."

The best thing about this: since they are a innovative Startup they expect you to work for free.

But who am I to judge something so brand-new and innovative. I contacted them to find out what these dank innovations are about.

They can't even explain what a blockchain is or the basics of ML and AI, they basically just want someone do it for free...

It's still ok since no one is gonna fall for this bait... this morning a friend of mine told me he got a new job... and he even can work from home...

I'm not even mad, I just feel sadness and sorrow specially for him, because he is a good dev and accepts big times underpay and now free work, because he thinks a day off in his CV will lead him to be unemployed 😭

Fucking hate it how people successfuly manipulate kids and youth to them to work 24/7 for minimum wage or even for free and some other douchebags trying to take advantage of this 😡

This, fucking, designer. He has no fucking clue what he's doing. Every minor fucking thing has to be a new fucking screen.

Toast notification? Snackbar? At least dialog? NOPE, WE NEED A NEW SCREEN.

Lead fucking designer my ass. Wasting everyone's time flapping your dick around.

When you have to add new features to a 5 years old app, because it would be a heavy lift to rewrite.

So no dev lead has the balls to bring it through the board, so you are stuck with ancient and awful code.

At one of my previous gigs, the IT director was just some guy that dated the bosses daughter. When she inherited the company he went from entry level data analyst to his new director position. IF he decided to show up to work at all it would be at just in time for lunch, and then he'd head out shortly after.
This guy would ask for an estimate on development and then start the timer when marketing started working on the project. This would often lead to us estimating something like 4 months on a project, and then waiting on marketing for 3 of those months, leaving us with 30 days left.

So this post by @Cyanide had me wondering, what does it take to be a senior developer, and what makes one more senior than the other?

You see, I started at my current company about three or four years ago. It was my first job, and I got it before even having started any real programming education. I'd say that at this point I was beyond doubt a junior. The thing is that the team I joined consisted of me and my colleague, who was only working 50%. Together we built a brand new system which today is the basis on which the company stands on.

Today I'm responsible for a bunch of consultants, handle contact during partnerships with other companies, and lead a lot of development work. I'm basically doing the exact same things as my colleague, and also security and server management. So except for the fact that he's significantly older than me the only things that I can think of that differentiates the seniority in the team are experience and code quality.

In terms of experience a longer life obviously means more opportunities to gather experiences. The thing is that my colleague seems to be very experienced in 10 year old technologies, but the current stuff is not his strong side. That leaves code quality, and if you've ever read my previous rants I think you know what I'm thinking...

So what in the world makes a person senior? If we hired a new colleague now I'm not sure it'd be instantly clear who should guide and teach them.

I know I'm out of the loop since I barely use these sites, but...

What is it with this seemingly ridiculous new trend on LinkedIn of replacing your meaningless job title with, somehow, an even more meaningless fake description of what you're doing? I'm seeing it all over.

Back in the day it'd just be "Python developer". Then the trend seemed to be a "Senior / lead / principle software engineer / Python specialist" (who cares if you're actually a senior eh, this is LinkedIn.) And if that wasn't ridiculous enough, now it's "Helping to transform the globe towards a greener future by implementing beautiful, robust code in Python 3.10" or similar. Who the hell wants to see this crap?!

User A: We need to do some check on our data. So you need to add in a new function for this, we can't use your system otherwise.
Me: Ok then.
Spends 2 days or so to get it working
Me: So this is the function we'll add. Can you confirm that its ok?
User A: Ohh...but now I'm not too sure about this. Let me confirm with my team lead on this.
User A: I just checked. Good news,we don't really need that function now. I think we can use it with the current one anyway haha. And I just confirmed this so no worries.
So I just wasted my time then. Great.

Hello all, I was wondering how some of you guys manage stress on the job? I recently got a new "real" job as a lead php dev working 9-5 in down town Houston. I must say, this "normal" work schedule is kicking my ass. I'm constantly exhausted, stressed out and am now having second thoughts about the position. What should I do?

Hired by large prestigious company to do web development. Understanding at the outset, I was not a web developer, just wanted my foot in the door with the company. 2 days after orientation, I am placed on a $20 million contract expansion with 3 other developers. All new to this contract. So: new language, new technologies, new team, no leadership, no mentorship. 2 months later after a month of asking for help, I'm asked why I'm not delivering solid code by the project exec and moved to the testing team. Testing team lead introduces me to people on the contract and answers questions or tells me vaguely where to loom. Spend last 4 months building a professional fuck you by making myself a yes man to everyone and their mother. Left the contract and have been getting regular hours with them since (including developing for them). New contract loves me and despite the project execs attempt to torpedo me, I have an excellent reputation and am positioned for career advancement already.

I couldn't give him the finger, but I made him regret lettimg me go. Original team lead has since been released for unrelated HR complaint.

Being a junior and part of a small team at a startup, working with a new software architecture, even the team lead is a beginner in it. It feels like I'm at an echo chamber, there's nobody expert enough to look up to if stuck, decisions seem to be based on opinions rather than an architectural design kinda point of view.

Ugh, I hope I'm not the only here ever feeling this way.

I started off in a MNC company as a junior developer. I entered with candy glasses.
I didn't expect to win the lottery. Of getting abuse by superior.

I stayed for a year, at the project. Constantly being belittled by this team lead. It was awful i enter as a fresh grad. All the new tech were so new and scary at that point.

During my time there, i constantly think that developer is not my stuff.

Ultimately i reach the state of burnout. I reached out to the manager and broke down in his office.

I actually told the manager. "I hate coding"

I remember staying up to 4am just complete a piece of program. To be ready to be push to production the next day. My team lead just come screaming at me saying there is bug.

Upon receiving that message via skype. I broke, tears flow down my eyes.

After which i reach a state of burn out. I start to reach out to external parties for help to get me out of there.

Now i am recovered from the burn out. I am curious of the technology that were utilized in that project. I literally face palm. After understanding the technology it isn't so hard after all. I just didn't gear myself up with the tech.

I still do enjoy working on code.

People of devRant. I am in need of some advice.

So I joined this new firm around an year ago and ever since my team lead resigned, we have been managing it ourselves. Then a senior member suggested me that I could be a good fit as a team lead role. Now there are members in my team that are more experienced than I am but they either don't want to lead or are not good at it. I never had a formal leadership role before although I have driven projects. Higher management is open overlook my lack of experience but has also said that I may not find lot of technical growth as I am moving to a more administrative role. Any piece of advice on what I should do? I would love to have a leadership role but would it really affect my technical learning?

That feeling when you hace your first talk with new lead QA, all the way from Microsoft:

QA (sitting at her new desk & PC): "How do I get the log in screen?"
Me (trying to be helpful): "Have you checked the machine is on?"
<QA checks>
QA: "How do I turn it on?"

We rewrote the whole thing, except for iFraming some old pages in. We had to, the system was fucking awful and couldn't cope with any of the new mission critical requirements.

Client didn't understand the scope. Our project leader somehow snuck it in and we worked on it for months. We were sure we'd be kicked off the whole project... Somehow things didn't crash and burn. How it didn't blow up defies rational thought and the laws of physics. The new system worked, the client was happy, and boss made a lot of money.

Lead dev worked weekends for what feels like an eternity, it really was his baby and no one else on our company could have done it. It's where I finally learned how to do things the proper way; DDD, unit testing and TDD, architecture, building strong components in front-end, you name it. Before that I had a great nose for code smells and how not to do stuff, but now I got to see a proper system for the first time. It was glorious.

Then lead dev left and the system degraded quite a bit because new team didn't keep to the architectural patterns or general best practices. But we had a good run.

This wanker approached me via LinkedIn before new year to be team lead to a diverse team of devs spread over a few time zones.

The mission? Build a metacritic clone, but geographically constrained to New York.

Me : How much are you offering?

Him: <radio silence>

Regain work life balance.
The last few years especially with COVID I've started to do way to much for the company's I've worked for. Working while I was coughing my lungs out when I had COVID. Working during my holiday because it was finally a fun feature to develop. Working in lunch breaks because people would call me all the time (remote there are no boundaries)

I left that company on a good note, started actually healthy as the new company actually understands flex working. However as I gained responsibly more meetings started to appear also causing rushed lunches no more walks of sport activities. Than I was lead in a project and because of some personal circumstances (death in the family) that was running long. Again started to work overtime trying to catch up.

I need to stop doing this. Caring is fine but I just give to much when I feel responsible. Good thing is that my current company actually wants to help me with this.

!rant && !!happiness;

I told you some times ago that I was almost fired then put in a new position as tester: my goal is to test if the functionality asked by the client works the way it should.

Today, after 3 months of doing this only, I got to speak with the lead developer, who pretty much saved my ass back then, and told me that not only he was pleased by my work, but he looked at the code I did and liked the organization I set up to handle multiple projects in one folder (trust me, it was INSANE), but he was also genuinely happy about how I'm training the new dude.

And pretty much suddenly, he told me that my logic and knowledge about development was better than some of the colleagues who were there 2 years before I started, I just needed a bit of work to make people forget about what happened in January.

Life is currently fucking good, it's almost sad I have nothing to rant about 😊😊

This is so annoying, I had 9 diff. jobs the past 2 years and this is my 10th and if this doesn't change I might reconsider my options again.

I came to work at a company that pays me like a Junior and treats me as an intern. My 20yo "boss" who acts as a project owner/lead dev doesn't want to learn anything new and sees any improvement as a waste of money. The problem is he thinks hes a great programmer but he doesn't know shit. Im mainly working on the Laravel installation because "I claimed I know Laravel". And its absolute garbage. They haven't used a single Laravel features besides routes and everything else is vanilla PHP. They write for loops that loop through $_REQUEST to remove a single character. Write 100 deep nested ifs and they abuse Elasticsearch to the point ES crashes because the program is using 1000 deep multidimensional arrays. Its only a webshop...

Everytime I try to make a suggestion like making the master branch protected, doing code reviews etc etc I get shut down because they are autistic and don't want anything to change.

I have made a decision that I really want to document for myself on DevRant, under the comment section of this post.

I'm turning off all social media access after 7 PM for 2 weeks, just to experiment on how this pans out. This includes any online shopping apps and other apps like 9GAG, YouTube, Insta, Facebook, WhatsApp, Discord and DevRant.

Why am I doing this? Because I feel like I'm wasting too much of my time on these apps and enforcing rules on myself would make me bored AF and come up with creative ways to spend my time. Maybe I'll pick up the guitar again, maybe I'll learn new coding topics and create tutorial videos about them idk. Also boredom can also lead to proper sleeping times, I think.

My hands are already shaking thinking about tomorrow when my mind will take the impact for the first time. Wish me luck.

I'm a tech lead for a new agile project for a manager who knows nothing about agile. Having to work on a chart that shows exactly how many sprints each milestone will be and when it will complete for like, 17 sprints from now when requirements aren't even set. Wtf?

Being a team lead is watching your members grow more and more while you stay out of date because you don’t have any more time to read and learn what’s new

I'm the lead dev on this team. The project is split into multiple separate modules to comply with separation of concerns, and so new devs don't need the whole fucking codebase (risking them running away with everything) to contribute to the project as a whole.

So we don't need a fucking config file to enable and disable features.

So we don't need to upload a 500mb monolith every time we want to test a change.

So we can test old fucking versions of modules without merging it back into the entire codebase.

What did this fucking dev do? He was having one small issue with Maven. One. It wasn't updating his local snapshots to the correct Artifactory version.

He decided, instead of trying to fucking fix it: HEY, LETS IGNORE THE LEAD DEV'S DEMAND TO KEEP THEM SEPARATE. IM GOING TO MERGE THEM INTO ONE MODULE FOR SOME FUCKING REASON.

I refuse to continue working with this dev if he's going to sidestep my demands and undermine my authority. He wants to go it alone? Be my fucking guest. I'm not touching his shitty single-codebase monolithic monstrosity.

If this is going to be a regular fucking occurrence, he can eat a dick and choke on it.

This happened many years ago.

First, the background. I was working on a government project with a consulting firm. I would regularly sit on conference calls with several business analysts, project managers (yes, plural), and government employees where I was the only one with any technical knowledge of the platform we were working with. Of the other supposedly technical people, most of them were warm bodies hired by the consulting firm. They knew little to nothing. Most of them bullshitted their way into the jobs.

They hired a new project manager (or program manager, I don't remember) to lead the project at a high level. Things were not going well, because the environments were unstable. Since it was high security government project, we couldn't do any work for several weeks because you cannot copy work from outside environments. Literally a criminal act.

The new lead PM proceeds to take charge and send demanding emails. The one that sent me over the edge was an email that indicated we were all not working hard enough and we had to provide our detailed plans for a project in 30 minutes. Yep, she had it in all caps and a large font at the bottom - a 30 minute deadline. It would have been a rough 24-48 hours to put that together. 30 minutes was an impossibility.

That was the last straw for me. I flipped my shit and ripped my boss a new one. To be totally honest, I regret doing that. It only made stuff worse. Within a month or two, I quit along with our best business analyst.

About a year later, I found out from another government employee of the agency that a scandal erupted within the organization. At least one director level person on that team (government employee) was fired for cause. If you know how governments tend to work, generally it requires serious ethical or criminal violation for an employee to be fired. The consulting firm I was working got most of their work canceled, and they had to lay off most of that team. I'm convinced, based upon other stuff I read about my former employer, that kickbacks were involved. They had no problem paying off government employees for fat contracts and/or cooking the books (another scandal).

However, after that experience, I hope I never work on a government project EVER AGAIN.

Got a new team and teammember who has been here for years seemed not so happy having me now as lead. No problem, i even can understand him a bit. Still, if you have a f***** problem there are better times to address them then every f***** time at stand-ups. -.-

Started this day great with the mention that a coworkers contract isn’t suspended.

In August?

Thats in freaking 6 months. Workload is already fucking insane, and STILL you fucking decide to fucking fire another fucking person from YOUR fucking company.
This has been the 5th i think and my contract is due to July. If it is prolonged i’m thinking of screwing this company over my going away myself. Bunch of mother fucking idiots.

Ended the day great as well.
Heard that a new person is going for lead promotion. Haha.
He has been here for only two months. :,)

Left and right projects are exploding meanwhile i’m in the middle trying to cut the right wire!

New dev guy in office, Does zero research when stuck in somewhere while doing a task. Goes around asking the team if they had done that before. Talks on the phone for like 10-15 mins with god knows who when he has a technical problem.

Doesn't even bother to do a simple debug before complaining about an exception in a service to the dev who wrote it (if he knows the dev who wrote it)

Interestingly, he marks the tasks he does in a google sheet in red, yellow and green rows that's shared with our tech lead.

Not that he bugs me or anything, but just thought i should share this here.

Job BS that made me consider quitting?

Huh. so timely.

With my previous employer, it was the whole "we're doing Agile and sprints and all the things" with "finish the project in six weeks plus here are some more requirements" garbage. Plus my tech lead always let the business roll over her and add unplanned requirements during a sprint without adjusting the deadlines set by the project managers. In summary: a fuck-all combination of Waterfall deadlines, Kanban tickets and Scrum timeboxes.

At my current employer, it's our business partners who're a bunch of douchebags that don't plan for anything except making sure their bonuses stay intact. Recently they terminated support for a third-party product that literally drives 99% of their web application then says to us "Hey, we need to build our own replacement for the vendor product using an entirely new stack. You have 3 months or our clients will get pissed." Oh, and these business partners keep raising new issues without any documentary basis except "this doesn't feel right" when they test our in-progress work. So helpful <sarcasm />

On the bright side, I'm getting paid whether or not this project fails, so... meh.

If anyone here remembers the first 2 part rant story I posted then you will know that I got unceremoniously laid off by a company that tried to blame me for their bad decissions at one point

Well, a couple of days ago I found out that the senior dev and the owner took a trip to San antonio tx in order to try and look for growth opportunities and more developers. The thing is, being a Mexican company they thought they could go away with half assed solutions and mexican pay charts (to them it is completely reasonable to pay a dev with a degree and experience close to 13.99 an hour) just to find out that shit like that does not fly with American professionals. After I left, no one would monitor their .net implementations , the lead developer being a new php developer himself and not knowing much about .net had to take care of much of the things they had to work with, their API made no sense and it was damn near impossible to connect their services to a mobile platform unless you had ninja like skills and ingenuity.

I hold no grudges and really wish them the best, but it pleases me to know that they know now that their way of doing things is not standard in the U.S. now that makes me happy.

I have a co-worker who won’t stop “refactoring” our codebase. He will go on a long tangent — under the guise of working on a proper story — and then reveal proudly after a few days that he now introduced a new middle-layer into the code which will help us such and such.

I have never seen any benefit from this. I think sometimes cleaning up variable names is nice, but a lot of the things just add noise and complexity. He’s a junior dev, I’m a senior dev. My progressional opinion is that he is doing a bad job. Management doesn’t know the full extent and the lead programmer scolds him every now and then but in the end let’s the code changes pass code review. “It has already been implemented so what’s the harm”.

Then the rest of us are stuck with horrible merge conflicts. I recently noticed that some new business-important unit tests that I wrote were mysteriously gone. Oops — lost in some misguided refactoring I guess. I’m assuming they were failing after the refactor, so clearly they had to go... Fortunately the underlying logic still works I think.

His main tactic in all of this seems to be to just use argumentative stamina. He will lose discussion after discussion but doesn’t seem to care. He’ll just talk and talk. And the in the end the lead tech gives in. And/or doesn’t have the energy to catch the error introduced.

I swear, the company would be better off without him. Maybe even better if we keep paying him but he just cleans the toilets instead. Sometimes I almost believes he gets up in the morning to come to work and just fuck with people all day.

I got enough Today so I marked my linkedin profile with “looking for new opportunities”.

It’s actually cool you can pick up to 5 job positions, location, form of employment and let know only to recruiters not all of your contacts that you are open for a new “opportunities ”.

I picked technical consultant, software architect, technical lead, lead software engineer and principal software engineer.

Time will tell if I will be able to find something better then I am dealing with right now.
Customer I am consulting for is cool but the company I work for went over the years from cool to get the fuck out right now cause we only hire managers and people without any knowledge.
It’s probably cause they hired many people from one company that was acquired, probably those who know everything about nothing.

Struggling

Started a new job not super long ago with the intention of "learning new tech" and so I get my wish, I'm thrown into a project as the LEAD ENGINEER

And my junior dev proceeds to run circles around me and I know literally nothing about what is going on in this project aside from the architectural / feature planning discussions I've had with marketing/junior

I've been trying to learn vuejs for what seems like weeks and weeks and I'm just not "getting it" I come from a strong oop php background and this paradigm is using tons of tech I know basically nothing about. Every time I talk to junior I get super depressed cause he's speeding along and I'm still completely clueless.. what the FUCK do I do

We've recently employed a new lead dev that seems to have a problem in that his solution is always the correct solution.

On a typical day, whenever I push code up for review via pull request, every single ticket I work on, he has something that has to change which doubles the amount of time of each ticket.

I'd be fine with this if the other 2 developers also think he's a bit of a headache in terms of his opinion but a lot of the time, there is always.. ALWAYS something that has to change because his method is better than mine.

For example, just now I pushed up some code that literally just adds in the user's email to the view which is already in the store for that action/effect anyway. I added one line of HTML.

He comments saying that I need to change the way it gets the email by doing a different request in the effect, to get the current user id, and from that match it against the email address, and THEN display it in the view.

This ticket took me 5 minutes. He's making me make it 30-60 minutes (to understand his requirement and implement it).

Is this normal? Am I over reacting?

Opinions please!

Hey! This is a followup to my last story.

TL;DR: I thinking of quitting my old job, got an offer at a startup, about the same pay, but much better working conditions.

First of all, the meeting with my lead. It was a performance report on her side to me, and I got 100 to 110% in performance in all points. My lead said "this team without you wouldn't be this team anymore" - which makes me feel a little bit bad for her if I decide to quit. She is a great team lead, but I don't belive the old company is worth my time anymore.

Now to the new company. Shortly after that performance report meeting, I had a call with the ceo, and what do I have to say besides: What a cool dude. He listened to me, asked me questions about my previous jobs (not just as programmer) and so on. But because first looks are deceiving, I went to their office last thursday. And wow. Their are exactly what I imagined them to be. Cool, young folks, 100% tech enthusiasts, and open minded.

One of the new hires in the new company wanted a 6 months internship between his studies. Instead they offered him a full time job - for the 6 months. They even offered me to pay back my scholarship that I will own my old company for leaving early. This is awesome.

The only things that will be worse than my old job are, that I have to negotiate payment instead of yearly increases, 4 days less paid vacation, so only 26 days, and 40h weeks. And they have no workers council, which isn't good, but it's not the worst either.

I got them fixed on 57.000€, not including an up to 10.000€ annual bonus. The way you achieve your bonus seems good to. It's split in two parts, internal and external bonus. Internal bonus is when you engage with internal events like tech calls, sharing your knowledge on your main IT topics, etc. External Bonus is a bit more complicated, but also straight forward. You work on projects for customers, and if you have less than 3 weeks a year that you dont participate in an project, you get the full bonus.

Last friday, I filed a request for a certificate of employment from my current team lead, this is odd for her because I have never done it before, and she asked why I requested it. I said to her that we can talk about it, and she agreed but didn't call me, yet.

Lastly, another good friend of mine will be employed by my team soon, but for a fraction of the payment that I currently receive! He is doing the exact same work, and even worse, he is doing project managment for his main developer project too! And is getting less paid... I just cant...

Yesterday we needed to update a few cloud instances, the only other person who knows about setting up CICD and our OpenShift Containers than me is only in part time and works two days a week, his trainee didn't know anything, so it's up to me. This isn't hard or anything, but it shows that this system our mangement maintains will fail soon, maybe even with me going? I sure hope so tbh.

One of you guys said, I should go to my team lead and negotiate a higher pay, but the truth is, that because we are a big ISP we have an collective agreement for payment and are grouped by tasks (which is bull shit btw, because I'm doing tasks much higher paid than currently). This also means that I cannot simply jump in another group, and can only increase my current pay to about 115%, which is done automatically every year by 5% up to 115%. Anything above is considered extra, but I don't think they will go with it.

I will decide this week about my future at the old company, but I really don't know what to do...

Below is a transcript from work Slack today. Only the names and some code are changed. It ended up causing a bit of drama. DevRanters, what do you take from this?

---

Delivery Lead:
Hey Gang. What's the blocker for FEATURE-123?

Dev1:
FEATURE-122 crashed on iOS app when viewing Feature Introduction page.

Teach Lead:
I've talked about this with Dev1 on a side channel.
And diagnosed the stack trace.
It looks like there is/was some bad handling of a List in the Feature Introduction view logic.
But this is confined to changes that Dev2 is still working on.
(It's not present in master)
Dev2, what's your current position on this?

Dev2:
I have tested at my end with Dev1 but it seems to be working fine

Tech Lead:
There is a race condition related to the use of someList.first()
My guess is that theres a Flow of those lists defined, with an initial value of emptyList
And that on your machine, that Flow is updating with a new value quickly enough that it doesn't matter.
But on Dev1's, for whatever reason, it doesn't get there in time, hits the empty list and falls over.
The logic that's performing the first() needs to gracefully handle empty lists as well.

Dev2:
Where is that logic called?

Tech Lead:
Here's the stack trace Dev1 provided in our conversation earlier:
Caused by: kotlin.NoSuchElementException: List is empty.
...
at 3 iosApp 0x00000000 kfun:kotlin.NoSuchElementException#<init>(kotlin.String?){} + 00
at 4 iosApp 0x0000000 kfun:kotlin.collections#first@kotlin.collections.List<0:0>(){0§<kotlin.Any?>}0:0 + 000
...
at 9 iosApp 0x0000000 kfun:kotlin.coroutines.native.internal.BaseContinuationImpl#resumeWith(kotlin.Result<kotlin.Any?>){} + 0000

This line:
kfun:kotlin.collections#first@kotlin.collections.List<0:0>()
...says that it's first() being called on an empty list.

Dev1:
FYI: Dev3/Dev4/myself are seeing the same issue with the same stack-trace above.

Tech Lead:
So Dev2, have you introduced such a call?
Because I checked master branch and there isn't one, in that version of the file.
Ok, I'll check your working branch Dev2
...
Yes you have here:
var processed1 = someList.first()
var processed2 = someList.first()
...
Lines 123, 124.
Solution looks really straightforward guys.

Dev2:
Okay, I will fix that and push the change

Tech Lead:
Check if someList is empty and allow for generating / handling null processedValues in the view.

Now; I'm going to be straight with you here.
This issue has been discussed over several hours today.
I expect that either one of you could have gone through the process I did in the last 10 minutes above, and resolved it in the same way :point_up:

Dev2:
I went on a break and it's not reproducible on my machine

Tech Lead:
I didn't reproduce it on mine either.

Dev1:
Dev2 and myself are now on sharing screen to sort this issue out. Hope to update back later.

Tech Lead:
<Screen shot of diff with changed code>
:point_up: That change should do it.

Dev2:
Already have pushed the change.

Tech Lead:
...just seen it, is good - same approach :ok_hand:
Dev1 please let us know when tested on your machine.

Dev1:
That does it. It fixes the issues. Thank you, Dev2. I will pick it off from here.

Tech Lead:
Glad to hear it guys.

Dev1:
I have to say this that it is not because we are not working on the issue - Dev2 and myself (together with Dev3/Dev4) have been on this issue all this morning. It just difficult to connect the dot when it wasn't reproducable on Dev2's machine. I brought the issue up because I wanted to switch to working on other tickets while waiting for this to resolve. Still thank you largely for Dev2's work and your keen eyes that spot and resolve the issue quickly.

Tech Lead:
Noted Dev1.
I think the take-away has to be to read the stack-trace carefully... don't worry - we've all been guilty of not reading the error in full, at some point.
The stack trace said that the 'first' element is being referenced from an empty list - that's just logically impossible, right?
Looking for that call to first, we saw it wasn't in the code before, and is after (two of them, in fact).
So then we ask ourselves, how can we deal with an empty list - and then solution almost presents itself.
It didn't really take reproduction of the error to resolve.
Maybe working with a new tech stack creates an anxiety that every issue faced will have a complex solution related to that stack; but I think you'll agree, this particular issue really just required a deep breath and your trusty 'debugging skills 101'... don't lose them! :smiling_face:

TL;DR; do your best all you like, strive to be the #1 if you want to, but do not expect to be appreciated for walking an extra mile of excellence. You can get burned for that.

They say verbalising it makes it less painful. So I guess I'll try to do just that. Because it still hurts, even though it happened many years ago.

I was about to finish college. As usual, the last year we have to prepare a project and demonstrate it at the end of the year. I worked. I worked hard. Many sleepless nights, many nerves burned. I was making an android app - StudentBuddy. It was supposed to alleviate students' organizational problems: finding the right building (city plans, maps, bus schedules and options/suggestions), the right auditorium (I used pictures of building evac plans with classes indexed on them; drawing the red line as the path to go to find the right room), having the schedule in-app, notifications, push-notifications (e.g. teacher posts "will be 15 minutes late" or "15:30 moved to aud. 326"), homework, etc. Looots of info, loooots of features. Definitely lots of time spent and heaps of new info learned along the way.

The architecture was simple. It was a server-side REST webapp and an Android app as a client. Plenty of entities, as the system had to cover a broad spectrum of features. Consequently, I had to spin up a large number of webmethods, implement them, write clients for them and keep them in-sync. Eventually, I decided to build an annotation processor that generates webmethods and clients automatically - I just had to write a template and define what I want generated. That worked PERFECTLY.

In the end, I spun up and implemented hundreds of webmethods. Most of them were used in the Android app (client) - to access and upsert entities, transition states, etc. Some of them I left as TBD for the future - for when the app gets the ADMIN module created. I still used those webmethods to populate the DB.

The day came when I had to demonstrate my creation. As always, there was a commission: some high-level folks from the college, some guests from businesses.

My turn to speak. Everything went great, as reversed. I present the problem, demonstrate the app, demonstrate the notifications, plans, etc. Then I describe at high level what the implementation is like and future development plans. They ask me questions - I answer them all.

I was sure I was going to get a 10 - the highest score. This was by far the most advanced project of all presented that day!

Other people do their demos. I wait to the end patiently to hear the results. Commission leaves the room. 10 minutes later someone comes in and calls my name. She walks me to the room where the judgement is made. Uh-oh, what could've possibly gone wrong...?

The leader is reading through my project's docs and I don't like the look on his face. He opens the last 7 pages where all the webmethods are listed, points them to me and asks:
LEAD: What is this??? Are all of these implemented? Are they all being used in the app?
ME: Yes, I have implemented all of them. Most of them are used in the app, others are there for future development - for when the ADMIN module is created
LEAD: But why are there so many of them? You can't possibly need them all!
ME: The scope of the application is huge. There are lots of entities, and more than half of the methods are but extended CRUD calls
LEAD: But there are so many of them! And you say you are not using them in your app
ME: Yes, I was using them manually to perform admin tasks, like creating all the entities with all the relations in order to populate the DB (FTR: it was perfectly OK to not have the app completed 100%. We were encouraged to build an MVP and have plans for future development)
LEAD: <shakes his head in disapproval>
LEAD: Okay, That will be all. you can return to the auditorium

In the end, I was not given the highest score, while some other, less advanced projects, were. I was so upset and confused I could not force myself to ask WHY.

I still carry this sore with me and it still hurts to remember. Also, I have learned a painful life lesson: do your best all you like, strive to be the #1 if you want to, but do not expect to be appreciated for walking an extra mile of excellence. You can get burned for that.

My Technical lead always asks one question to new interviewing candidates. "Write a SQL query to find the second highest salary from employee salary table". It's the same question which he faced in one interview and he didn't have answered it.
Sorry for my bad English..

I had mentioned before I got offered a new role, with 50% increase.

I wasn’t expecting my current employer to counter, but they suddenly shat themselves and basically matched the salary, and offered promotion to software developer (sans junior). They acknowledge my role within the company is only increasing in responsibility and so far I have exceeded expectations. Its a nice response to have from them, although I do wonder how long it might have taken without the panic.

The new company have counter-countered, promising to raise salary by a further 20% of total, within the first 6 months, provided I learn React reasonably quickly (about a month), integrate with the team and start to take on my roles within the Agile set relatively independently (3-6 months). They also don’t bother with the junior role title at these pay bandings.

I currently get about half an hour a week with my lead dev on sticking issues. In this new team, I would be one of ten javascripters, working towards best practices, TDD etc. This is absolutely the realm I want to specialise in, at the first stage of my career.

I said I would stay with my current employer, before the counter counter move. Now I am full of doubt.

Has anyone landed in teams like this, only to find they didn’t offer increased learning at all? If that was a high risk for me, I wouldnt take it, despite the offer of more cash. I’d sooner get more skilled in the stuff I have been working in at my current role.

Pretty amazing how much amazing life experiences can cause anxiety. Never been in the middle of a bidding war before...

I work in a small scale company based on Kolkata, India. It's my first job and I have been working here for last 6 and half years. Now I am the technical lead there.

I love my job. I love taking new challenges which I need to solve on my own (most of the times). My working hours are 9am to 6pm. Hardly I have to stay late at office. Even if I have any client meeting after 6, I do it from home. I am never tired on Mondays, I love to join my office. I can do my personal projects after reaching home, sometimes even in the office. All these goods come with a small price, I get less salary than my friends who are working on the MNCs (e.g. IBM, TCS, HP etc). They are frustrated though, with their jobs, with their bosses, with the long working hours. I am not. Sometimes I feel bad that I earn less. But that feeling doesn't stay much longer. It goes away whenever I join the office and get a new thing to do.

I have rejected offers from many companies. That includes all the major MNCs working in India. I feel bad about that sometimes, just like currently I am feeling. One my friend (a really bad developer) is roaming in the New York city, he is there for an onsite project. I know I can't go their, at least now. And that feels bad.

What should I do? Does it make me an idiot to stay in a company for more than 6 years? Should I switch and join an MNC like everyone does? I am confused. Pretty confused.