!rant

After over 20 years as a Software Engineer, Architect, and Manager, I want to pass along some unsolicited advice to junior developers either because I grew through it, or I've had to deal with developers who behaved poorly:

1) Your ego will hurt you FAR more than your junior coding skills. Nobody expects you to be the best early in your career, so don't act like you are.

2) Working independently is a must. It's okay to ask questions, but ask sparingly. Remember, mid and senior level guys need to focus just as much as you do, so before interrupting them, exhaust your resources (Google, Stack Overflow, books, etc..)

3) Working code != good code. You are an author. Write your code so that it can be read. Accept criticism that may seem trivial such as renaming a variable or method. If someone is suggesting it, it's because they didn't know what it did without further investigation.

4) Ask for peer reviews and LISTEN to the critique. Even after 20+ years, I send my code to more junior developers and often get good corrections sent back. (remember the ego thing from tip #1?) Even if they have no critiques for me, sometimes they will see a technique I used and learn from that. Peer reviews are win-win-win.

5) When in doubt, do NOT BS your way out. Refer to someone who knows, or offer to get back to them. Often times, persons other than engineers will take what you said as gospel. If that later turns out to be wrong, a bunch of people will have to get involved to clean up the expectations.

6) Slow down in order to speed up. Always start a task by thinking about the very high level use cases, then slowly work through your logic to achieve that. Rushing to complete, even for senior engineers, usually means less-than-ideal code that somebody will have to maintain.

7) Write documentation, always! Even if your company doesn't take documentation seriously, other engineers will remember how well documented your code is, and they will appreciate you for it/think of you next time that sweet job opens up.

8) Good code is important, but good impressions are better. I have code that is the most embarrassing crap ever still in production to this day. People don't think of me as "that shitty developer who wrote that ugly ass code that one time a decade ago," They think of me as "that developer who was fun to work with and busted his ass." Because of that, I've never been unemployed for more than a day. It's critical to have a good network and good references.

9) Don't shy away from the unknown. It's easy to hope somebody else picks up that task that you don't understand, but you wont learn it if they do. The daunting, unknown tasks are the most rewarding to complete (and trust me, other devs will notice.)

10) Learning is up to you. I can't tell you the number of engineers I passed on hiring because their answer to what they know about PHP7 was: "Nothing. I haven't learned it yet because my current company is still using PHP5." This is YOUR craft. It's not up to your employer to keep you relevant in the job market, it's up to YOU. You don't always need to be a pro at the latest and greatest, but at least read the changelog. Stay abreast of current technology, security threats, etc...

These are just a few quick tips from my experience. Others may chime in with theirs, and some may dispute mine. I wish you all fruitful careers!

Scene: Senior developer left, 3 Junior devs(including me) are now loaded with work.

*Intern asks for help*

JuniorDev1: I have 2 projects of which i'm the lead on one. I don't have time to help anyone.
JD2: 2 projects as well dude, speak to me after work, much easier then.
Me: 3 projects, lead on two. Sure how can i help you.

Took less than 5 minutes to help the intern.

2 hours Later. Check in meeting

PM: Our Junior devs are really busy and can't always help you guys. JD1 are you overloaded?

JD1: Yes, is their anyway we can split the one projects work?

PM: Sure. JD2 are you overloaded?

JD2: Not really, but i agree on splitting the projects between the three of us.

Me: *Are these fuckers serious? i have three projects, they have 2 and they wanna give me more work because they are overloaded and don't know how to manage their time*

PM: Ok cool, i'll update it. CooCooK4Choo, i see you building your own game during lunch time. You definitely not overloaded.

Me: Actually! what i do in my lunch time is my own personal work because it's the only time i have to work on personal projects. I actually do feel overloaded with the 3 projects and now more work from them, could we split the work load evenly please.

PM: I thought you said you could handle the 3 projects?

Me: I can, i have been, but with more work coming my way i don't think i'll be able to.

PM: Unfortunately i need the other Junior Devs on demand, so i won't be able to split the work load evenly.

Me: On demand for what? Why not let the interns help?

PM: In case i need their help. The interns are helping the other Junior Devs with things that don't require too much out of them.

Me: *This FUCKEN BITCH!* Cool, I'm done with the 1 project, expect the business rules at the end of the day. I'll see if i can get the other 2 near done by Friday so i can have time to look over the code of the new projects that i'll be splitting with the other Junior Devs.

PM: Cool, glad we all on the same page.

You know what? FUCK this stupid shit of favoring people in the FUCKEN work place.
This is my first full-time job ever, I've been here for a full year today and i can honestly say these people are just giant children with money. I should know, out of work i am a giant child, but from 8:00 - 16:00 i'm a FUCKEN adult.

After listening to two of our senior devs play ping pong with a new member of our team for TWO DAYS!
DevA: "Try this.."
Junior: "Didn't work"
DevB: "Try that .."
Junior: "Still not working"

I ask..
Me:"What is the problem?"
Few ums...uhs..awkward seconds of silence

Junior: "App is really slow. Takes several seconds to launch and searching either crashes or takes a really long time."
DevA: "We've isolated the issue with Entity Framework. That application was written back when we used VS2010. Since that application isn't used very often, no one has had to update it since."
DevB: "Weird part is the app takes up over 3 gigs of ram. Its obviously a caching issue. We might have to open up a ticket with Microsoft."
Me: "Or remove EF and use ADO."
DevB: "That would be way too much work. The app is supposed to be fully deprecated and replaced this year."
Me: "Three of you for the past two days seems like a lot of work. If EF is the problem, you remove EF."
DevA: "The solution is way too complicated for that. There are 5 projects and 3 of those have circular dependencies. Its a mess."
DevB: "No fracking kidding...if it were written correctly the first time. There aren't even any fracking tests."
Me:"Pretty sure there are only two tables involved, maybe 3 stored procedures. A simple CRUD app like this should be fairly straight forward."
DevB: "Can't re-write the application, company won't allow it. A redesign of this magnitute could take months. If we can't fix the LINQ query, we'll going to have the DBAs change the structures to make the application faster. I don't see any other way."

Holy frack...he didn't just say that.

Over my lunch hour, I strip down the WPF application to the basics (too much to write about, but the included projects only had one or two files), and created an integration test for refactoring the data access to use ADO. After all the tests and EF removed, the app starts up instantly and searches are also instant. Didn't click through all the UI, but the basics worked.

Sat with Junior, pointed out my changes (the 'why' behind the 'what') ...and he how he could write unit tests around the ViewModel behavior in the UI (and making any changes to the data access as needed).

Today's standup:
Junior: "Employee app is fixed. Had some help removing Entity Framework and how it starts up fast and and searches are instant. Going to write unit tests today to verify the UI behaivor. I'll be able to deploy the application tomorrow."
DevA: "What?! No way! You did all that yesterday?"
Me: "I removed the Entity Framework over my lunch hour. Like I said, its basic CRUD and mostly in stored procedures. All the data points are covered by integration tests, but didn't have time for the unit tests. It's likely I broke some UI behavior, but the unit tests should catch those."
DevB: "I was going to do that today. I knew taking out Entity Framework wouldn't be a big deal."

Holy fracking frack. You fracking lying SOB. Deeeep breath...ahhh...thanks devRant. Flame thrower event diverted.

You know what?

Young cocky React devs can suck my old fuckin LAMP and Objective-C balls.

Got a new freelance job and got brought in to triage a React Native iOS/Android app. Lead dev's first comment to me is: "Bro, have you ever used React Native".

To which I had to reply to save my honor publicly, "No, but I have like 8 years with Objective-C and 3 years with Swift, and 3 years with Node, so I maybe I'll still be able help. Sometimes it just helps to have a fresh set of eyes."

"Well, nobody but me can work on this code."

And that, as it turned out was almost true.

After going back and forth with our PM and this dev I finally get his code base.

"Just run "npm install" he says".

Like no fuckin shit junior... lets see if that will actually work.

Node 14... nope whole project dies.

Node 12 LTS... nope whole project dies.

Install all of react native globally because fuck it, try again... still dies.

Node 10 LTS... project installs but still won't run or build complaining about some conflict with React Native libraries and Cocoa pods.

Go back to my PM... "Um, this project won't work on any version of Node newer than about 5 years old... and even if it did it still won't build, and even if it would build it still runs like shit. And even if we fix all of that Apple might still tell us to fuck off because it's React Native.

Spend like a week in npm and node hell just trying to fucking hand install enough dependencies to unfuck this turds project.

All the while the original dev is still trying TO FIX HIS OWN FUCKING CODE while also being a cocky ass the entire time. Now, I can appreciate a cocky dev... I was horrendously cocky in my younger days and have only gotten marginally better with age. But if you're gonna be cocky, you also have to be good at it. And this guy was not.

Lo, we're not done. OG Dev comes down with "Corona Virus"... I put this in quotes because the dude ends up drawing out his "virus" for over 4 months before finally putting us in touch with "another dev team he sometimes uses".

Next, me and my PM get on a MS Teams call with this Indian house. No problems there, I've worked with the Indians before... but... these are guys are not good. They're talking about how they've already built the iOS build... but then I ask them what they did to sort out the ReactNative/Cocoa Pods conflict and they have no idea what I'm talking about.

Why?

Well, one of these suckers sends a link to some repo and I find out why. When he sends the link it exposes his email...

This Indian dude's emails was our-devs-name@gmail.com...

We'd been played.

Company sued the shit out of the OG dev and the Indian company he was selling off his work to.

I rewrote the app in Swift.

So, lets review... the React dev fucked up his own project so bad even he couldn't fix it... had to get a team of Indians to help who also couldn't fix it... was still a dickhead to me when I couldn't fix it... and in the end it was all so broken we had to just do a rewrite.

None of you get npm. None of you get React. None of you get that doing the web the way Mark Zucherberg does it just makes you a choad locked into that ecosystem. None of you can fix your own damn projects when one of the 6,000 dependency developers pushes breaking changes. None of you ever even bother with "npm audit fix" because if security was a concern you'd be using a server side language for fucking server side programming like a grown up.

So, next time a senior dev with 20 years exp. gets brought in to help triage a project that you yourself fucked up... Remember that the new thing you know and think makes you cool? It's not new and it's not cool. It's just JavaScript on the server so you script kiddies never have to learn anything but JavaScript... which makes you inarguably worse programmers.

And, MF, I was literally writing javascript while you were sucking your mommas titties so just chill... this shit ain't new and I've got a dozen of my own Node daemons running right now... difference is?

Mine are still working.

I’ve had a good amount of incompetent co-workers in the past. One that stands out was this junior developer who worked at one of my previous companies. He was incompetent, but that wasn’t even his worst attribute. He was incompetent, and worse, he had a piss-poor attitude.

Myself and a few other devs at the company tried to help him, but he would literally get mad when people tried to help him. Sometimes he would even call one of us over and start getting snarky with us as we tried to help him. He was a piece of shit and a shitty developer. I don’t think he built one complete feature or fixed one bug in the year he was at the company before he was eventually fired.

Oh, and aside from his incompetence and shitty attitude, he had no sense of humor. It was so annoying. My friend and I made a little song based on his name and a group that sounded like his name, and he got pissed. We always used to sing it anyway after that and it always riled him up. I feel a bit bad about that now but he pretty much got mad at everything so whatever.

One of my favorite memories of him is when he was leaving one day, my good friend/co-worker and I were having a Nerf gun battle. The junior was leaving the office, and my friend tried to get him involved in the battle and shot him, but accidentally hit him in the back of the head. He said nothing, didn’t turn around, and just walked out lol. He was not happy about it.

This is how one of our junior devs solved a merge conflict

Root interviews for a job

So I've been interviewing for fun lately (and for practice), and it's been going mostly well. This one company in particular looks interesting, and they seem to really like me. This morning was interview #4 with them; tomorrow morning is #5.

The previous interviews were pretty enjoyable, especially the last one where I interviewed with one of the senior devs who gave me his "grumpy old man rails quiz." He actually asked some questions I wasn't able to answer! (Mostly dealing with Rails' internals.) Also when showing me the codebase, there were a few things I hadn't seen before, so it's exciting that I'll actually be able to learn something if I sign on. We ended up talking for almost an hour past our allotted time, and we got along famously. He said he was very surprised I did so well on his quiz because most people don't. Everyone else I interviewed with so far has liked me and gave positive reviews, too.

I don't know if I want the job, but that's beyond the scope of this rant anyway. The real reason for this comes next.

My interview today was with the VP of engineering. It was more of a monologue, as he wanted to give me perspective to see if I actually wanted to work there, but it was still very much a monologue. He's an old white guy who seems to loves to drone, and he never seemed very happy when I responded, so I let him drone and drone. Good information though.

But he's very set in his ways in some regards, and two of them were pretty insulting. We never really talked about technicals, and he just assumed that since I wasn't old and graying that I was a junior dev. He said, and I'll quote: "We run a lean but senior team, so we typically only hire senior devs here. But the dev team is all old white men. There's no diversity in talent, age, sex, race, religion, etc, and I'm looking to change that." He made several more allusions to my more junior level, too. He made a lot of assumptions (like how I'm not comfortable with structure because I've been the only dev so often) and got annoyed when I countered them.

I realize he has no idea of my skill level -- even though he should if he was listening to his team -- but to just assume that I'm not talented because I'm young, and bloody hire me just because I'm female? I don't want to be your diversity hire, old man. 🤬

So I'm feeling angry.
I might still take the job because the it offers considerable benefits over where I'm working (despite being quite happy here), but it will absolutely be despite him.

At age of 20, I got hired as junior dev at a mobile gaming company. We were 2 junior devs hired at the same time and one of our senior colleagues made a prank: he came in the office before us and rearranged our offices in a "funny" manner.

Two days later I waited for him to go home. I opened his PC case, removed the power button cable from the motherboard and then re-arranged everything back to normal. Well, I couldn't resist...

Next day he came into the office and, well, surprise... the PC was not starting. He went to the IT department and they spent 4 hours trying to figure out why it was not working. They replaced the CPU, RAM memory, including the PSU.

I had to go and tell them: "maybe it's the power button jack?!".

I got into some problems for that prank. Indeed I crossed a line, but what the hell... that was a bad IT department.

when your boss tells you they hired you just to save money, and the job should actually be done by a team of intermediate/senior devs, but they thought one junior dev could do it in the same time span

*Client phones me at 11pm*
Client: It's not working!!
Me:What's the error you're getting?
Client: "Database connection error"
*Phones system/dB admin*
DB Admin: Yeah we had to change the SQL logins, I've sent you the new ones
*Phones junior dev in charge of dB programming*
Junior Dev: Yeah you'll just have to go and change the credentials. They're in all the places where we're using the dB, just before the statement, in the connection strings...

We make over 470 calls to the DB 😑

LAPTOPS is basically identical to PAPRIKA on a swipey phone keyboard.

So today there were 5 smartass junior devs sitting in a meeting with bell peppers, because I asked them to bring their paprika.

Thanks @dfox
As a junior,
This week's topic is giving a lot of best advises to me from other devs..

Back in the day when I was a junior developer, I somehow got hired by this guy who asked me to code his entire platform from scratch. I was being paid a junior dev salary, being asked to do senior dev work, and unfortunately I needed the money, so I didn't want to turn the job down. So I did what any junior dev would do in the situation... I decided to experiment and ended up with an insanely inefficient codebase.

For some stupid reason I thought that a good DB model would be to pull one record from the DB at a time, and then just repeat the method in a loop as needed. Keep in mind I was a self-taught junior dev. The backend worked great during development, and after 3 months of developing we decided to add a lot of data in the DB for further testing, and... you guessed it... the platform slowed down like shit!

Moral of the story... u get what you pay for, so hire great talent and pay them well! And also that self-taught junior devs don't know that the f@*k they are doing sometimes.

So there is this girl who joined the company as a trainee.

The company developed a 1 year project to train 25 trainees and she joined saying that she already had some experience making websites. (remember this)

They started in the beginning of January and stayed for about 3 months just studying the platform (Salesforce) and receiving some classes from Senior Devs, on subjects like OOP basics, loops, conditions and features of the platform.

After this time they joined the teams, 2 joined my team, a guy with 32 years that worked 10 years in a bank and wanted to go for a IT job and the girl of 22.

We gave her a really small task, just to make a code to copy info from one field to the other on a list of objects.

After 3 days of saying she was working on it we asked her to show us the code, she had written the "code" directly in the class, VS Code was going crazy with errors. When we asked her "But where is the method?", she answered "What is a method?"

After it we had other experiences trying to teach her some things. The team was formed by me (mid level dev), another mid level dev, a senior and a architect (who was self taught and one of the best teachers I've ever seen).

We tried for about 3 months to teach her how to do basic stuff, like a for loop, and every time we learned that she was missing some "foundations" of this basic stuff, so we would come back and explain the foundation, and a couple times she needed to use this knowledge like a week later and didn't remember shit.

So after this the team talked with our leader that we wanted to let her go and focus on the other guy who was going really well and some other junior devs who had joined the team.

But the HR found out that she had sued her last company, we don't know the reason, but HR guys were afraid of firing her without a careful firing process.

So now we're stuck with her in the team, and everything we ask her to do need to be remade, not because the code is bad, but because it NEVER works

And after all this I still ask myself, how did she finish college? Every person that i know that studied CS or CS like courses had a lot of OOP or at least knew what a class and a method were supposed to be.

Senior devs out there, please be supportive to juniors. Don't treat them bad just because they don't know as much as you do. Guide them and help them learn and grow as devs. That'll make your company (and/or the community) a better place to work at, because everyone will be a better dev, and you might learn and grow in the process as well.

My first dev job. Me and another guy get hired at the same time. He will be the lead dev, and I’ll be the junior dev on a long term project. Project gets delayed (and eventually canceled, but that’s a different story), so the lead dev decides to give me programming challenges to test my skill level. I successfully complete the challenges, but they aren’t up to his standards. Belittles me in front of our manager. Afterwards I ask him to show me how he would have done it. The dude can barely type let alone show me the way it should be done. I say nothing to the manager.

A few weeks pass, it’s clear the project we were hired for is canceled, so we are given other work. They task the lead dev with porting the company website to Wordpress so non-devs can alter content. They chose Wordpress mainly because the lead dev said he is familiar with it. Two weeks later, no progress has been made. They ask me if I can do it, and I do it in 2 days including additional functionality that was requested. Manager asks me why I thought lead dev couldn’t do what I did. I said, “I don’t think lead dev knows what the fuck he is doing. I don’t think he knows how to program.” Manager says, “Huh.”

Several months later lead dev is still there, but has yet to work on any projects with any success. They finally let him go.

Glad to finally get that off my chest.

Start-up: hires 3 junior devs to save money.

Start-up: expects things to get done faster-- BUT-- Start-up keeps adding things to the TO-DO list and backlog-- i.e. it's all relative!!

Start-up: gets angry at 3 junior devs why they can't deliver when they keep adding tasks and ask we fall behind.

Dev team: "Seriously? You hire more devs to finish tasks faster, but you keep adding more than are being finiahed-- obviously it's gonna take longer now regardless"

Git --pull life together

For an ostensibly security-focused financial company, these people really don't know what they're doing. Everything I've seen thus far is so hacked-together that I feel like i'm looking at code written by high schoolers.

Seriously, some of API Guy's code is better than this.

And they even make a point to remind me of ultra basics like `.to_a`, `.map`, or "a good command to keep on hand is `rake db:migrate`" -- like seriously? Those are in bloody "Intro to Rails" tutorials (and it's `rails db:migrate` as of Rails 5). For an ostensibly all-senior team, these devs are awfully junior.

Hi Junior devs, we love you 👋

I’m getting really tired of all these junior-turn-senior devs who can’t write simple code asking ChatGPT to solve everything for them.

I’m having to untangle everything from bizarre organization/flow to obvious gotchas / missed edge cases to ridiculously long math chains (that could be 1/10th the length), or — and I feel so dirty for this — resorting to asking ChatGPT wtf it was thinking when it obviously wrote some of these monstrosities. Which it gets wrong much of the time.

“ALL HAIL CHATGPT!” Proclaims the head of Engineering. “IT’S OUR PRODUCTIVITY SAVIOR! LEVERAGING AI WILL LET US OUTPERFORM THE ENTIRE INDUSTRY!”

Jesus fucking christ.

Starting to wish I never got involved in this industry.

I am working for the most ridiculous, god awful place I have ever had the misfortune of working and I am having a HELL of a time getting out of it because everything wants 5 years fucking exp in some fucking specific framework that is basically the same as every other fucking framework.

Our previous cto was a closeminded totalitarian bully and when she finally left she was replaced by a lecherous fucking dinosaur who has no idea how to code in our code base. He also has barely been showing up to work for the last few months.

For some reason our fucking ceo allows this all to continue and only interjects whenever he can make himself the biggest nuisance (ie design handoffs etc where he has little to no knowledge)

I was already woefully underpaid but was recently 'promoted' to team lead and when I brought up my ridiculous salary (yes I was essentially just funneled into this role) they gave me a neglible raise and ceo told the fucking dinosaur to tell me he 'doesn't like when people ask for raises'

The only reason I am in this position is because we have such ridiculously poor employee retention and I am one of the people after only 2.5 years there that has the ability to provide any kind of knowledge transfer. Most of our dev team consists of people fresh out of school and our code base is just an absolute mess of junior dev spaghetti debauchery.

I have expressed concerns over this and was told that I'm negative and go looking for problems and that 'everywhere is like this'

The ceo has a few people he keeps close because in his words 'they're the only ones who don't disagree with me'

He also refused to hire anyone with experience because they cost too much and he doesn't like people who have opinions.

To make matters worse all the fucking dinosaur does is wander around and talk to the junior devs about video games.

His previous favorite past time was staring at my tits, ranting about his wife and telling me 'he'd offer to give me a back rub but you can't do that now a days'

I caught his fucking wife creeping me on LinkedIn a few months ago for some fucking reason.

Oh and as icing on the cake I had a fucking interview today for an intermediate angular position and a few minutes after I received an email saying that ACCTUALLY they had been informed they were now looking for a senior react dev.

Like seriously what the fuck.

!rant

At my last job, my boss would constantly tear my work apart, belittle me and patronise me. He didn't really understand web development and just wanted to hire someone to do it for him. I ended up burning out and he persuaded me to quit because of it cause he didn't want to go through the whole disciplinary process (because he had no real reason).

A year later, and I've had my first review with my current boss, who's also a developer. He said he's learned a lot from me, I've helped the business and the junior devs grow; and that he struck gold in hiring me. I've got no feelings of burnout and I actually enjoy going to work now.

I'll be the first person to say that I'm not the best developer on my team and my new boss was probably exaggerating with me a little bit, but it goes to show that the people you work with are some of the most important people in your life.

ARGH. I wrote a long rant containing a bunch of gems from the codebase at @work, and lost it.

I'll summarize the few I remember.

First, the cliche:
if (x == true) { return true; } else { return false; };
Seriously written (more than once) by the "legendary" devs themselves.

Then, lots of typos in constants (and methods, and comments, and ...) like:
SMD_AGENT_SHCEDULE_XYZ = '5-year-old-typo'

and gems like:

def hot_garbage
magic = [nil, '']
magic = [0, nil] if something_something
success = other_method_that_returns_nothing(magic)
if success == true
return true # signal success
end
end

^ That one is from our glorious self-proclaimed leader / "engineering director" / the junior dev thundercunt on a power trip. Good stuff.

Next up are a few of my personal favorites:

Report.run_every 4.hours # Every 6 hours
Daemon.run_at_hour 6 # Daily at 8am

LANG_ENGLISH = :en
LANG_SPANISH = :sp # because fuck standards, right?

And for design decisions...

The code was supposed to support multiple currencies, but just disregards them and sets a hardcoded 'usd' instead -- and the system stores that string on literally hundreds of millions of records, often multiple times too (e.g. for payment, display fees, etc). and! AND! IT'S ALWAYS A FUCKING VARCHAR(255)! So a single payment record uses 768 bytes to store 'usd' 'usd' 'usd'

I'd mention the design decisions that led to the 35 second minimum pay API response time (often 55 sec), but i don't remember the details well enough.

Also:
The senior devs can get pretty much anything through code review. So can the dev accountants. and ... well, pretty much everyone else. Seriously, i have absolutely no idea how all of this shit managed to get published.

But speaking of code reviews: Some security holes are allowed through because (and i quote) "they already exist elsewhere in the codebase." You can't make this up.

Oh, and another!
In a feature that merges two user objects and all their data, there's a method to generate a unique ID. It concatenates 12 random numbers (one at a time, ofc) then checks the database to see if that id already exists. It tries this 20 times, and uses the first unique one... or falls through and uses its last attempt. This ofc leads to collisions, and those collisions are messy and require a db rollback to fix. gg. This was written by the "legendary" dev himself, replete with his signature single-letter variable names. I brought it up and he laughed it off, saying the collisions have been rare enough it doesn't really matter so he won't fix it.

Yep, it's garbage all the way down.

This is for all the junior devs and people moving into the corporate world.

Remember, HR is there to protect the company, NEVER the employee.

Do not fall for the okie-doke when they tell you they are there to help.

If destroying you is cheaper in the long run than damage to the company then be sure they will slit you from ear-to-ear.

Trash, trash, trash.
Who the fuck writes this shit?

Who the fuck lets these trash should-be-junior devs roll their own crypto? and then approves it?

The garbage heap of a feature (signing for all apis) doesn't follow Ruby standards, doesn't follow codebase conventions, has `// this is bridge` style comments (and no documentation), and it requires consumer devs to do unnecessary work to integrate it, and on top of all this: it leaks end-user data. on all apis. in plaintext.

Fucking hell.

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.

This is basically my life

Rant from my old company:

CEO decided he could cut costs by outsourcing to cheap devs in other countries.

Does this, the new hires are super incompetent. We're now paying for a whole team that is adding work cause they keep fucking up.

Leadership is super happy with the "savings" (which is basically just the team here working harder to fix everything).

All the smart people start leaving, leading to a downward spiral.

Last I heard, one of my junior co-workers had been promoted to senior (he hardly had any coding experience).

Fuck them all

me when "fixing" a junior devs work.

Me: Hey Guys we've been working on this application(project 1) for 4 months and i think we're almost done.

Owner of Company(Not My Boss): CooCook4Choo we moving you to project 2, forget about the previous one.

2 months go by, project is completed.

Boss: I've got another project for you
Me: Awesome!

1 month later...

PM: We're moving you back to project 1
Me: Why?
PM: Our senior dev resigned, we only have junior Devs and we need a lot of help before deployment next month.
Me: Why am i moving back to a project i was taken off of
PM: Where an agile company and you will be moved off many projects
Me: **Fuuuuuuuuuuck!!!* Ok i'll need documentation of everything that happened in the past three months, the current issue, what the current sprint revolves around and A demo of what has been added.
PM: Relax, I've got a lot of work myself, you will get them soon.

2 days later, still don't have what i need, PM is on vacation.

Me: Guess i don't have any work to do.

99% of our server-side code is Python and PHP (legacy applications).

Asked a junior dev to make a small update to a PHP site so we could have it run some cleanup server side. Plenty of existing PHP code to look at and piece something together. Should be 50 lines max.

Did he use the existing PHP code to do this task? Nope. Did he at least use Python? Nope.

Node.js

His response?

"I couldn't figure it out and Node.js seemed to have good support for mongo so I used that instead."

We have 0 lines of server side javascript. Never had node installed. Literally none of the devs use node here. Not only is this completely outside of our tech stack, but he had to take the time to learn Node and JS just because he thought it was easier.

Much would of rather he put in twice as much time to learn the tools of our stack.

Hiring junior devs is a game of Russian roulette.

You can get some one who is smart and loves coding. In this case stack, limitations etc don’t matter and experience will be great for junior and the rest of the team

Or it will be a lazy person who watched 5 videos and think to be better than everyone else. 95% of juniors are these fuckers. Takes about 1 week to find out and fire… which starts the 3 months recruiting loop again.

I've never had a problem with helping junior devs but when their keyboard and mouse looks like they bought it used from a primary school - glossy and covered in food etc... All I can think is burn it..... Burn it with fire.
Seriously... Keep your peripherals clean... They get nasty pretty quickly.

I hate clients that tell the developers what to use without discussion.

We're paid to solve problems.

Dictatorship on tools and methodologies are okay with junior devs or interns, but when you have senior devs, it has to be a democracy.

Having limitations like browser versions or server capabilities are fine, but declaring which slider to use, you MUST use jquery, or all that jazz just grinds my gears.

First junior software dev job, asked what I wanted for hourly pay, replied “I need at least $13/hour to survive.” (This is in US, 2007, I was almost done with Bachelor in CS, single mom with two little kids, was also in the army national guard at the time)

I grew up poor, and was very ignorant about salary negotiations. So of course they offered $13/hour. I accepted, thinking it must be fair, and was glad to be making more than minimum wage. Six months in, I’m doing the same work as their devs with 2-4 years experience, find out they are billing clients $100/hour for my work. Then, to top it off, the COO makes a joke in a meeting about how it’s not a big deal for their “technical assistant” to be doing lackey work because he’s only paid $13. Fuuuuuuuuck. That comment still makes my blood boil.

I had a nice manager at the time that explained how salary negotiations worked, but I still think it’s lame as hell. I ended up getting put on salary, $50k/year, after threatening to leave.

Setting junior devs free for the first time

OH GOD I HAVE AN INTERVIEW FOR A JUNIOR SOFTWARE DEVELOPER POSITION ON THURSDAY

IN A COUNTRY THAT APPARENTLY HAS LESS JUNIOR DEVS POSITIONS THAN PRESIDENTS

WTF I DO THIS IS MY FIRST JOB INTERVIEW

Imagine this clusterfuck:
A small company creates its own CMS on PHP 5.5 and MySQL, coded by fresh junior devs who apparently just got into coding.

My new employer sadly is one of their customers and now I got the task to migrate a group of tightly linked websites on subdomains to an actually sane and maintainable CMS...

Fuck me...

Apparently the continuous extension of the websites over the years got so labor intense, that the mentioned company lacks the manpower to fulfill further development wishes.

I've looked into the code today... let me tell you, PTSD is helluva thing.

- Each subdomain has a complete copy of the Crap Management System, there is no use of composer packages and each of the 50 folders in the webroot contains a mix of source code and images or other resources.
- LESS is transpiled into CSS by PHP on requests.
- There is no central file for environment variables like a ".env".
- Each website uses at least 5 different versions of jQuery, of which some jquery.min.js files were manually modified.

Don't get me started on how the DB is organized...

My work on this has just started, there will be more I've yet to uncover.

"C'mon, man! Gimme a break!"

As a junior developer, your primary goal should be to learn and absorb as much as you can, not to try to make a name for yourself. It's all too common that I see devs fresh out of college with this amazing gung ho attitude that quickly devolves into needing to feel like the smartest person in the room.
This leads to an unnaturally inflated ego, a feeling of self importance, and blocks you from truly understanding what is going on in the stack in front of you.
That's not to say you can't try to take on difficult tasks, just be humble and ask for help when you need it, and don't make assumptions that might lead to rework later.
I would much rather you ask me a question then put up a PR that has wildly different assumptions because you didn't fully understand the acceptance criteria of a particular task.

tl;dr - sit down, shut up, do your job, learn what you can as fast as you can.

Sincerely,
A very fed up Senior Dev

I am tired of toxic politics at work.

Signs of a toxic workplace:

* (good) decisions are discouraged rather than encouraged.
Someone wants to introduce a great optimization and guess what the reply is (often from someone IT-ignorant): wait a minute, you can't do that because we have all these nifty little hacks and if you dare to suggest change to our shitty system, we could not allow that! We want to stay in our comfy zone, no no!

* no one can make a decision unless Mr. favorite-developer-everyone-likes says it's a good idea. And even if he's wrong, no one cares to listen to anyone else's idea on it. Stupid Feudalism. One man decides over the entire codebase. That's just idiocy. Where's TEAM in there?

* thinking years of experience equals intellectual capacity. It certainly does not! There are senior developers with 15 years of experience who don't even know how to open commandline, or they didn't even know about Chrome developer tools, or how the HTTP spec is built. That shit just makes me cry inside. How can you give these peoples the title of senior when they know less than a freshman year kid?!

* ignoring people's education and/or capacities. "You just graduated, so you're a noob". Right, I know more than you, you idiot. You've demonstrated your ignorance often enough. Stupid ignorant colleagues.

* blaming politics (every team blames the other team and there's constant tension)

* roaming ignorance (no one in the company, and I mean no one, besides me, knows enough about Information Technology to make competent decisions or analysis)

Politics:
What gives testers the idea that they know more than other members of the team? Why do they treat devs like they are mentally challenged?
What gives PO's that same idea?
What gives managers the idea that they can just yell at developers and threaten them with time pressure? Yeah, because the customers are breathing down their neck.

Just because I am a Junior Developer, that makes me stupid? I am tired of no one caring to listen to my ideas. I could save the company at the snap of a finger but everyone ignores my opinion (and often facts) on things.
People come in and instead of asking me for help, they ask everyone else for help, including the people who don't know shit about IT; now that's insulting.

Anyway, toxic politics.

!rant

I got a promotion at work!

Is it weird that I don't want it because I still feel like I have too much to learn to no longer be a "junior"? I'm happy that my hard work is paying off but I'm worried that this is how bad senior devs are made.

Junior devs splitting methods be like

The fact that this week's rant topic exists is the exact reason I never do freelance work. It always ends in horror.

I don't believe good fullstack devs exist. A good junior will assess their talents/passions and specialize to become a senior. They'll keep checking the rest of the market from the corners of their eyes and start moving when necessary. But eventually, focus and specialization is a must.

If that's true for the field of development... why would I invest time in marketing, support, sales, PR, legal?

Maybe you can earn a bit more gross income in freelance work — but I see my employer as a service provider, I "hire" them so I don't have to manage phone calls, lose sleep over court cases, play product owner or worry about getting paid.

I have a junior who really drives me up a wall. He's been a junior for a couple of years now (since he started as an intern here).

He always looks for the quickest, cheapest, easiest solution he can possibly think of to all his tickets. Most of it pretty much just involves copy/pasting code that has similar functionality from elsewhere in the application, tweaking some variable names and calling it a day. And I mean, I'm not knocking copy/paste solutions at all, because that's a perfectly valid way of learning certain things, provided that one actually analyzes the code they are cloning, and actually modifies it in a way that solves the problem, and can potentially extend the ability to reuse the original code. This is rarely the case with this guy.

I've tried to gently encourage this person to take their time with things, and really put some thought into design with his solutions instead of rushing to finish; because ultimately all the time he spends on reworks could have been spent on doing it right the first time. Problem is, this guy is very stubborn, and gets very defensive when any sort of insinuation is made that he needs to improve on something. My advice to actually spend time analyzing how an interface was used, or how an extension method can be further extended before trying to brute-force your way through the problem seems to fall on deaf ears.

I always like to include my juniors on my pull requests; even though I pretty much have all final say in what gets merged, I like to encourage not only all devs be given thoughtful, constructive criticism, regardless of "rank" but also give them the opportunity to see how others write code and learn by asking questions, and analyzing why I approached the problem the way I did. It seems like this dev consistently uses this opportunity to get in as many public digs as he can on my work by going for the low-hanging fruit: "whitespace", "add comments, this code isn't self-documenting", and "an if/else here is more readable and consistent with this file than a ternary statement". Like dude, c'mon. Can you at least analyze the logic and see if it's sound? or perhaps offer a better way of doing something, or ask if the way I did something really makes sense?

Mid-Year reviews are due this week; I'm really struggling to find any way to document any sort of progress he's made. Once in a great while, he does surprise me and prove that he's capable of figuring out how something works and manage to use the mechanisms properly to solve a problem. At the very least he's productive (in terms of always working on assigned work). And because of this, he's likely safe from losing his job because the company considers him cheap labor. He is very underpaid, but also very under-qualified.

He's my most problematic junior; worst part is, he only has a job because of me: I wanted to give the benefit of the doubt when my boss asked me if we should extend an offer, as I thought it was only fair to give the opportunity to grow and prove himself like I was given. But I'm also starting to toe the line of being a good mentor by giving opportunities to learn, and falling behind on work because I could have just done it myself in a fraction of the time.

I hate managing people. I miss the days of code + spotify for 10 hours a day then going home.

Am I really unlucky, or are juniors these days all lazy af and such pampered babies that need hand holding all the time?
So back when I was a junior, when I wanted to learn something new, I would ask for some pointers from my seniors, could be an article, a video or even a book. From there I would look up further knowledge, play with the idea in my machine. If I couldn't understand something, or if I needed a better explanation of something, I would go back to my senior, but it was really rare.
Then comes this modern day, I'm the senior now and I'm in charge of mentoring a bunch of kids, who would treat me like their personal chatgpt. "Hey Junior #0, this is something you may want to read to help your next ticket, let me know if you have difficulty". Next day junior #0 would come back and say "I don't understand, the article mentioned X but I don't know how to do X. Can you show me how to do X?". Bro, no one knows how to do X after being born, just google "how to do X" and it gives you the fucking answer. Why the fuck do you have to circle back to me because of this. Junior #1 would refuse to read any articles longer than 250 words, and require constant 1-1 meetings to give him personal lectures. Dude this is not a class room, grow the fuck up! Junior #3 would write the messiest code possible despite my efforts to introduce tons of resources, then complain "why I'm still junior, how do I grow". Bro maybe if you learned half of what I sent you, you would have gotten promote by now. Fucking lazy kids these days!
Oh I can't fire these juniors. Top management was very clear that "we don't have budget to hire other devs for you, it's your responsibility to train them better".

When you're laughing at all the rants about the junior devs, then remember you're a junior dev

Fucking hate when "senior" and "lead" devs ignore the advice of numerous junior devs when it comes to technical and process driven decisions. Especially when said higherups don't even code anymore and don't really understand the consequences of their decisions.

PORTFOLIO INFLATION

when every junior is writing algorithms, the next step up, the only way to keep up is writing apps. When every junior is writing apps, the next leg up is writing an entire SN.

Eventually junior full stack devs are writing microservice streaming cloud backend content delivery optimized social networks wrapped in virtualization with load balancing, proper CI, public accessible analytics apis, written in custom webaseembly compiled scripting backend utilizing both the latest graphql and every single feature of postgres, while also being a web site builder, an in browser app, mobile optimized, designed to transmogrify your asset pipelines linearflow functional-oriented modular rust cratified turbencabulator while cooking your turducken with CPU cycles, diffusing your gpt, and finetunning your llama 69 trillion parameter AI model to jerk you off all at the same time.

And then the title "wizard" becomes a reality as the void of meaning in our lives occupied by the anxiety of trying to reduce the fear of rejection in job hunting, is subsumed by the brief accidental glance into the cthulian madness-inducing yawning abyss of the future which is all the rest of our lives we have to endure existing for until at last sweet sweet death consumes us and we go to annihilation never having to configure one more framework or devops deploy of another virtual environment.

And it dawns on us that we no longer develop or write code at all. No, everything has become a "service" in this new hellscape future. We slowly come to the realization that every job is really just Costco greeter, or eventually going to be reduced to something equivalent, all human creativity, free will and emotions now taken care of by the automation while we manage the human aspects, like sardines pushing against one another not realizing their doom has been sealed along with the airless can they have been packed into, to be suffocated by circumstance and a system designed to reduce everything to a competition of metrics designed by the devil, if the metrics were misery", and "torture", while we ourselves are driven by this ratfuck wheel to turn endlessly toward social cannibalism, like rats eating their babies, but for the amusement of wallstreet corporate welfare whores who couldnt turn a dime if it wasnt already stolen.

And on our gravestones, those immortal words are carved, by the last person who gave up the ghost, the last whose soul wasnt yey shovelled onto the coal fires driving the content machine consuming the world:

Welcome to costco. I love you.

I'm the only developer in my company. I am a "junior dev" who started working like 6 months ago. Safe to say I am not well experienced and have a lot to learn in this journey. Due to this pandemic, my bosses who have been flaunting their wealth have started making losses and now needs to find another way to get money. Mind you, the company I work with is a marketing firm.
So what the bosses thought of doing was creating a delivery service due to the current situation. It is not their field but since they still need to show people they are the rich people, they need money either way. Since I'm the only developer in the company I've to make this application. I've to make an Android and iOS app with a back-end and an admin portal all in 1 month. My pay is shit and by shit I mean less than even 700 USD. I've not done a project like this before so there would be a learning curve as well. And there is no one to guide me either.
They think just because they have hired one developer anything development related is settled and I will do everything no matter how big or complicated or how shitty my salary is.
The feature list is a whole system, like it is so complicated that someone could really make their own company just to work on that application. It's HUGE.

I'm thinking of saying no I can't do this shit. But just wanted to see what some more experienced devs say about this. I've attached the features list in the rant.

Alright, this my fucking rant right here. Distraction? This whole company is a distraction! Boss decided to throw us all in an open work environment doing jobs that require careful concentration. Straight outta college I'm getting handed vague ideas, (make a desktop app that helps our customers put data on the internet, make an iPhone app) with out so much as an inkling of what technologies to use, just make it work.
Ok I will but when you hit a roadblock with very little resources to draw in it's hard to stay focused.
On top of that since I worked in support for a year I'm our senior support person! But sometimes support just doesn't use their brains and I'm using my time to solve very basic problems.
That brings me to my next point, the goddamn piece of shit that is our telephone. Fuck that thing when it rings it's never good. Moreover, since I don't want to get roasted for not being responsive I have the motherfucker forward to my personal cell. So I answer every fucking call and I get so many spam calls!
Not to mention I'm mainly running the hardware show around here. Shits broke I'm the one fixing it. Need new shit I'm putting the order together.
Tried to get a new guy to be the sys admin, ordered a 6th gen board with a 7th gen proc, had to pull 3 machines apart to get that sorted. Then he left bc family issues, and has been gone for weeks.
The other devs are also slam up busy, and the main product is about 15 people's piss on a plate of garb age spaghetti. (I got a lot of shit going on but at least I'm the only one pissing in my spaghetti) it's a constant run around if who does what with a code first plan later mentality causing confusion and delay.
Nobody wants to help anybody because they are also annoyed with this setup and are getting bitched at by customers or management.
Sales is mostly composed of a bunch of crackhead yes men and women who just want a commission and only half know the shit we sell and have sold 15 new features that had not been discussed. But management always says make it happen. In what priority? It's all a priority they say! Wtf.
So yea, then it brings me to me, dealing with this much chaos at work makes it seem like a high amount of chaos in my life is normal. I'm just now learning to control this.
I've had to do a lot of growing up as a person and as a developer. I've went from being the most junior to about the 3rd most seniors and I've no doubt my efforts have contributed to the growth of the company.
I'm a big believer in coding flow, and that it takes at least 15 mins to get in that flow and about 5 seconds to break it. There is no do not disturb on the company chat, everything always on fire it seems.
So fuck a lot of this, but I've done the research and where I'm at is the best opportunity in a 100 mile radius. So I am thankful for this job. Plus I usually win the horror story contest.

So TL;DR the biggest distraction is every fucking thing in this god forsaken place.

You utter &@£#s. You give rediclious promises to clients without consulting Devs how long items will take, when issues with project are clarified with client months in advance you turn around week before last and do a massive U turn. Expect junior developers to be masters of Photoshop, flash, server side technologies and to get around and code the front end. Then developers who are putting in the over time already you demand a massive load of overtime extra and threaten us if we don't meet the deadline?! Sat here blood boiling. last guy here litrually rage quit because of issues like this and #&## I think I'm going to too, so hard to try stay professional! ##&##&# I have had it!

Grr the feeling when one of your interviewers has a hard-on for trying to find ways to sink your boat.

Went to a job interview yesterday during my lunch break for a mid level dev job in central London , i have been trying to transition from a junior role.

First were two senior devs , that went quiet well...

Next up was the tech lead and a team lead, lets call the latter Mc-douche for some problem

The tech lead was fine, very relaxed and clam guy more interested in seeing the logic of my answers and questions as to why i did certain things in this or that manner....

Mc-douche, he would always try to find something wrong then smile smugly and do that sideways head waggle thing

His tech lead is like " yup that's correct"
But he would be like " yeeess but you didn't think about bla bla bla" then talk about shit not even present in the context of the question

Ah also he would ask a question then cut me off as soon as I begin to say that i didnt mention or take into account x or y even though literally my next sentence is about address those details he wanted.
let me fucking finish you dickbag 😡

Had a js question, simple stuff about dom manipulation, told not to bother with code... yet McD starts asking me to write the code for it....managed it , quite easy stuff

Then a sql and db test , again technlead was happy with the answers and the logic am approaching the question when writing my query, yet mc d Is bitching about SQL syntax....
Ok fine, i made a simple mistake, I forgot and used WHERE instead of HAVING in a group by but really?! Thats his focus ?!

Most devs I know look up syntax to do stuff , they focus on their logic first the do the impl.

Then a general question on some math and how i would code to impl a solution on paper
That was a 20 mins one, the question said they didn't expect me to finish it totally so
I approached it like an exam question.

First
I focussed on my general flow of my process, listing out each step.

Then elaborated each step with pseudo code showing my logic for each of the key steps.

Then went deeper and started on some of the classes and methods , was about to finish before it was time up.

Mc douch went through my solution
And grudgingly admitted my logic was "robust enough" it was like he really had to yank that deep out of his colon.

I didn't really respond to any of his rudeness throughout the whole interview,i either smiled politely or put on a keen looking poker face.

Really felt awful the rest of the day, skipped the gym and went home after work, really sucks to have a hostile interviewer.

Pretty sure i wont be hearing anything good from them even though the three other interviewers were happy with me I felt.

Being me. Fresh out of UNI with a three year bachelor in CS, no work experience. Starts in a big tech company with a lot promise of exciting project etc. Starts in 3 projects with one lead dev and two senior devs.

First month begins. I start by setting up my local environment and read documentations, which is fairly irrelevant and old. One of the senior devs quits.

Second month begins. Lead dev quits as well and the other senior dev having sick leave for the rest of the month. Basically I'm on my own, but thankfully not responsible for the projects.

Third month begins. The other senior dev is still sick. Nobody to help. Now I'm forced to talk to customer with a lacking knowledge of projects. Nobody knows what is going on. Hopefully my other senior dev will come back.

Fourth month begins. My senior have quit as well. I've been assigned as responsible of all three projects now. FML.

Fifth month begins. I begged my manager for help. Got a junior dev to help me with one of the projects. He and I still have no clue what we should do.

What a shitty start to a career as a developer.

Anybody having a similar experience?

Customer support people are weird.
They ping "Hi" and just leave it at that!

Wtf do you want me to do with your "Hi".

Is it something urgent I need to look at? Or some generic query?

But I won't fucking know that, unless I reply to your stupid context-less greeting. Because you can't bother to take an extra minute to type. Even worse when it is outside my work hours.

If I do decide to reply I am already online and lost my leverage on deciding whether it's actually urgent or not!

Fuck you Karen from support and fuck you Kumar.

And fuck you junior devs! Don't fucking "Hi. There?" me bitch! Type what you want I'll reply if it's worth it and when I have time to.

My boss pays me well and treats me well, but he expects me to do project management (documentation, giving tasks to 2 junior devs, reviewing their code, helping them when they are stuck), coding, architecture and to finish the project in a time record time.

When I told him that this week I will not work on development but will start to do documentation because the project got so big that it is difficult to keep track, and also the other 2 developers are waiting for tasks for me to give them, he looked disappointed.

I noticed and told him that if he wanted to speed up development, he must hire another project manager, or another senior developer because I can not do them both and expect to finish in a record time.

He keeps asking almost every day, "When are we going live?"

After years around devs of all levels of expertise I have found the following to be true mostly of junior developers.

Junior devs seem to like to pick out a single (or few) idiosyncrasies of a language/framework and then call it shitty overall.

While senior devs have seen the small idiosyncrasies of many languages/frameworks and know that none of them are perfect and those quirks come with the territory.

It may also have something to do with senior devs having less to prove and therefore not wasting their time of such useless language debates....

ROUND 1: FIGHT!

I hired 2 fresh out of school junior devs to work with me on my old web app.
They were brilliant, knew a lot of things, and were motivated.
They started complaining about how the code was shit, the db was shit, there were no best practices, the technology was old, bug fixing was boring, no comments in code.

I felt bad, very bad during 3 years, because they were absolutely right. I tried to work with them through better coding practices, rewriting, documenting etc.

Now they both have left.
I'm alone maintaining and evolving the application.
And I start to come across the code THEY developed.

What a bunch of shit. SQL queries bringing down the server. Duplicate code, because they didn't want even read the old one. Useless comments.
Performance killing functions. Exceptions swallowed without mercy. I have to clean up they poop.

I feel somewhat better, though. The application is still growing and holding the ground after many years and generating at least 800K$ per year in revenues.

Maybe better, but sad. I really wanted to share the project with somebody else but I failed, and I'm left alone....

After I spent 4 years in a startup company (it was literally just me and a guy who started it).

Being web dev in this company meant you did everything from A-Z. Mostly though it was shitty hacky "websites/webapps" on one of the 3 shitty CMSs.

At some point we had 2 other devs and 2 designers (thank god he hired some cause previously he tried designing them on his own and every site looked like a dead puppy soaked in ass juice).

My title changed from a peasant web dev to technical lead which meant shit. I was doing normal dev work + managing all projects. This basically meant that I had to show all junior devs (mostly interns) how to do their jobs. Client meetings, first point of contact for them, caring an "out of hours" support phone 24/7, new staff interviews, hiring, training and much more.

Unrealistic deadlines, stress and pulling hair were a norm as was taking the blame anytime something went wrong (which happened very often).

All of that would be fine with me if I was paid accordingly, treated with respect as a loyal part of the team but that of course wasn't the case.

But that wasn't the worst part about this job. The worst thing was the constant feeling that I'm falling behind, so far behind that I'll never be able to catch up. Being passionate about web development since I was a kid this was scaring the shit out of me. Said company of course didn't provide any training, time to learn or opportunities to progress.

After these 4 years I felt burnt out. Programming, once exciting became boring and stale. At this point I have started looking for a new job but looking at the requirements I was sure I ain't going anywhere. You see when I was busy hacking PHP CMSs, OOPHP became a thing and javascript exploded. In the little spare time I had I tried online courses but everyone knows it's not the same, doing a course and actually using certain technology in practice. Not going to mention that recruiters usually expect a number of years of experience using the technology/framework/language.

That was the moment I lost faith in my web dev future.

Happy to say though about a month later I did get a job in a great agency as a front end developer (it felt amazing to focus on one thing after all these years of "full-stack bullshit), got a decent salary (way more than I expected) and work with really amazing and creative people. I get almost too much time to learn new stuff and I got up to speed with the latest tech in a few weeks. I'm happy.

Advice? I don't really have any, but I guess never lose faith in yourself.

I was just a junior developer, and the senior interviewer had just left for a quick break.

And, I had to interview one dude for the post of Web Designer (we were not asking for experienced devs). And, then he comes up, opens his laptop, goes to a folder and opens an html file that turns out nothing but a "Save Page as.." of one News Website. Seriously, I just said nothing, asked him a bunch of questions and off he goes. I could not stop laughing later.

Senior Devs, what are your general expectations from a junior Dev at work?

Today was not a good day for me at all ,being considered a junior developer is not a good thing.
Yes I know due to my lack of the understanding of your 3 years old code base I could not meet up with the deadlines.
So as a punishment one of our senior devs asked me to bring my chair to his desk and told me to commit and push my progress every ten minutes .
He'll then review reading each code line by line ., Reverting too.
The worst part was that for the ten minutes I'll need to wait another 5 , because he was watching some Fifa19 gameplays on YouTube.
This went on for 3 hours .

It worked because I feel like a title noob today .

getting into dev work is such a shit show. thinking back 2 years ago I decided to switch career so went on bootcamp and starting looking for junior role.

as you know full well all jobs requires 5+ years when the tech has only been around 3. Anyhow, got a junior full stack role at a start up, all good , great pace (cos of startup) and wide range of tech to learn. one minute i am doing great , next day I am not good enough and got let go (WTF?) ,also whats up with some backend devs Jesus why wouldnt you let me put a " on aws because you are the backend dev what the fuck is wrong with your ego man?

fun story number 2: after being let go of my first role due to being good dev for one day and bad the next. I went for an intern role for really low paid. well fair enough I am here to learn right guys? nope, i have experience with the main tech from my last job and I managed the take home test and despite I told them i have more experience front end they criticise my backend code , despite i was able to tell them what I have done not so well and I have found a better solution AT THE INTERVIEW. still not good enough. I was really doubting myself If I am that shit at being an fucking intern with a stack I have experience in.

fast forward another job interview I landed my current role with fantastic culture, good line manager & tech lead. nice colleague and I am being treated like a prince with the work i put in. Why is this industry so fucked?

so, folks out there trying to get into this game. dont lose hope, you can do it , you just need to get fucked a bit to know whats good out there!

Diary of an insane lead dev: day 447

pdf thumbnails that the app generates are now in S3 instead of saved on disk.

when they were on disk, we would read them from disk into a stream and then create a stream response to the client that would then render the stream in the UI (hey, I didn't write it, I just had to support it)

one of my lazy ass junior devs jumps on modifying it before I can; his solution is to retrieve the file from the cloud now, convert the stream into a base64 encoded string, and then shove that string into an already bloated viewmodel coming from the server to be rendered in the UI.

i'm like "why on earth are you doing that? did you even test the result of this and notice that rendering those thumbnails now takes 3 times as long???"

jr: "I mean, it works doesn't it?"

seriously, if the image file is already hosted on the cloud, and you can programmatically determine its URL, why wouldn't you just throw that in the src attribute in your html tag and call it a day? why would you possibly think that the extra overhead of retrieving and converting the file before passing it off to the UI in an even larger payload than before would result in a good user experience for the client???

it took me all of 30 seconds to google and find out that AWS SDK has a method to GetPreSignedURL on a private file uploaded to s3 and you can set when it expires, and the application is dead at the end of the year.

JFC. I hate trying to reason with these fuckheads by saying "you are paid for you brain, fucking USE IT" because, clearly these code monkeys do not have brains.

Some ranters get pissed with junior dev who thinks unit testing is not necessary and a waste of time. While I'm here convincing all senior devs in my office why testing is important. I gave up.

Really fed up with my colleague and possibly my job. Am starting to doubt am cut out to be a developer

Am a junior java dev , been working working for this company for about 2 years now. Although they hired me to be a java dev, they pretty much exclusively had me working on JavaScript crap because none of the other more senior devs wanted to do even so much as poke JS with a long stick....

Oh and the salary was crap but i figured since i had barely 3 years of exp i thought i would stick with it for a while

But a few months ago after seeing other opportunities I got fed up and threatened to quit , already started interviewing etc
Got an offer, not exactly what i wanted but better than where i was. Went to quit but they freaked out and started throwing money at me. They matched and exceed the other salary and promised to addressed the issues that made me want to leave. Ie get me to work more on the java side of the project and have me work with someone more senior who could sort of mentor me, i had been working semi solo on the js shit till then...

The problem is that my supposed mentor is selfish prick... he is the sort of guy who comes in real early, basically he goes to early morning prayer then come in at some ungodly hour and fuckoff home around 3pm

He does all his work early morning then spends the rest of the day with his headphones on stealthily watching youtube, amazon, watching cricket, reading about Palestine , how oppressed muslims are or building a website for some mosque.

I asked him to let me sit with him so that I could just learn how this or that part of the sys worked , he agreed then the very next day comes in and does all the work before i get in at 9 , i asked him how he did it and he tells me oh just read the code.

Its not as simple as that, out codebase is an old pile of non standard legacy dog shit. Nothing works as it should, i tried to go through documentation online for the various stuff we use , but invariably get stuck when i try the usual approach because it turns out the original devs had essentially done a lot of custom hacks and cowboy coding to get stuff working, they screwed around with some of the framework jars & edited libraries to get stuff to work, resulting in some really weird OSGI errors.

My point is that i cant really just "read the code" or google ...
I gotta know a bit more what was actually modified and a lot of this knowledge isn't fucking documented, theres a lot of " ohhh that weird bug yeah yeah that happens cuz x did this hack some years ago to fix this issue and we kinda built on it, yeah we weren't supposed to do that but heyyy what u gonna do, just do this or that instead"

I was asked to set up a web service to export something, since thats his area of expertise and he is suppose to be teaching me the ropes, i asked him to explain where i should start and what would the general workflow be, his response is to tell me to just copy the IMPORT service and rename it to export then "just do it um change it or something" very helpful indeed (building enterprise application here nothing complex at all!!)

He sits right next to me so i can see how much works he actually does, i know when he just idly sitting there so thats when i ask him questions, he always has his earphones on so each time i gotta find a way to get his attention with a poke or a wave, he will give a heavy sigh and a weary look as he removes his headphones, listen to my question then give me the shortest answer possible before IMMEDIATELY turning away and putting his headphones on as fast as possible regardless of whether I actually understood or even heard what he said. If i ask another question ( am talking like an immediate follow up question for a clarification or something) he will
Do the whole sigh + tired look routing to make me know yeah you are disturbing me. ( god was so happy the day he accidentally sat on and broke them)

Yesterday i caught a glance at his screen as i was sitting down and i think he and another dev were talking about me
That am slow with my work and take forever to get into gear.

Starting to have doubts about my own ability n wether am really cut out to be a developer. I know i can work hard but its impossible to do so when you have no clue where to start and unable to look it up since all the custom hacks doesn't really allow any frame of reference.
Feels like am being handicapped and mocked, yesterday i just picked up my gear n left the office.

I never talk ill about my colleagues, whenever i have a 121 with my mgr i always all is fine, x n y are really helpful etc
I tried to indirectly tell my other colleague about this guy, he told me that guy had kinda mentally checked out of this job and was just going through on auto pilot and just laughed it off (they have been working together for almost a decade and a buddies) my other colleague is pretty nice but he usually swamped with work so i feel bad to trouble him.

Am really Fed up with it all

I (senior dev) just went out with colleagues from work. We started drinking what eventually led to some dancing and partying. After a lot of drinks one of the junior/intermediate devs told me that he was surprised i am not a conservative bourgeois like he supposed i am based on his work-experience with me and that he can have actually have fun with me.

MAN I AM FUCKING SORRY THAT I AM PROFESSIONELL AND THAT I DISTINGUISH BETWEEN MY PRIVATE AND MY PROFESSIONAL LIVE!

A useful guide of general rules for junior devs, while asking questions to senior devs.

1) If you're a junior dev, you're going to not know stuff. A lot of stuff. That's perfectly fine and expected. The more you realise you don't know, the more you move forward.

2) If you don't know something, duckduckgo it. If after at least 1 hour and a max of 2 hours of searching you still don't get it, ask someone.

3) If the senior dev just gives the answer directly, it means they think you should've already known the answer.

4) If the senior dev just gives the reasoning behind it, but not the answer, it means you should know most of it, but you can probably arrive at the answer with a bit more reasoning and it's a unique problem.

5) If the senior dev gives you the answer with an explanation, it's a very good question and you will likely get to learn something you didn't know already.

Replace senior dev with stack overflow and it still works the same.

When junior devs “fixes” the legacy defect...

Fml... you keep getting the weekly discussions right on point.

I started with the last guys right out of university... just out of Hospital.

With a brand new degree and a Crohn’s diagnosis I stepped into the first place I found hiring. They were good guys, after a junior dev... to get stuck in their muck.

I did! I nailed project after project, tricky development after tricky development. I spent 5 years with them and over those years things changed.

They had a mass cull... the original idea was to get rid of the useless middle managers, the ones managing other managers being managed by another manager for no real reason.... the ones that do fuck all with their day.

But the fucking idiots upstairs put the job of working out the cull in the shitty middle managers hands.

So, instead, they cut the titles senior, junior and everything in between. Everyone was just a thing, no senior things, no junior things. Just things.

Once they’d done that they said “we’ll we have this many things, they’re all the same, let’s get rid of the things with the highest pay checks because the other things can do it just as well for less money”...

And that’s how they cut 50% of their senior techs.

I was one of the ones left behind but the damage became obvious quick. The middle managers barked out orders at people who couldn’t complete them, and everything went to shit.

My team was rebranded twice in as many years... an obvious ploy for funding, but the cost of the team fluctuated like hell because contractors had to fill the senior positions at 3 times the cost.

Then the managers started barking out Self contradictory orders. Do this, but this way...

This would work, but not that way... try explaining that to a group of non-technical, useless as fuck middle managers. It took months, and shit flows downstream so we got the bulk of the hassle for it.

Then my boy Morpheus, got a warning... they threatened his contract for saying “this will work, but not that way”.

He kept the contract, and the manager giving him the warning said he didn’t think he should... but he, and all the middle fuckwits don’t have the balls to stand up against nonsense.

That was the breaking point for me, I handed in my notice and told them a month was what they could have.

I didn’t have a position or an idea of where to go, a few long-standing offers as back up in a pinch but not the perfect job.

On the Thursday I decided I was done, I let my manager know. Then I boshed the fuck out of my CV and updated my profiles.

My phone started ringing off the hook, a senior NG2/MEAN/Ionic dev on the market is like candy to recruiters. They’re lovely too.

I went to a few interviews that were okay but not great. Then a company got in touch... one that I immediately recognised as an IT book publisher. They said they were looking for NG/NG2 devs, senior. winner! Set up the interview.

So I’d spent the weekend with the missus, about an hour away from mine and 2 from the interview. I hadn’t planned on staying there but at 6ish she looked over at me and said “do you have to go” <- imagine that with puppy dog eyes from a gorgeous Slovenian lass.

I folded quicker than a shitty pancake toss.

We spent the night together but that meant I had to be up at 6, to go back to mine, iron my interview clothes and make it to the train to manage the interview. Fuck. I did it, but I was at the interview wired on caffeine and struggling to be awake and coherent. I still managed, that’s what I do, I make do and try to do well regardless of the situation.

That comes from being ill btw, when you’re dealt a shitty hand you learn to play it well.

They were good guys, the heads all knew what they were on about, not the middle management bs I was used to.

They demoed me live with an ng1 test, which was awesome as hell to play with.

We chatted, friendly and cool guys! I loved the place.

The end of the week they got me in for second round. Ng2 and competence test, again I went for it!

Positive feedback and a “we’ll get back to you ASAP, should be by Tuesday”...

Tuesday was the Tuesday before the Friday I was due to leave the old company... I was cutting it close.

On the Monday the offers started rolling in, a few C# ASP MVC positions, cool but I was holding out for the guys I’d interviewed with.

Then Tuesday comes around, I’m nervous as fuck but it’s okay because I knew regardless I can pay the rent in December with one of the offers.

Then said yes!

The thing that seemed most important in the process was my ability to talk to any fucker. If you’re coming up to interview, talk to everyone, the grocer, your barista, the binmen, anyone. Practice that skill above all others.

I start tomorrow morning! I can’t wait.

Final thought: middle managers are taints.

Did you ever feel like mad rage for the junior devs when they blame you for their failures?

TL;DR: Stop using React for EVERYTHING. It's not the end-all solution to every application need.

My team is staffed about 50/50 with tenured devs, and junior devs who have never written a full application and don't understand the specific benefits of different libraries/framworks. As a result, most of these junior devs have jumped on the React train, and they're under the impression that React is the end-all answer to any possible application need. Doesn't matter what type of app is, what kind of data is going to be flowing through the app, data scale, etc. In their eyes, React is always the answer. Now, while I'm not a big fan of React myself, I will say that it does its job when its tasked with a data-heavy application that needs to be refreshed/re-rendered dynamically and frequently (like Facebook.) However, my main gripe is that some people insist on using it for EVERYTHING. They refuse to acknowledge that there can be better library/framework choices (Angular, Vue, or even straight jQuery,) and they refuse to learn any other frameworks. You can hit them with countless technical reasons as to why React isn't a good choice for a particular application, and they'll just spout off the same tidbits from the "ReactJS Makes My Nips Hard 101" handbook: "React is the future," "Component-based web architecture is the future," (I'm not arguing with that last one) "But...JSX bro.," "Facebook and Netflix use it, so that's how you know it's amazing." They'll use React for a simple app, and make it overly-complex, and take months to write something that should have taken them a week. For example, we have one dev who has never used any other frameworks/libraries apart from React, and he used React (via create-react-app) to write what is effectively a single form and a content widget inside of a bootstrap template. It took him 4 MONTHS to write this, and it still isn't fully functioning. The search functionality doesn't really work (in fact, it's just array filtering,) and wont return any results if you search for the first word in an entry. His repo is a mess, filled with a bunch of useless files that were bootstrap'd in via create-react-app. We've built apps like this in a week in the past using different libraries/frameworks, and he could have done the same if he didn't overly-complicate the project by insisting on using React. If your app is essentially a dynamic form, you don’t need a freaking virtual DOM.

This happens every time a big new framework hits the scene. New young developers get sucked into it, because it's the cool hip new framework (or in React's case, library.) and they use it for everything, even when it's not the best choice. It happened with Angular, Rails, and now it's happening with React.

React has its benefits, but please please please consider which library/framework is the best choice from a technical standpoint before immediately jumping on the React train because "Facebook uses it bro."

So at this startup i was single iOS dude age 34, android had 1.5 dudes, one older, one you ger. That 0.5 younger was tech director, really good, so they churned for two guys. Millenial, nice guy, never making conflict, just being sleazebag.

Nobody explained to boss why iOS was always late with features, even when i complained. So i got help, 10 months later, project was unpolished but stable, codewise. Now i interview and hire a guy, age 27, who was all yeah dude no problem, and that being my first interview, i fell under his friendly appearance. I ignored a fact that he didn’t know 90% of stuff i was asking him, because he was so friendly and outgoing and we will do anything attitude.

The guy knew very little, was childish and irresponisble. He showed at work at noon. He started telling me what to do, his senior collegue who started the project. He argued about everything that i would tell him. So i spent three to four hours a day charting with him, because we were in different cities. He had two uears of experence, but he was below junior level. And he refused any of my advices for learning in free time. No, he said, thats my free time, you will not tell me what to do. Well, how do you plan on being better, i asked. He said, i learn by doing. But, since he was at his job only six hours a day, instead of eight, and since he was productive only for 2, i guess he was lazy.
He would deliver a UI he would make, without business logic, and tell it is done. Then clients would call me and ask why text fields are not saved..

This all took me month to understand. I lost time, i lost trust, and soon he was fired.

But, soon i was fired also, replaced by another two devs who i had interviewd and formed a team. I was discarded as trash, just like that. I have even worked overtime to catch up with android guys, unpaid.

Took me year to recover mentally from this.

Lessons learned: be objective when interviewing. Job is business, not friendship, trust no one, keep neutral on work. Leave honesty for someone else, honesty will be used against you. Never criticize two girls in office who disturb developers by talking about sex and dicks all the time, dressed sexy, they are girlfriends of people ranked above you. Leave code perfection for your projects.

During the majority of my career, I've been the stereotypical pissed off guy with earphones in mashing away at his keyboard.

During lunch hours, I absolutely love listening to other pissed off devs. Their tales of buggy Microsoft products, oblivious project managers, dangerously unqualified directors, and severely disabled bosses are often the only thing that put a smile on my face in a workday, and here in Tokyo a workday is often your whole day. I don't feel there's anything wrong with it - the targets of their abuse often really are leeching tons of money while contributing little to nothing, so I feel like they deserve the abuse.

However, I don't like it when devs trash-talk other devs. I sympathize with those guys, even if they wrote bad code. I know writing good code is really, really hard, and I know that they were trying to do it under extremely difficult circumstances (in an office). If they're junior I sympathize even more because they're often better than I was when I had the same amount of experience.

So in conclusion, don't hate your fellow dev. Don't let hatred control you and poison your well-being. Direct your hatred where it belongs, at project managers.

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.

Ok, so I already asked when junior is no longer a junior..got mixed answers. Now I'd like to know what defines seniority level in your country?! Years of experience, having wide range of knowledge, great leadership skills, having boobs (joke).. ?!? But seriously, I have no clue what the standards in my country are, and internet is full of different opinions & examples that are making me wanna go cry in a corner.. o.O

Figured some answers from real people might help me get my head around this, so if it's not too much to ask fellow devs here, please answer this questions to help me grasp this better with examples..& non dev folks, you are welcome to comment too!!

A) What country are you guys from?
B) How is seniority defined there?
C) How are you placed by others?
D) If different, where would you place yourselves? Why?

It's killing me.

This senior keeps doing all his fixes in the the same branch (named "develop-copy-{hisname}") and keeps merging it directly into develop and deployment branches. He has a lot of experience and therefore the manager gave him direct access to the branch.

The problem will arise when the QA team sends back one of the issues in the release back for changes. This never happened till date (his fixes are early and we vet all in-team changes, therefore he gets time to clean up his mess before the release date) but someday this will bite us in the ass.

I'm really unsure about ratting him out to the manager but I couldn't convince him to use separate branches (or separate commits) for different fixes. I couldn't convince him to add JIRA links/numbers into the commit messages either.

And, the junior devs I manage are getting inspired by him, and won't listen to me when I try to enforce separate branches, creating a political mess (probably I'm kinda like a contractor and they are permanent employees).

Sucks.

Bad dev habit: Approving junior devs PRs into master without really looking them over.

It finally happened. One of our junior devs pushed a secrets file to their git branch and now I have to reset ALL THEIR CREDENTIALS. "git add ." will be the death of me.

Starting to develop a phobia of asking for help from senior devs since I can now sense their face-palm whenever I open my mouth.

Maybe I'm not ready to work as a junior dev yet...

It might be a stupid question, but:
Do the full-stack devs of you actually have that function in the job contract or does it just say "(junior/senior) software developer"?

Mine says just "Software Developer" and in my opinion it sounds just too generic and undervalued for what I'm actually doing...

​I'm a junior dev in a scrum team with two senior devs: one actual senior and one average dev that's just been around for a long time. At stand up meeting, that average senior lists helping me as one of his task Every Single Day. 9 out of 10 times when I ask him a question we end up asking the senior senior together.

From a life of a junior developer...
Got assigned one task for a 2 week sprint. 'Finished' it in 3 day, not actually sure it's finished as all the other devs are too busy to look at the pull request. So here I am... Ranting away and being bored

Junior devs PR -

line 98: Catches FileNotFoundException.

line 99: Immediately throws FileNotFoundException

--

CHANGE REQUESTED 🤦🏻‍♂️

Real question here.

Do you feel like you're being paid enough?

If you're senior devs, did you also get paid enough when you were a junior?

How do you guys/girls explain to potential new customers that you can perfectly work in a structured business environment and follow the rules, but also that you're assertive enough to oppose desicions being made based on bias, misunderstanding, fanboyism, or grave stupidity.

I just got informed from a freelance position that they would have hired me if it were not for my 'rebellious nature towards customers'

I don't oppose customers, i oppose stupidity unfounded.
Example from experience
> me working in a helodesk support position, all windows computer.
> new mgr comes into office, is a douche and complete mac fanboy
> wants all computers that are FINALLY working decent for some time in the entire department replaced with mac's... Back at 2010.
> whole team, even disliking microsoft themselves, are telling mgr that's a bad, dangerously dumb idea, expensive too, different OS, different software mgmt making, back then integration microsoft and apple was beyond diarhea... Several other issues the senior devs and admins pointed out

>mgr: 'but aple is soh much better, like a billion times better, hurrduurrrrr'
His decision passed somehow to the board..
> All stations from our customers get changed...we don't get a single machine to try out problems because overspending
> we are most of the time unable to help out customers because we still have pc's...
> mgr asks team why performance drops after 1 month
> we compared performance graph with his starting date of mgr, see clear drop after mgr's plan implemented...
> board stilll stands by mgr, gets praise for 'bold changes in the company', but appears to be some associate's son
> two main seniors leave after 15 years of employment, in three months, 80% of staff leaves.
> we canr fix the problems, we are not dev's , we get shit from all sides, i was still a junior in the industry so i worked as a slave inside that job.
> eventually get fired due to 'bad performance'
> mgr loses entire team... 'Hey why don't we outsource this dept to south africa, it's a lot cheaper! '

now that company is an it hellhouse where everyone get clinically depressed from sitting atbtheir station...
This is what i wish to oppose!

How to make that clear!

Just had a junior/mid dev who worked in our company for around 3 months quit because in his words "he is unable to win any argument".

I saw his comments in MR's and other seniors were just being meticulous. Had he compromised a little or atleast got to knew the devs in person and took this offline most of his problems would have been resolved. Never scheduled any meetings before implementing stuff, he just followed his gut and then shot himself in the foot plenty of times.

Personally I think it wasnt even a skill issue but a communication issue. We have a relaxed culture where u can work in the office or fully remotely so the guy came in on his first day, picked up his laptop and we never saw him. Tried to invite him for an afterwork beer or some activities, he never accepted.

If he had met the devs in person he would have seen that:

1. One guy has OCD and he never agrees with anyone but if theres a timeline hes able to make compromises and hes actually chill
2. Second guy is also a perfectionist but has mentor capabilities and you can always go to him about anything and he helps to mediate with the first guy. You can run everything through this guy and he will never give you shit
3. Third guy in the team is just a junior hotshot whos a bit insecure and disagrees in comments just because he can. But he can be dealt with very quickly with showing a little backbone.

Like seriously these are just people that you can deal very easily when u know their personalities. Instead he saw everyone in company as these 2D robots that he wasnt able to win his arguments against.

Communication shouldnt happen only in standups and MR comment section. U have to learn to deal with people otherwise u will burn urself out like this guy and quit.

Can't stand it when devs who never bother to do anything / don't pull their weight etc. suddenly come out with:

"Ooh I'm really feeling the imposter syndrome right now, I feel like everyone around me is just leagues ahead of me and I shouldn't be here"

...then wait for everyone to tell them how amazing they are, how they're a critical part of the team etc.

No mate, imposter syndrome is a thing, but so is being a genuine waste of everyone's time. I'm not talking about having bad days, I'm talking about your work output being practically zilch for the past half a year or so because you're "not too familiar with the framework", then going after this pity party approach. As a senior dev, it's kinda insulting to all the great junior and mid level devs who do a better job while being paid considerably less.

There's nothing that screams "junior" more than a graduate dev dressed up in a suit awkwardly posing for a LinkedIn photo.

Seriously, stop it, and stop listening to whoever tells you to don a suit so you're taken seriously. Maybe in marketing, HR or finance - but that's not how devs think, or hire people.

The day after I delivered a secure programming course to our junior devs.

Junior dev: I can't figure out what's happening when I generate this sql.

Me: what do you mean generating ... It should be a prepared statement..

Junior dev: no I'm just generating the strings from the form

Me: ... Let's try this again....

So....
I was asked to transfer a spaghetti Android/iOS project to xamarin for a bank client yesterday because "that's what they use".

This is a crm/loyalty app that has been around for 2+ years now (you can imagine the mess). On top of that I have no knowledge of c#, .net or xamarin.

So I ask: "When is this supposed to be delivered?"

Boss: "It was scheduled for 2 weeks ago but let's say 2 weeks from now"

Me: "..... This is a huge remake it won't be even close to ready in 2 weeks"

Boss: "Let's check on the progress in 2 weeks and see how it goes"

Why is it hard for bosses to provide an actual timeframe???

He's been pulling the same crap with junior devs for years and of course they get nervous and create more spaghetti code...

Anyway long story short (not) I have an interview Monday!

Let's hope it's not more of the same!

P.S.: to junior devs: When you are given a deadline... IGNORE IT.

!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.

How do you deal with massively poorly-performing and unknowledgeable teams?

For background, I've been in my current position for ~7 months now.

A new manager joined recently and he's just floored at the reality of the team.

I mean, a large portion of my interview (and his) was the existing manager explicitly warning about how much of a dumpster fire everything is.

But still, nothing prepares you for it.

We're talking things like:
- Sequential integer user ids that are passable as query string args to anonymous endpoints, thus enabling you to view the data read by that view *for any* user.
- God-like lookup tables that all manner of pieces of data are shoved into as a catch-all
- A continued focus on unnecessary stored procedures despite us being a Linq shop
- Complete lack of awareness of SOLID principles
- Actual FUD around the simplest of things like interfaces, inversion of control, dependency injection (and the list goes on).

I've been elevated into this sort of quasi-senior position (in all but title - and salary), and I find myself having to navigate a daily struggle of trying to not have an absolute shit fit every time I have to dive into the depths of some of the code.

Compounded onto that is the knowledge that most of the team are on comparable salaries (within a couple thousand) of mine, purely owing to length of service.

We're talking salaries for mid-senior level devs, for people that at market rates would command no more (if even close) than a junior rate.

The problem is that I'm aware of how bad things are, but then somehow I'm constantly surprised and confronted with ever more insane levels of shitfuckery, and... I'm getting tired.

It's been 7 months, I love the job, I'm working in the charity sector and I love the fact that the things I'm working on are directly improving people's lives, rather than lining some fintech fatcat's pockets.

I guess this was more a rant than a question, and also long time no see...

So my question is this:

- How do you deal with this?
- How do you go on without just dying inside every single day?

Are Junior devs meant to be put on solo projects or does my company just have a large expectation of us?

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.

Got fired today due to one big cunt who just joined to sabotage all junior devs because his older than all of us, im dissapointed at how arrogant some of you old devs are, the good old days development houses used to be fun and young, i respect all of you with great heart but we are not trying to compete with you if we know knew tech better than you, times have changed, if you are still dumb about bootstrap dont hate on anyone but yourself. Grow deFaQuPndStopHating

Junior devs who are unable to use Google and don't respect your headphones, brutally pulling you out of the zone. There's a special place in hell for these guys.

So after months of self study my company finally appoints me as a junior developer with a major client as the intermediate dev on the project resigned. My tech lead assures me that junior devs only fix bugs and do other minor changes. One week in and in our first sprint planning session the client decides to priorities a Major update to the app. Now I have 2 weeks to deliver what will either make or break my immediate career. And I have no idea how to implement any of the changes. Stack overflow you're my only hope (and many hrs of YouTube tutorials)

We spent 9 hours taking a vote, across all of the dev team (including junior devs), about how to design the backend architecture and which security measures we should take.

The CTO refused to listen to the person assigned to the design (me at the time) because he preferred fire-and-forget for EVERYTHING, ignoring all of the blatant drawbacks, and claimed that "there is no truly fault tolerant system", which is such a cop-out that my mind still cannot fathom it.

So therefore, since he couldn't have it his way, we took it to a vote (not my decision). Spent nine hours discussing the pros and cons of HTTP vs MQ systems to arrive at a vote.

I "won", and then left the company shortly after, because it was clear that even though the votes were in my favor, I was going to be "nickel and dimed" to death about the changes and how it's deployed, etc. to the point the system will end up like the previous systems they wrote.

Oh and the fact I was asked to help "improve morale" for the team that was working on the old, broken, overengineered project (I don't manage them nor did I write any of that code) by being assigned to arrange breakfast catering because it'd somehow mean more "coming from a senior dev".

I loved the people there - truly, some of the best people - but the company was broken from the ground to the ceiling.

CTO was let go a while after I left, I guess - most of the dev team has since left too and the majority of their work is being outsourced to Indian subcontractors.

So today I was offered a job at the company as a junior frontend developer. Digging a little deeper I found out that they don't have any other frontend devs in house.

So the job offer translated to:
- senior skillset
- senior workload
- junior wage

Best part is that I was freelancing for them in past and was helping to establish some of the workflow a year ago for more money they offered now.

Thanks, no thanks, I guess?

!rant

I see a lot of crap about junior vs senior devs nowadays. I think the distinctions are small.

In reality senior devs have been burnt more in the past by their own mistakes or have seen mistakes by other people. That's about it.

What other distinguishing characteristics have you found?

Do any other junior devs get secret joy when the architects and senior devs argue out on open?

why I say FUCK AI -

-> So much stupidity with "It will replace devs". Any dev who has more than 2 brain cells has had their issues with ChatGPT or AI knows that AI is not sufficient nor good enough to get even basic tasks done.

-> "It will be good in 5 years" - well then, talk to me after 5 years. I'm not buying a product or an idea on a "promise". I judge the tech for what it is today, not on what it can be in 5 years.

-> "Just trust me bro" - I see influencers suck that robot dick, but no explanations are given. What they say sounds to me like it's parroted off of general mass media. Nothing new to add nor any insight.

-> AI has issues that nobody seems to talk about. Hallucinations being the biggest of them all. ChatGPT tells you something, and you're supposed to take it as fact? That's too dangerous for a normal person.

-> Junior software developers are scared even to this day that AI can replace them. If they can't think for themselves, it falls upon us (or at least, me) to drive them in the correct direction or give them real opinions on what it is.

I am a junior web developer, currently working in my first job for a small company, I was hired because I have an interest in meteor and modern web dev.

When I say small I mean I am the only full time js dev.

So the project we are working (my first ever professional project from start to finish) is a travel booking web app (being a little vague, for the sake of privacy). I am the lead developer, as a new programmer of a project that is far from trivial. There are no other javascript devs in office, no sort of code review. We have an outsourced dev but as I got in a flow with one dev my boss supposedly told him to do it part time (without discussing with me), but haven't heard anything from him, so assuming he's just disappeared (probably annoyed at being treated like a commodity).

Boss has set up the stages, and forces me to move on to the next stage before that stage has been finished. I will have to go back over the whole thing to finish things off.

He will only hire cheap juniors, one front end guy with barely any experience is styling the site.

He is used to churning out WordPress and Magento sites.

Wish I had a senior I could learn off.

I want to stick at this project and see it through, but i can only see it ending in a train wreck.

At the same time I want out, I want to work under a better team with senior programmers and better code review.

I just have to do my best and see how it goes I guess

Hello senior devs.. . What happens if you screw up? I mean if a junior dev screws up, the senior helps.. right?

This was a long time ago, when I was an 18 year old junior dev in my first job and still studying at college part of the time.

The lead programmer saying things like “we [meaning the experienced devs] are alright if this project goes wrong but you need to prove that you can deliver because you could be out of a job”.
Thanks. Mofo set me right up for lasting confidence issues.

Less than two years later I was killing it when the language they used became object oriented. That asshole couldn’t understand any of the concepts.
That feeing of being out of my depth has lingered though.

If you're going to look for junior devs on facebook... make sure you don't try to be funny and write any kind of bullshit-code.. there is a f**king space in the function name! Dude....

Text says:
"Rieke Computersysteme is looking for you!

void send Application () { ... }"

The feeling when, as a junior dev, you realize the code base is a mess and learning from the senior devs is more accurately learning the preferences of the senior devs. There is no "right" way to do things.

Also, how did anyone get anything at scale with JS before typescript!?

A /thread.

I have to say something important. As the story progresses, the rage will keep fueling up and get more spicy. You should also feel your blood boil more. If not, that's because you're happy to be a slave.

This is a clusterfuck story. I'll come back and forth to some paragraphs to talk about more details and why everything, INCLUDING OUR DEVELOPER JOBS ARE A SCAM. we're getting USED as SLAVES because it's standardized AS NORMAL. IT IS EVERYTHING *BUT* NORMAL.

START:

As im watching the 2022 world cup i noticed something that has enraged me as a software engineer.

The camera has pointed to the crowd where there were old football players such as Rondinho, Kaka, old (fat) Ronaldo and other assholes i dont give a shit about.

These men are old (old for football) and therefore they dont play sports anymore.

These men don't do SHIT in their lives. They have retired at like 39 years old with MULTI MILLIONS OF DOLLARS IN THEIR BANK ACCOUNT.

And thats not all. despite of them not doing anything in life anymore, THEY ARE STILL EARNING MILLIONS AND MILLIONS OF DOLLARS PER MONTH. FOR WHAT?????

While i as a backend software engineer get used as a slave to do extreme and hard as SHIT jobs for slave salary.

500-600$ MAX PER MONTH is for junior BACKEND engineers! By the law of my country software businesses are not allowed to pay less than $500 for IT jobs. If thats for backend, imagine how much lower is for frontend? I'll tell you cause i used to be a frontend dev in 2016: $200-400 PER MONTH IS FOR FRONTEND DEVELOPERS.

A BACKEND SOFTWARE ENGINEER with at least 7-9 years of professional experience, is allowed to have $1000-2000 PER MONTH

In my country, if you want to have a salary of MORE THAN $3000/Month as SOFTWARE ENGINEER, you have to have a minimum of Master's Degree and in some cases a required PhD!!!!!!

Are you fucking kidding me?

Also. (Btw i have a BSc comp. sci. Degree from a valuable university) I have taken a SHIT ton of interviews. NOT ONE OF THEM HAVE ASKED ME IF I HAVE A DEGREE. NO ONE. All HRs and lead Devs have asked me about myself, what i want to learn and about my past dev experience, projects i worked on etc so they can approximate my knowledge complexity.

EVEN TOPTAL! Their HR NEVER asked me about my fycking degree because no one gives a SHIT about your fucking degree. Do you know how can you tell if someone has a degree? THEY'LL FUCKING TELL YOU THEY HAVE A DEGREE! LMAO! It was all a Fucking scam designed by the Matrix to enslave you and mentally break you. Besides wasting your Fucking time.

This means that companies put degree requirement in job post just to follow formal procedures, but in reality NO ONE GIVES A SHIT ABOUT IT. NOOBOODYYY.

ALSO: I GRADUATED AND I STILL DID NOT RECEIVE MY DEGREE PAPER BECAUSE THEY NEED AT LEAST 6 MONTHS TO MAKE IT. SOME PEOPLE EVEN WAITED 2 YEARS. A FRIEND OF MINE WHO GRADUATED IN FEBRUARY 2022, STILL DIDNT RECEIVE HIS DEGREE TODAY IN DECEMBER 2022. ALL THEY CAN DO IS PRINT YOU A PAPER TO CONFIRM THAT I DO HAVE A DEGREE AS PROOF TO COMPANIES WHO HIRE ME. WHAT THE FUCK ARE THEY MAKING FOR SO LONG, DIAMONDS???

are you fucking kidding me? You fucking bitch. The sole paper i can use to wipe my asshole with that they call a DEGREE, at the end I CANT EVEN HAVE IT???

Fuck You.

This system that values how much BULLSHIT you can memorize for short term, is called "EDUCATION", NOT "MEMORIZATION" System.

Think about it. Don't believe be? Are you one of those nerds with A+ grades who loves school and defends this education system? Here I'll fuck you with a single question: if i gave you a task to solve from linear algebra, or math analysis, probabilistics and statistics, physics, or theory, or a task to write ASM code, would you know how to do it? No you won't. Because you "learned" that months or years ago. You don't know shit. CHECK MATE. You can answer those questions by googling. Even the most experienced software engineers still use google. ALL of friends with A+ grades always answered "i dont know" or "i dont remember". HOW IF YOU PASSED IT WITH A+ 6 DAYS AGO? If so, WHY THE FUCK ARE WE WASTING YEARS OF AN ALREADY SHORT HUMAN LIFE TO TEMPORARILY MEMORIZE GARBAGE? WHY DONT WE LEARN THAT PROCESS THROUGH WORKING ON PRACTICAL PROJECTS??? WOULDNT YOU AGREE THATS A BETTER SOLUTION, YOU MOTHERFUCKER BITCH ASS SLAVE SUCKA???

Im can't even afford to buy my First fuckinf Car with this slave salary. Inflation is up so much that 1 bag of BASIC groceries from Walmart costs $100. IF BASIC GROCERIES ARE $100, HOW DO I LIVE WITH $500-600/MONTH IF I HAVE OTHER EXPENSES?

Now, back to slavery. Here's what i learned.

1800s: slaves are directly forced to work in exchange for food to survive.

2000s: slaves are indirectly forced to work in exchange for money as a MIDDLEMAN that can be used to buy food to survive.

????

This means: slavery has not gone anywhere. Slavery has just evolved. And you're fine with it.

Will post part 2 later.

Let me begin by saying I knew the jist of the announcment before even reading the CeO's LeTteR... though it's comically and ironically far worse than I could have even expected

this is absolutely an 100% genuine rant from the bottom of my heart

Just go absolutely fuck yourself, your devs, and your entire org. Imma call it right now and say Udemy as a company won't be around in a mere 10 years. (easy to say this actually; the average lifetime of a company in general on the stock market is 18 years, with a garbage shit pile like Udemy i can guarantee its less than that)

oh, but their stock was up 38% on friday on good earnings... wonder how they did that

"But why!?!?!? Why are all creators going to tiktok and youtube?!?!?" - Udemy CEO mouthbreather

stupid fuck, maybe take a lesson from a 1st grader and get educated

people think devs are bad? Oh, its about to get a whole lot worse. there's no motivation anymore for skilled devs to build valuable courses, more and more junior devs using outdated spit out shit information from IdiotGPT, and a destruction of number of people on stackoverflow, asking the same 10 questions over and over again...

oh how the times have changed...

Another rant reminded me:

I’ve been at the same company for almost five years now, and I’ve seen the dev teams grow: several juniors come in, and even a few that left - or more precisely, was let go. And for each of those that were let go, the root issue with them was always the same: not the lack of skills or ability to learn their trade at job, no. It was always communication issues serious enough to render working with them impossible.

So remember juniors, besides googling and problem solving, the most important skill to master in team-based dev envs is COMMUNICATION. You need to fucking be part of the team or you’re out, no matter how good you are technically. If that’s too hard, either this is the wrong line of work for you or you need to just go solo. It’s that simple, boys, girls, and everyone else on the spectrum.

I don't understand some job ads. The companies want developers with 3+ years of experience in everything for entry level positions.

Aren't there any entry level positions for entry level developers with less experience?

If this is the norm, how do junior devs get the experience they need to be qualified for these "entry level" positions?

Who doesn't love it when you get rejected from a junior position because of missing knowledge. Apparently it's normal that junior software devs who just finished their training have extensive knowledge in Microsoft server and cloud architecture.

do all the IT Companies want to hire us as senior devs & pay as junior? Or it is just my country?

Was very sick today.
Hopped over to work virtually so I can help with an issue holding up prod release.
Felt pretty awesome about the whole deal.

Than realized three things:

1- this was a bad example to junior devs.
2- stole learning experience from other devs
3- I am leaving this company. I should have allowed the weaning process to start

any advice for a junior dev that can't get any fucking help from the senior devs? I can only in good-conscience try to solve a problem for so long before I know I'm seriously wasting my time

when I ask for help I often get "I'll get to your question in two or three days"

like damn I'm pretty stuck here guy

What exactly is a junior developer?

I mean what it depends on?

I ask because some colleagues have told I'm not junior but I have a junior role at my company

I don't even care and I don't like these classifications of devs but when someone asks me if I'm junior I actually don't know what to answer

I thought it was getting crazy when I read about ninja developer role but let's not talk about it

PS: I have been coding for 5 years now if it matters

Obligatory subjective view from inexperienced eyes of a highschooler

I think it's evolving to be more beginner-friendly and more easily accessible. I'm seeing ppl roughly my age can program pretty well (ignoring the mandatory programming classes in highschool that stuff is just no (I know, we had this convo before but do hear me out, although it teaches fundamental programming in Pascal, the execution sucks ball because "mandatory")). I'm not saying we are on par with the in-industry devs, it's just we can code well enough to at least make decent small program/script.

With newer scripting languages that are easy to pick up and syntactically similar to English which is obviously Python, both objectively and subjectively, and its ability to be OOP without scaring first-timers of the what-the-blyn-is-this blank program (looking at you C#) people can be introduced to programming and programming concepts fairly easily and they can switch from Py to other languages with little to some hiccups, from my personal exp at least.

But then there's the "too much kiddies in the field" arguments I saw on dR (I think) a while back then when SO decided to better support newbies. To that, I can only say "Please give us a chance". We're completely oblivious to how the dev world work nor how you guys do your work so before you scold us on this, at least tell us how to work like you before you go on a 2-A4-page rant on how the industry is not as good as before and how it has degraded.

That leads to the problems of politics invading programming. We have it, I hate it, goddammit I wanna murder them. Linux CoC controversy is just...no. And then there's forced diversity in hiring (also ranted on dR a while back) and corporations pissing devs off to satisfy a minor group. I'll just shut up on this. No no no no no no no NO I'm not gonna. Not gonna.

Do correct me if I'm wrong though. I'm a less than a junior dev.

Fuck start ups with large projects with no continous integration setup on git... and very many junior devs including the CTO(Not even a googling guru).... for fucks sake we cant deliver spaghettis as iF we are coding a restauRANT... fuck this shit load of a project....

We have pretty fast and lean dev process between QA/Design/Devs.

But sometimes, it's going to shit ;p

QA :
An option "ROLE" is missing for grouping in that table.
So 5 min to create ticket, assign someone from design on it

Design : Yeah, this is true. We missed that option in our design.
Proceds to modift figma by adding an option "Role" to a drop down.

Reasigned to Junior dev.

Junior dev : I have no clue how grouping works with graphql.

So at least 30 min.

Reasigned to me.

Me after 1 min of looking at it : PR chhanges on screen shot :

Facepalm... Everyhtibng was already in place, someone forgot to add id AND name, not just name.

Git blame => Or never mind... it was me..

Apple Music is the worst music service I've ever used.
By far the worst UI/UX ever.
It doesn't allow me to easily organize my music the way I want.
Search is sluggish.
The recommendation algorithm sucks.
Can't LIKE a song without it asking me to also sync my local music files to the cloud. Seriously, why the fuck can't I like/favorite a song and be done with it? Why does it need to sync with my local files?
This is a basic feature that works in literally on any other music platform.
The damn thing can't even play FLAC.

I know Spotify has its issues, but it actualls feels like a well engineered piece of software.
Apple Music seems like it was made by junior devs for a school science fair.

The only thing going for Apple Music is the sound quality, everything else is bullshit.

Today one of the more junior back-end devs told us, that he doesn’t plan to do front-end, because he doesn’t want to make design.

He basically told us that in his view FE devs do design work and that’s it.

What the f**? We have designers for that. Front-end devs are not the ones who make design. Reaaad uupp, boy

I use to work with a lot of people from all around the world, so i can say from the very first meeting if you are a good dev or not, and darn ! i hate the self confident devs who think they are the best, especially when they are junior !
I want to tell them : WAKE UP ! YOU ARE NOT THE ONLY ONE IN THE WORLD !!

Why things are fucking hard when you're not too good and not too bad at work. I'm like normal dev just throw things at me give me any task any framework I will learn it, I will solve production issues, I will help my co-workers to get their shit done even my JIRA is clean but it feels like I'm going nowhere. I'm like an average guy who knows many things other than normal guys or devs (by considering I'm junior and the people who are working with me).

I'm feeling like I'm in a fucking loop, where every day is same.
Is there anything I can do? which will make me feel little better?
I think every guy on earth have some innovative ideas even I have some(of course some of them are implemented already even they are kinda same, even some ideas are totally new, some are not possible, some requires much knowledge of certain field). But by just having an awesome idea doesn't change anything.

Maybe I'm not trying hard, there are several other reasons which are coming in my way but of course, I shouldn't tell any reasons.

My companies org is in a serious state of disrepair when it comes to project management.

Everything is tracked via conference. Each level of management (CTO, EVP, SVP, BP, S DIRECTOR, DIRECTOR, S MANAGER, MANAGER) all have a different tracking page that all say slightly different things.

To organize things there's a technical project manager who isn't just new to the team, he's new to the field. He's not technical, or experienced in project management. He's never worked within a scrum before.

He's dictating how to organize the teams scrum, and he's getting it very wrong. Decided to organize efforts in all the confluence pages by creating another one for him, again it's different.

When the work in confluence page 3/16 isn't done by a due date anybody knew about, the engineers have to hop on a call and get a Micky mouse solution out the door by the of day so upper management doesn't think the projects off the rails.

In the mean time I've taken a small group of more junior devs and shielding them. We have a side scrum that we manage and is going great, and I'm blocking the BS.

CORPORATE SUCKS. Golden handcuffs are a thing. I might set sail for greener pastures once i don't have to pay back my signing bonus if I leave.

PM here. I'm having an interview with prospective junior devs next week. I want to make sure that they know a little and can learn a lot. Do you guys have any suggestions of how to ascertain that? I'm thinking simple programming exercises or something.

Again, it's not that important what they know today.

Joined a new startup as a remote dev, feeling a bit micromanaged. So this week I joined an established startup as a senior mobile dev where I work remotely.

Previous two devs got fired and two new guys got hired (me as a senior dev and another senior dev as a teamlead, also third senior dev will join next week).

Situation is that codebase is really crappy (they invested 4 years developing the android app which hasn't even been released yet). It seems that previous devs were piggybacking on old architecture and didn't bother to update anything, looking at their GIT output I could tell that they were working at 20-30% capacity and just accepting each other MR's usually with no comments meaning no actual code reviews. So codebase already is outdated and has lots of technical debt. Anyways, I like the challenges so a crappy codebase is not really a problem.

Problem is that management seems to be shitting bricks now and because they got burned by devs who treated this as a freelance gig (Im talking taking 8-10 weeks pto in a given year, lots of questionable sick leaves and skipping half of the meetings) now after management fired them it seems that they are changing their strategy into micro managament and want to roll this app out into production in the next 3 months or so lol. I started seeing redflags, for example:

1. Saw VP's slack announcement where he is urging devs to push code everyday. I'm a senior dev and I push code only when I'm ready and I have at least a proof of concept that's working. Not a big fan of pushing draft work daily that is in in progress and have to deal with nitpicky comments on stuff that is not ready yet. This was never a problem in 4-5 other jobs I worked in over the years.

2. Senior dev who's assigned as the teamlead on my team has been working for 1 month and I can already see that he hates the codebase, doesn't plan on coding too much himself and seems like he plans on just sitting in meetings and micromanaging me and other dev who will join soon. For example everyday he is asking me on how I am doing and I have to report this to him + in a separate daily meeting with him and product. Feels weird.

3. Same senior dev/teamlead had a child born yesterday. While his wife was in hospital the guy rushed home to join all work meetings and to work on the project. Even today he seems to be working. That screams to me like a major redflag, how will he be able to balance his teamlead position and his family life? Why management didn't tell him to just take a few days off? He told me himself he is a senior dev who helped other devs out, but never was in an actual lead position. I'm starting to doubt if he will be able to handle this properly and set proper boundaries so that management wouldn't impact mental health.

Right now this is only my 1st week. They didn't even have a proper backend documentation. Not a problem. I installed their iOS app which is released and intercepted the traffic so I know how backend works so I can implement it in android app now.

My point is that I'm not a child who needs hand holding. I already took on 2 tickets and gonna push an MR with fixes. This is my first week guys. In more corporate companies people sit 2 months just reading documentation and are not expected to be useful for first few months. All I want is for management to fuckoff and let me do my thing. I already join daily standup, respond to my teamlead daily and I ping people if I need something. I take on responsibility and I deliver.

How to handle this situation? I think maybe I came off as too humble in the interview or something, but basically I feel like I'm being treated like a junior or something. I think I need to deliver a few times and establish some firm boundaries here.

In all workplaces where I worked I was trusted and given freedom. I feel like if they continue treating me like a junior/mid workhorse who needs to be micromanaged I will just start interviewing for other places soon.

I just completed my college degree in may of this year and started working in a small company of <50 employees. I'm made to sit idle all day because I'm a junior and also because they dont have much shit going on.
I approached my head a few days back to discuss the same and he says that it's my responsibility to ask my senior devs to keep me busy and assign me work.
Now do I really have to suck my seniors dick everyday to make him assign me something?
Plus this asshole made the head believe that I'm not competent enough and that's the reason they're soft ignoring me, whereas I always did everything up-to his standards and then he even sometimes appreciated me for that.

Now the real question, if I leave this company and they give me a bad review, will it have a considerable impact on my future? I'm confused as fuck. 😐

TL;DR: Newly joined fresher, made to sit idle in the company, company guys somehow make it seem it's my fault for being idle, may give me a bad review when I leave, will it make me look bad?

Companies are laying workers off these days like it's nothing.

My company dismissed (just within my department) 90 out of 129 workers — that messed me up.

However, though, my team experienced just a partial effect: 2 Senior devs are needed out of 3 — mid and junior devs are going. I literally had to re-interview for my role again, since they need to keep only 2 senior engineers.

To cut the long story short, I was the first selected candidate — grateful I still have my job. But, I'm sad to see the disruption.

I understand that at the end of the day, it's all business, but mehnnn ...

Is anyone going through the same thing here?
How y'all coping?

One of new junior devs after his 3 month "trial period" was good enough to keep him so he went to boss to talk about his future.

He came back with big smile and told us how much of big raise he got (now earning as much as seniors)

I asked my boss what was so special about him, maybe we should improve somehow, he answered "He was yelling at me, what could I do?"

Now I know how to approach him next time I talk about a raise :p

What do you think about having a portfolio website for junior devs? Does it help, does it not? How could I promote mine?

I had literally JUST learned to code, after completing an online course. I had played around making some tiny C# programs was looking for my first Junior job. A recruiter got in touch and to him I sounded like I knew what I was talking about. So he contacted the employer, called me back me later on and said that the employer wanted to see some sample code of mine.
"Sure!" I said eagerly and pasted my programs into an email. My two programs were probably about 20 lines of code in total - both Console apps. One was a stopwatch which I "hadn't quite got working yet", the other a Quadratic Equation solver.
The response came back that I was "too Junior for the position".
I know we all have to start somewhere, but I painfully cringe when I think about this employer and probably alll the devs there crowding around his monitor, pissing themselves at my tiny programs.

A see a lot of ppl talking about shit junior devs do, this is good lets me know wat not to do

Had junior devs work on a new feature on a project I spent days fixing. They spent days on the new feature but built it off of the broken version of the project and never pulled from the repository. Now when I merged their new feature onto the working and correct branch, their feature is all broken. I swear Im going to kill them all.

One of the most inefficient practices I've seen done in companies is the company housing 50+ devs having to hire an expensive consultant who is only available on a limited time to figure out mysterious or in-depth problems with the company's main application (for example, JavaScript problems).

Then the whole dev team sits on his shoulders and production can't run smoothly until he fixes things. Even worse, him having the so-called qualifications, being the 'expert', but when asked an in-depth JavaScript question, they don't know the answer.
When I suggest to figure out things in-depth so problems like these can be prevented in the future, I'm met with: "Nah bro, we'll just apply quick fix #2" just because I carry the title 'Junior Developer'. Makes me want to hit my head on the wall on how stupid these people are.

This could all be solved if the dev team would be competent in the first place, knows how to read documentation and isn't lazy, most importantly. I hate teams like that.
Grab, the damn, documentation, read W3C, read MDN, get educated, and stop using band-aid solutions! Gah.
Toxic companies like these are what's wrong with some places in the development world.

I'm a proponent of knowledge.
Fellas, know your stuff.

I was moved from a team I loved where I felt my tech leads were competent, where my tech leads valued my skills and my manager was fabulous and excelled at making sure everyone had the resources they needed and was rewarded for good work, to a team where my tech leads are inconpetent and constantly treat all the junior devs with condescension. Additonally, although my new manager seems nice and has good intentions, she is focused too much on the results of work and not the morale of her team. Consequently, she consistently ignores the negative feedback that is given about the tech leads because "the tech lead gets the results"

Hey devs!!

I just can't stop myself from sharing this.

Its been two years now ... my junior is working. and now she is handling standalone WP projects.. but somehow her task got stucked so I was asked to help her.

So I just said check the count of variables and she messaged me with code .. Ma'am this isn't working .. Haha.. I mean come on she better can google out atleast for syntax :(

<?php if(count($content2 == 3) && count($interestt2 == 3))
{
print_r($content2);
print_r($interestt2);
}else{
echo "not checked";
}
?>

I can see why companies hate hiring junior devs. The ones I've worked with have been incompetent. If I was the hiring manager, the only time I'd hire a full fledged junior dev for a full stack role is if they have already built a simple full stack website. Ugh.

Junior newbie dev here.
I want to buy "Clean code" by Robert C Martin. Its tad bit pricy here in india.
I wanted other devs (especially senior devs) opinion on the book. Is it worth the buy ? What are your reviews ?

Everytime I consult with senior devs on how to transition from my sysadmin job and get my first dev job they always tell me to get a CS degree.

Look. I will get that fucking degree eventually. But I want to build up dev skills and learn from a company before killing myself over math crap for 3 years. But it's like a vicious cycle. Every junior position I apply to rejects me because I have no degree.

I'm fucking frustrated and depressed.
What should I do? I want to break from the IT meme and get a dev job.

In the meantime I'm doing small projects and freelancing in my very little free time. But I feel I'll never truly be a developer until I work as one professionally.

How do you handle work colleague who is becomming too chummy? Got this one guy who is my age at work (we are in late 20's), we've been working for the past 5 months in the same team. At first I was in a bad place so kinda overshared my personal life with him so did he. Went out for drinks and etc.

Problem is that its becoming weird in the office now. I am trying to fix my habits like quitting drinking and quitting smoking and all I get from him is pressure about why Im not going out and etc. He doesnt even really know me, just assumes that if Im not hanging out with him I just sit in my home on a couch. And in the end what if I do? What kind of guilt tripping is this?

Also I feel that he as a senior is kinda undermining me. I am not a senior but definetly also not a junior anymore, and he treats me as a junior while he has at least half of knowledge gaps as me. He has been working remotely for some time now and I noticed even how dynamics in the office changed. I see other devs coming up to me for advice and I see that I am actually competent enough to help them. If my big ego senior was here, he would be sucking all of the attention out of the room and I would be in his shadow yet again. Its just weird.

Teach students the importance of clean code/architecture and testing. Even if they dont yet understand the more complex topics such as architecture, they should understand why quality is important and that software is a craft more than a science. You cant just apply principle X and insert design pattern Y and profit++. You actually have to think and constantly improve. AND TEST.
Think I would probably also cover things like build automation and continuous delivery. These are now important things for junior devs to know about going into companies.

Have u guys ever wonder, all those devs we rant about (mostly senior developer), how it feels like to be them? Today I realized, I am most probably becoming like one.
I joined devops 7 month back(around one and half year in industry). Right now, I am 2nd senior member in project. I have done deployment on multiple environments more than 100 times. But till today, I never knew how the deployment is being done. I knew to trigger job but I never knew how it worked. Today when a junior asked me, then I learn ansible, then I understand whole deployment process.(and remember I am 2nd senior most with 7 month in project)
Sometime I wonder, till now I always had good rating and most responsible title. But how much is that because of my technical knowledge? Sometime it feels like I have very good luck. But man, it's very depressing. Sometime it feels like my junior don't get enough limelight because I am in their way although they have good knowledge but they lack the though process for now. Most of the time my senior present me as role model to juniors, and it's very embarrassing for me(this will not continue on as I talked to my seniors) . I did work on good projects from time I joined company. And never had any issue and always deliver what needed. But I still can't write code in Java to take input or do for each on array in javascript without seeing stackoverflow once.
Now I fear that someday I will write piece shit of code and whole efficiency of project will go down cause of me. Atleast, the person who will get to fix it will get a chance to have good rant here. I tried open source projects to understand how to write good code but I always have hard time understanding new-projects which I never worked on.
Then there is reputation on Indian devs. This is my another Fear. That someday cause of me, my fellow devs will get bad reputation as well.
This coming year, my goal is to fill up all the holes but I don't know why my fingers are crossed.
Sorry, I had to bring this out somewhere. And please ignore my grammatical mistakes.

Serverless and death of Programming?!

_TL;DR_
I hate serverless at work, love it at home, what's your advice?
- Is this the way things be from now on, suck it up.
- This will mature soon and Code will be king again.
- Look for legacy code work on big Java monolith or something.
- Do front-end which is not yet ruined.
- Start my own stuff.

_Long Rant_

Once one mechanic told me "I become mechanic to escape electrical engineering, but with modern cars...". I'm having similar feelings about programming now.

_Serverless Won_
All of the sudden everyone is doing Serverless, so I looked into it too, accidentally joined the company that does enterprise scale Serverless mostly.
First of all, I like serverless (AWS Lambda in specific) and what it enables - it makes 100% sense and 100% business sense for 80% of time.

So all is great? Not so much... I love it as independent developer, as it enables me to quickly launch products I would have been hesitant due to effort required before. However I hate it in my work - to be continued bellow...

_I'm fake engineer_
I love programming! I love writing code. I'm not really an engineer in the sense that I don't like hustle with tools and spending days fixing obscure environment issues, I rather strive for clean environment where there's nothing between me and code. Of course world is not perfect and I had to tolerate some amounts of hustle like Java and it's application servers, JVM issues, tools, environments... JS tools (although pain is not even close to Java), then it was Docker-ization abuse everywhere, but along the way it was more or less programming at the center. Code was the king, devOps and business skills become very important to developers but still second to code. Distinction here is not that I can't or don't do engineering, its that it requires effort, while coding is just natural thing that I can do with zero motivation.

_Programming is Dead?!_
Why I hate Serverless at work? Because it's a mess - I had a glimpse of this mess with microservices, but this is way worse...

On business/social level:
- First of all developers will be operations now and it's uphill battle to push for separation on business level and also infrastructure specifics are harder to isolate. I liked previous dev-devops collaboration before - everyone doing the thing that are better at.
- Devs now have to be good at code, devOps and business in many organisations.
- Shift of power balance - Code is no longer the king among developers and I'm seeing it now. Code quality drops, junior devs have too hard of the time to learn proper coding practices while AWS/Terraform/... is the main productivity factors. E.g. same code guru on code reviews in old days - respectable performer and source of Truth, now - rambling looser who couldn't get his lambda configured properly.

On not enjoying work:
- Lets start with fact - Code, Terraform, AWS, Business mess - you have to deal with all of it and with close to equal % amount of time now, I want to code mostly, at least 50% of time.
- Everything is in the air ("cloud computing" after all) - gone are the days of starting application and seeing results. Everything holds on assumptions that will only be tested in actual environment. Zero feedback loop - I assume I get this request/SQS message/..., I assume I have configured all the things correctly in sea of Terraform configs and modules from other repos - SQS queues, environment variables... I assume I taken in consideration tens of different terraform configurations of other lambdas/things that might be affected...

It's a such a pleasure now, after the work to open my code editor and work on my personal React.js app...

The fog of war over all that happened with my change of team is starting to dissipate.
3 people were involved and there were 4 different versions of the whole situtations, but from what I've been able to collect it looks like the company is expanding and one of the mail KPI for the current team leaders is how good they are at creating a NEW generation of team leaders, to take care of the new entries.
My previous team leader told me about all these new growth perspectives and the junior entries I could manage, knowing very well of the desire I have previously expressed of being a senior dev with my small group of juniors to teach.

I declined the offer, stating that this whole year has been exhausting. Every single time I've tried anything (using modules for new components on our old web client, tsdoc to document our types, suggesting technologies like ANYTHING BUT ANGULAR AND MONGO, telling how removing down migrations was a retarded move) my suggestions were either shrugged off or flat out refused. Let alone how every time I was proven right, except for angular but give it time and that will bite their tail as well.
Don't get me wrong: they are well withing their right when they take all those decisions, and more. But I DO NOT PLAN on selling a plethora of bad decisions to a new stack of devs as if they were the gold standard.
"I understand your reasons; you, as a company, need a well coordinated team all running towards a goal; loose cannons are harmful.
But now I need you to understand me: I do not agree with your technical direction. I never lied before and I will not start now. Promotions don't matter nearly as much as my integrity, and integrity in my world means speaking up about problems. Your position is perfectly valid, but mine is as well and they can't be reconciled. If I were you I'd make myself a favor and make sure IHateForALiving doesn't become a team leader; given your direction, I'm not the man you want right now".

As mentioned, one of the KPI for team leaders is how succesfull they are in finding new team leaders, and trying to turn me into one didn't end well; I love sharing knowledge, but being honest to myself is far more important to me. So this meant my previous team leader failed in a very big task, and thus was demoted? At the same time, I've been there for 2 years now so they're not really eager to replace me, but I'm under strict examination too as of now.

As a junior dev, you are stuck on a Problem and somehow you are not able to proceed and there is a ridiculous process to finish the task on a deadline otherwise you have to hear from higher management. Your manager cum senior dev is not helping you out or not responding in any way. Do I kill myself being so incompetent dev or burn my ears listening to management complaints or is there any way I can get out of it? My life is just miserable and I feel demotivated day by day.

Just ranting my heart out...

i HATE having to hold other junior devs hand through THEIR work 😩

Worst part about my job is training junior devs with their supervisor insisting them to write unit tests without prior programming experience

Tips on getting promoted on work:

1. Collect a list of all improvements and achievements that u did during your time in that workplace

2. Compare your output with your colleagues output, check their MR's, their complexity and compare with yours.

3. Talk with your manager about a raise. Tell him about your achievements, like maybe you are working on a wider scope than others. Maybe you are mentoring junior devs. Or maybe you deal with a bigger workload than others but still deliver on time. Maybe your communication is good or maybe you document stuff very well and in that way you make your team more efficient and increase team output. Whatever. Pitch and sell yourself. Also provide some personal reasons why you need a raise, like maybe u have kids or maybe your rent doubled. Inflation and so on. Selling point is that u are a human not a greedy bastard.

At the end of that talk the manager most likely will say that he needs to speak higher ups, he needs to gather feedback from your colleagues and so on. Give him a week or two if possible, no more.

He will probably get back to you with an offer. If there is none start applying, get an offer and put in your notice. In my case I waited 3 months for my raise to go through. I put in my notice, had a stressed call from manager, showed him my offer and my raise was arranged the next day.

!rant: I need a little advice from fellow devs. I've come to the conclusion that development is not the right career path for me, but how to advance from here?

I've worked a little over a year as dev/scrum master and lately I've been assigned small project management tasks. I really liked the project management stuff, and I like talking to stakeholders and converting their ideas into well described requirements and development tasks.

But who will hire a junior level engineer with no formal project manager training or certifications?

What kind of jobs could I apply for?

So so so frustrated why is finding the right job such a fucking hassle! Landed my first junior dev job that was not what I was expecting mostly I work jira ticket written my middle aged morons to update PDF's servers that never had anything deleted from them 100k of files and about 10k folders shit you not. Don’t delete anything co worker deleted a file that took down a couple thousand person call center.

Looking at other junior positions with junior in the title and they want 4-7 years expierence at two different places. WTF if I have 7 years I would think I would a senior dev or close to one.

Just there is such a disconnect between the people who post the ads and vett the candiates to the hiring managers.

Does it get better? Started going to meet ups to meet more experienced devs in my area but still trying to find the right fit.

i have an idea today for find job as Junior:

First of all, startups usually hire senior devs only for two reasons:

1) is critical to their business, they need people that will ensure the project will be done no matter what, seniors usually brings that to the table.

2) The startups that raise some founding, usually have 100k+ raised, that money is basically enough for hire Seniors for some time without troubles, taking into account they will usually be highly profitable in the mid term, it is not a big deal to take the risk

Today startups, at least the most interesting ones, play the game in God Mode due to that founds raising, it is like having a max level character in some MMO with insane amounts of gold, you will buy only the best gear with that gold, not the low level gear, why you want to buy low level stuff, if you can buy the best of the best? that is why Juniors are not likely to have a place in startups, they can pay the Seniors.

But, there a situation in what an startup will wish to hire some Juniors, this is situation is, when they have never raised founds, they have no Cheat Mode, this ones are usually startups that have just few weeks or months of being created, and they need the MVP ASAP, this startups usually already have one or two Mid/Senior level engineers, but they have a very highly benefit from having a Junior in their team, this guy will no take any part in the Cake, will only work for lot less money and will discharge some stuff from the Seniors (Taking into account that is a minimum competent Junior).

Here is where Juniors can get jobs, at least for start their careers, and taking into account that thousands of new startups are created every year, this is a major market.

Ok, i already test that this approach if viable, i send requests to 5 startups that meets the conditions, and got response from 4! still not make a deal, but this is a lot more than 0 response after 2 dozen of applications to more stablished startups.

What you think about this? maybe this is just the jobless syndrome attacking me fuck

I'm currently the only dev that works with a client's dev team. That's not really how we usually work, usually it's a whole team of ours.

Three aspects why this sucks:

1) the client's dev team is made up of juniors and junior to intermediate devs. All of them are new to scrum. I therefore have to constantly support (dev & agile workflow), check all the PRs and have to think of everything in Refinement meetings.

2) the client's based in another timezone and the PO is super busy because we're the only agile team in their company. Therefore this is going to be the third Friday in a row where I have meetings until 6pm.

3) I also have a specific time frame I have to start working for my company, so I constantly work extra hours due to the time difference.

I'm just tired.

!Rant

Tldr: great spike to solve deployment problem may be a wasted effort.

Deployments of an ancient electron application need to be done in CodeDeploy to deploy the latest build. Customer hour restrictions cause this to be done only after midnight, and manually checked.

The whole team knows this is the wrong method of deployment and that there are many other operational problems with the project.

A few other senior team members get together and decide to spike out a way to use electron auto-deployment to accomplish this without using code-deploy at all.

After a shallow dive into this subject, we all get pulled aside to handle a change in another part of the software ecosystem. It happens. We leave the spike behind.

A junior-intermediate developer on the team pics the project up and gets a good spike going in a day and a half! We are all high fives and beers. This is Friday.

By Monday there is a pull request in for code review and it looks solid. Seems like it will make deployments a lot better.

Preparing the last deployment (hopefully) with CodeDeploy ever...

Marketing team members inform us that they are running an add system on the customer devices and to do it they are using Linux.

The current application being deployed is using Windows 10 (yeah, another problem).

They say they have made plans to move our application over to Linux. This means we may not be able to launch the junior devs great spike and the old deployment method may stay for the time being.

Meetings soon to find out how all of this will hash out.

End of rant. I hope I'm doing this right

I start my first "real" job on Monday. I will be one of roughly three new junior full stack developers on a team of 15 senior devs. The company has a casual dress code and they allow headphones. What should I expect? I want to grow and I don't want to be a nuisance, I also want to earn a reputation and become respected when I do have something to say.

Perhaps as a tip for the junior devs out there, here's what I learned about programming skills on the job:

You know those heavy classes back in college that taught you all about Data Structures? Some devs may argue that you just need to know how to code and you don't need to know fancy Data Structures or Big o notation theory, but in the real world we use them all the time, especially for important projects.

All those principles about Sets, (Linked) lists, map, filter, reduce, union, intersection, symmetric difference, Big O Notation... They matter and are used to solve problems. I used to think I could just coast by without being versed in them.. Soon, mathematics and Big o notation came back to bite me.

Three example projects I worked in where this mattered:
- Massive data collection and processing in legacy Java (clients want their data fast, so better think about the performance implications of CRUD into Collections)
- ReactJS (oh yes, maps and filters are used a lot...)
- Massive data collection in C# where data manipulation results are crucial (union, intersection, symmetric difference,...)
Overall: speed and quality mattered (better know your Big o notation or use a cheat sheet, though I prefer the first)
Yes, the approach can be optimized here, but often we're tied to client constraints, with some room if we're lucky.

I'm glad I learned this lesson. I would rather have skills in my head and in memory than having to look up things and try to understand them all the time.

I am a junior Java(Spring) developer myself and I am trying to understand the current trends.

Why are devs hating (or) moving away from java?

Ok. I got it. I need a portfolio. That will speak for you. I’m working on it. I’m building great stuff. In the meantime. How the heck do I get a job as a junior web developer with no experience. I only have a coding bootcamp and a 4 month internship. All companies want people with experience. You won’t even have an interview without experience. So what’s the strategy then? Looking out for some words of wisdom from fellow devs.

is being a tech/dev person, a dead end job?

i have been thinking about this for sometime. as a dev, we can progress into senior dev, then tech lead, then staff engineer probably. but that is that. for a tech person :

1. their salary levels are defined. for eg, a junior may earn $10k pm , and the highest tech guy (say staff engineer) will earn $100k pm, but everyone's salary will be spread over this range only, in different slots.

2. some companies give stocks and bonuses , but most of the time that too is fixed to say 30% of the annual salary at max.

3. its a low risk job as a min of x number of tech folks are always required for their tech product to work properly. plus these folks are majorly with similar skills, so 2 react guys can be reduced to 1 but not because of incompetency .

4. even if people are incompetent, our domain is friendly and more like a community learning stuff. we share our knowledge in public domain and try to make things easy to learn for other folks inside and outside the office. this is probably a bad thing too

compare this to businesses , management and sales they have different:
1. thier career progression : saleman > sales team manager> branch manager > multiple branch manager(director) > multiple zones/state manager (president) > multiple countries/ company manager (cxo)

2. their salaries are comission based. they get a commission in the number of sales they get, later theybget comission in the sales of their team> their branch > their zone and finally in company's total revenue. this leads to very meagre number in salaries, but a very major and mostly consistent and handsome number in commission. that is why their salaries ranges from $2k pm to $2-$3millions per month.

3. in sales/management , their is a always a room for optimisation . if a guy is selling less products, than another guy, he could be fired and leads could be given to other/new person. managers can optimise the cost/expenses chain and help company generate wider profits. overall everyone is running for (a) to get an incentive and (b) to dodge their boss's axe.

4. this makes it a cut-throat and a network-first domain. people are arrogant and selfish, and have their own special tricks and tactics to ensure their value.

as a manager , you don't go around sharing the stories on how you got apple to partner with foxconn for every iphone manufacturing, you just enjoy the big fat bonus check and awe of inspiration that your junior interns make.

this sound a little bad , but on the contrary , this involves being a people person and a social animal. i remember one example from the office web series, where different sales people would have different strategies for getting a business: Michael would go wild, Stanley would connect with people of his race, and Phyllis would dress up like a client's wife.
in real life too, i have seen people using various social cues to get business. the guy from whom we bought our car, he was so friendly with my dad, i once thought that they are some long lost brothers.

this makes me wonder : are sales/mgmt people being better at being entrepreneur and human beings than we devs?

in terms of ethics, i don't think that people who are defining their life around comissions and cut throat races to be friendly or supportive beings. but at the same time, they would be connecting with people and their real problems, so they might become more helpful than their friends/relatives and other "good people" ?

Additionally, the skills of sales/mgmt translate directly to entrepreneurship, so every good salesman/manager is a billionaire in making. whereas we devs are just being peas in a pod , debating on next big npm package and trying to manage taxes on our already meagre , "consistent" income :/

mann i want some people skills like these guys

Hi fellow devs, I have a question for you.
Do you think asking questions like (related to JS):
- What is the type of null?
- What is the result of 0,1 + 0,2 (0,30004)
- and other JS specifics

in a job Interview for a Junior position is the right thing to sort out applicants?
I have several years of programming experience, just not in JS, and got rejected because I couldn’t answer these questions. Feels kinda weird😅 What’s your opinion?

So, I work as a sysadmin junior (6 months and going), and in the past few months, I learned what my boss warned me about - Devs don't understand us admins, and we don't understand the devs.

We have this huge client who is about to migrate to our company (We do mostly server managment/Housing/Renting), and I am so gald I don't have to work on the migration myself!

Just hearing what the company devs say makes me facepalm: No, it won't work. It cannot work on just 3 machines (They use like... 20 in total), no, we won't get rid of our docker swarm, that's essential (Doing the absolute minimum in their infrastructure, just a fancy buzzword to lure people on. Though they've spent like 2 years developing the app that uses it, so they my not want to give it up).

I kid you not, once, they replied to an email that contained the phrase "To be afraid of/worried about" something during the migration, that something could break, not work, be unstable. 7 times.

Might not sound as bad, but it was a rather short mail, and when they're so afraid of everything, its kinda hard to cooperate with them.

My colleague literally spent this entire week mapping out /their/ infrastructure, because they were unable to provide us with the description themselves.

And as a cherry on top, they sent us a "graph" of relationships of all the parts of their infrastructure that was this jumbled mess of rectangles and arrows. Oh, and half of all the machines were not even in the graph at all! Stating that "We also have all this, but I really don't know how to ilustracte the interactions anymore"

Why do companies like that exist? If you build an infrastructure yourself, shouldn't at least someone know exactly how it works?

I need help for a dev test.

So the company that I work at is hiring a couple of new devs and they’ve put me in charge for test in order to see if the applicants are any good.
When I was hired there were no tests so I don’t have that many ideas for a good one.

Have you guys any good recommendations for a test or what it could consist of?

I’m thinking of having multiple small tests so if one misunderstands the task it’s not the whole test they fail. Would that be a good idea or not?

It’s for senior and junior web developer.

Any idea is greatly appreciated 😀

Went to the client meeting for the first time. Neve saw a group of people collectively trying hard Not to make a point.