Senior dev : * doesn't use git *
Me: you seriously should use git...
Senior dev: * still doesn't use git *
Senior dev: * overwrites production files with old files from other computer *
Senior dev: * talks to boss *
Boss: * gets angry at me *

My senior dev, shortens “analytics” into “anal” variables. Iam literally dying while Reading through the code!

Nobody:

Senior frontend Dev at my company: "microservices best thing ever"

Also him: "Relational databases gonna die"

Also him (talking to the DB team): "You're gonna dissapear, Mongo is the future"

Me: "Eh... Dude, Mongo is still a database.."

Him: "Microservices"

Send help...

Me, a junior dev: * reports an important issue and a possible fix *

Senior dev 1: nah, it'll do just fine.

Senior dev 2: that won't be an issue, don't you see? It's under control, man.

Senior 3: why are you even here? Why are you even talking?

Manager: yeah, what could possibly go wrong?

* a year after releasing the product, one of the seniors got fired and another one was hired *

New senior: this thing is bananas, code is inconsistent and there's memory leaks everywhere, how does that even work?

Me: nobody believed me when I said that.

Manager: it did work very well, where's the issue?

Me: it's everywhere, goddammit! Don't you see?

New senior: junior dev is right.

Me: I've been a WHOLE YEAR saying that!

Manager: did you? Really? Nah, you didn't.

...

I'm tired of this shit.

How I see my senior dev using vim,

One of the project manager came to one of our senior pro developer to say something. Before he even said anything the senior dev said:

Oh Fuck, not you again!

The pm politely left the area

New senior dev joined the project today.
Senior dev: "There's no way for me to test my changes before I merge this into develop"
Me: "Can you at least run our test suite?"
An hour later the develop branch is fucked and everyone who has merged it locally has pages of red errors splattered across their screens whenever they run any tests.
Start looking into what the fuck is going on.
Notice that all the errors are related to changes the new guy made.
Ask him if he ran the tests..
Senior dev: "Nah they wouldn't catch anything locally "
Stare at the stream of red text running down my screen.
Normally I wouldn't care but we were trying to prepare a release... RUN THE FUCKING TESTS ASSHOLE.

rookie dev : "to my senior, im gonna ask you the basic questions instead of googling it. Im gonna disturb you every now and then.... just kidding"

Senior Dev: "Be mindful of what you email to the team, some may be rubbed the wrong way."

Me: "I'm going on a year, I figured it was okay to send a meme when appropriate like [the other guy]."

Senior Dev: "Well, [the other guy] has been here for 17 years, so it's sort of expected from him."

Me: "You know what would be weird? If I was here for 17 more years and then 'started' having fun with the team."

Senior Dev: "Yes, but [the other guy] is the only one doing his particular job, which makes him important, so he tends to get away with more."

Me: "No, I get it. If you're a linchpin you can reply with cat memes, but people like me need to mind their place."

Senior Dev: "It's an uncomfortable conversation, but it's all bureaucracy."

Me: "Duly noted. But could you please forward me the specific email I sent that caused the concern?"

Senior Dev: "I'm not sure what the exact email was, when it was sent, or specifically whom it offended."

Me: "Okay, because that would be like me walking up to you and saying that you have a problem that needs to be fixed, but I don't know what your problem is or why it needs to be addressed."

Senior Dev: "You're right, but just be mindful of the emails you send outside of the group."

Me: "I've never group-emailed anything outside of the team."

Senior Dev: "Well, I'll let you get back to work..."

[FML!] 🤦‍♂️

Manager: "yeah so thanks for understanding we can't give you a payrise, by the way we need you to train the new guy we just hired who is your senior because even though he is more experienced than you as a c# dev he doesn't understand what an object is"

Me...

When you meet a senior dev that's far superior to you in every way.

Please don't make junior developers feel they're a burden.
Have you ever googled "how to mentor junior developers"? It's quite mind-blowing how many articles, talks and panels are on this topic. And yet still junior developers are not feeling welcomed in their companies.
Yup, you guessed it, we also have something to add (based on our own experience):

1. Asking for help is not easy. Please don't blow juniors off by telling them to read docs when they ask a question. Always assume they've read it and did a sprint to solve the problem. They ask you, because they see you as a mentor and really need your help. If you can, spend more time with them and guide through the entire problem solving process.

2. Please don't think "I learnt it this way so you should too". If you're in charge of teaching a junior developer, don't expect them to be a carbon copy of yourself. Because even though in your opinion your approach is more "pro", they might not be there yet to use it properly. And last, but not least:

3. Of course, juniors will compare themselves with seniors on their team. And there'll be moments they feel so guilty and so afraid that they cost the company too much, that they need training, and supervision, or are between projects and are not bringing in any money, and they'll fear that their company regrets hiring them. Make sure they don't feel like a burden. As juniors, we often
have this misconception what is expected from us.

Dear tech companies, please set very clear expectations and tell your juniors you're happy. Don't get us wrong here. We don't expect unicorns, roses and pats on the back from companies. We do understand- this is business, and at the end of the day we all are here to make money. To do so, companies need to make smart investments. Junior dev with a great assistance, planned support, and a clear training program will become a great asset. It really is as simple as that.

A customer did send a 3GB+ .txt file to the database guy in my office. He (senior dev) starts ranting about how he should handle this since his tools failed to do whatever he had to with this data.
After seeing him struggle some time I did a short search (I'm apprentice since 4 months) and then told him to use "split -l".

Senior Dev at work told me to cherry pick commits from another branch....later found out that it is an actual git command ! 😅

git cherry-pick <commmit>

junior dev: how do i-
senior dev: RTFM
junior dev: `npm install rtfm`

Junior dev: asks me an easy question cuz he's too lazy to figure it out

Me: listening, thinking he's gonna waste my time again 😓

Senior dev: eavesdrops and helps him out

Me: saved me, woohoo 😎

*Few minutes later*

Senior dev: "by the time you finished asking this question, you could have compiled the code yourself to see what happens"

Me: 😂😂😂😂😂🤣🤣😂😂😂

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

Junior dev: I found the bug
Senior dev: I found a bug

Junior dev vs senior dev? Anyway?

!Rant
Senior dev from another team comes up to me:
"you alright? Looks like you're struggling with something. Want me to give you a hand?"

And my personal favourite:
"feel free to slack me whenever you need help. Don't be afraid to ask questions. Only way to learn is to ask"

He also recommended me some books and resources to read.

I left work today motivated af!

Being told I’m not experienced enough to get a senior dev job I interviewed for.
Even though I aced the first 4 interview rounds, the tech test feedback was “the best solution they had ever seen”, and I’ve been a senior dev for 25 years.
Time wasting assholes.

Me telling a senior dev on how to install a proprietary software:

Me: Sir, the instructions are in the readme.txt

Senior: I'm supposed to read the readme?!

I am building a mobile site using flexbox. A senior dev came running to tell me that we need to support IE. Looked at him and said, "IT'S MOBILE!"

im a senior c# .net dev and i wear glasses.
i can c# and cant c# at the same time.
ha! beat that!

That awesome feeling when you solve a bug that your senior dev spent almost 4 hours struggling with in 30min 😎

Two heads are indeed better than one

1st post. Not sure if rant.

> Join 1st job after college.
> Desk assigned is close to a senior dev
> Random day, QA asks senior dev questions on something and coincidentally I happened to be working on the same thing.
> Senior dev borrows my system and explains qa something.
> By the end of explanation senior dev had bunch of shell commands written on notepasd on my machine.
> I don't understand jack shit of whats happening.
> QA looks at me and says, "Ping me once."
> I think, "no idea what just happened but must be something related to network ."
> I open terminal and type "ping" and quitely wait for further instructions (address to ping that is).
> Everyone starts laughing their asses off.
> QA guy opens slack, and sends himself the commands on text document.
> I realize what just happened
> Laugh awkwardly with everyone to ease the pressure
> FML

Senior Manager: I have to use your app today, how do I do that?

Dev: Well first you log in, and then you clic—

Senior Manager: That’s way too low level, I only deal with things on high level! Explain it to me from a high level.

Dev: Use the app to orchestrate the visibility of action items to stakeholders and pivot the leverage towards buy-in.

Senior Manager: Hmmmm….

Dev: Agile.

Senior Manager: Aha! I understand how to use the app perfectly now!

Senior Manager’s Account: Last Login - Never.

So apparently two "senior" "laravel-engineers" spent a total billed 35 hours trying to figure out a "critical bug" which "doesn't happen locally".

I went to the dev-console, saw it is generating http urls (fronted by cloudflare https, running on http server-side) and fixed that in maybe ~15 minutes, fucking morons.

Alleged senior dev in a company I was consulting at 👴: "interfaces? I never use those. I don't believe in interfaces"

*Doing a Peer Code Review of someone senior to me*

Me: This fix doesn't look like it will work, but maybe I don't understand. How does this fix the defect?

Senior Dev: *Blinks* It works on my machine

Me: But how does it work?

Senior Dev: It works when I run it on my machine...

Me: Do you know if this will fix the issue?

*Silence*

Never seen QA punt an issue back to development so fast.

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.

Senior Devs made the Program Manager cry. Dev Lead did nothing to stop it from happening, Program Manager Lead was in shock.

Senior Dev: "-bleep- I hate Javascript. It is such a pain to have to debug in Chrome"
Mgr: "Why are you 'having to' debug in Chrome?"
-in an almost 'you didn't know?' condensing tone -
Senior Dev: "Because you can't debug Javascript in Visual Studio."
Me: "Umm...pretty sure you can."
Senior Dev: "No, its impossible. I have to make a simple change in Visual Studio, save it, deploy all the files to the server, restart IIS, open up Chrome and use it's developer tools to find bugs. -bleep- Javascript sucks sooo bad."
-I do a quick search on stackoverflow-
Me: "No, I'm looking right at it on stackoverflow. You can debug Javascript in visual studio just like anything else."
- Mgr looks over and smiles, not trying to laugh -
Senior Dev: "Hey, did you watch that scene in Stranger Things...man thats a good show ..."
- other devs jump in to comment about the show, completely dismissing the VS/Javascript conversation -

Not sure WTF just happened.

Going to another senior dev.

Support: A customer complained about a nasty bug.
Senior Dev: There are no bugs in our software, just challenges that need to be solved.

I was a midweight dev acting as a lead dev on the frontend development of a project. I had already built most of it, it was all vanilla JavaScript, had no jQuery, the code was simple, fast, and small. Then I went on holiday and the company put a senior lead on the project to carry out remaining work while I was away.

When I came back, there was a bug in the age gate page and I started to investigate. I then noticed that the asshole added jQuery to the code just to select the country and date of birth input fields. That idiot, a senior lead dev earning more than twice what I earned, didn’t know how to select some elements on a page! I nearly lost my temper when I saw the added bloat.

Small Me(m): learning some basic code
Senior Dev(d): *walks by and sees my code*
m: hey got any advice on this?
d: learn to use regular expression. *walks away*
m: 30min later... *Mind blown*

And coffee of course ☕

My friend brought me a simple python problem. He expected the output to be 2,2,3... instead of 2,3... I didn't know python, but with a quick tweak to differentiate the two prints, I understood that the range() function is exclusive.

Before coming to me, he asked his senior dev & that guy just said - "Oh, your editor has a problem". 😐

Not everyone can do it 🙌

*Me explaining how to use npm to my colleague (senior dev)*

M: So from the command line you just need to move to the directory with the package.json first

C: Uhm right
C: *types ‘move dir’*

M: Aight just give me the keyboard

How does a senior developer not know how to use cd in a command line?

This company has been a "start-up" for 5 years farming money off of fucking idiots using a shitty CMS.

- The senior dev gets paid 15/hr
- No use of version control or testing
- the CEO has no fucking knowledge about tech.

and you wonder why it's FAILING?! I'm surprised you guys stayed afloat this long, jesus fucking christ.

"Senior Engineer/Dev/etc." is just the title for the guy who's learned from making the most mistakes.

!rant
Observed a full deployment the other day and discovered it's extremely inefficient. I proposed an idea to fix it, and was shot down by a senior dev on the team. I was ranting about how asinine the process was and how my process could reduce the amount of time and training required to do deployments with out any additional cost or overhead. A senior dev from another department over heard me, found my workspace and told me (in a nutshell), "write up a document about why the current process is garbage and how yours is better, and how it works, I'll review it and we'll get it worded and formatted right. When we finish the document, I'll forward it to the CTO of your department with your name on it and my recommendation for review." Fuck yeah. 😈😎

When your boss asks you and the senior dev, “how do we get the overseas contractors to stop writing lazy code and feel like they’re part of the team?” And you both respond with “we don’t, they won’t stop and don’t care. This is just a contract. Stop expecting them to love the project”. And then the boss agrees that he gets what he pays for.

...and then promptly says, “but HOW do we change their attitude about this?”

The senior told me he keeps a resignation letter in his drafts folder. He sometimes opens it and updates it with the latest gripes. He’s over 70 years old. The approach of DGAF is ever closer for him.

I love the skill requirements section of a junior Dev job advertisement.

To summarise "Basically you'll need all the skills and experience of a senior, but we are gonna pay you much much less". 😔

Junior dev:Hey,see my code works :)
*After analysis of code*
Senior dev:Let's talk about complexity bro
Junior dev: shit :(

Me as Junior Dev doing mysql first time, specifically INSERT test data to test db, sucess on first try.

My Senior co-worker says: WOW, Baby's first INSERT...... that sounds so wrong out of context xD

We made a software for hospitals in my old department. The senior Dev kinda gave me the software, because he thought it sucked and was perfect for a newbie like me. I really loved my work and gave everything I had to improve the quality of software, introduced tests, refactored old smelly code and talked with the product manager to overhaul the ui. Several months later this little shit project the senior gave the newbie, was a huge success and better than any thrash that the senior has created. The senior was really pissed, so everytime I had some days off, he tried to sabotage me in any way. I couldn't take that and many other things anymore, so I left the company. The most tragic part is, that my software could become a massive foundation for the company, but after I left they abandoned it. I still had some good contacts within the old company and they said, that the senior dev told everyone how bad everything was, that I have done through the years and that they can't even describe how bad the architecture of the software is. tl;dr fuck off!! I've done so much things for the company and they never appreciated it. I'm glad I quit that job. Best decision ever!!

It's 3:17AM and the senior dev won't give me a ship-it even after 4 code revisions. I've decided to give up on life

When I started learning to code I couldn't wait to become a 'senior dev' thinking I would spend all my time writing awesome code.

Now that I am a 'senior dev' and have the experience I now spend 90% of my time documenting & planning and even less time coding :'(

Senior dev says "it is a piece of cake and it can be done in 2 days", when a new feature is suggested and assigned to me.. but when it gets assigned to him : "This is a big feature and there are lot of things that we need to decide, it will take more than 3 weeks".

It's my 2nd week into my new job. I asked people what they think they are doing.

The summary:

Senior dev: we fix bugs
Junior dev: we write code
Intern: we create the future

It depends how you look at it. They are all called software engineer or developer.

New spin on the Manager / Dev format!

Recuiter: WE NEED AN ABSOLUTE NODE EXPERT, NODE NODE NODE, WE LOVE NODE! WHAT IS YOUR NODE EXPERIENCE?!?!

Dev: Well I've had exposure to it since it was nearly new, all the way back in 2012, and since my professional career started about 7 years ago I've used it fairly often on a per-project basis.

Recruiter: WELL HAVE YOU BEEN USING IT DAILY FOR THE PAST 5 YEARS!?!

Dev: Well no, as I said I've used it for specific projects... anyway, there are these things called weekends...

Recruiter: WELL WE ONLY WANT NODE ZOMBIES SO SORRY.

Dev: Thanks for reaching out and wasting my time.

Recruiter: ...

Dev: ...

God recruiters are like robots, don't they understand senior-level engineers are language agnostic?

Senior dev says "oh, we're not looking for load time optimization" and at the same time, the website loads for at least 1 minute on localhost... 😫

Recently been made senior dev at my company... I never really knew the struggle of finding decent developers who haven't massively exaggerated their knowledge on their CV's 😑

Hmmm there are several

Senior dev would leave for weeks(he was company co owner) and would blame shit not being done on me even though he gave me no access to his codebase. Shit back fired right in his face.

Senior dev called me an idiot(different company) for stating that I learned about MVC from Rails. I have no clue what triggered that reaction, but the way he said it really ticked me off. It was on a remote position, left soon, the dude was s cunt.

Next goes for my office: we yell random shit all the time, from racist to sexist to all around disturbing because we are constantly unsupervised.

Head of department knows:P he laughs with us.

When you get to 12pm (lunch time) and you've already been in 7 back to back meetings and no longer know what you were going to actually attempt to do today.

Listen kids, don't become the senior dev, you'll never work an hour in your day again!

#iJustWantToFuckingCodeToday!

Found out a senior dev threw me under the bus for a mistake I made while coding and it affected my raise. Not only was I never initially informed of the mistake, I was never told what went wrong and why it needed fixing. We also don't implement code reviews or anything of the sort. Seems like a great avenue for improvement and growth, right? 😑

The senior dev is mentoring our new recruit.
😨 I know, my face too.

When the newbie asked how to deploy, senior dev says, "Well, we copy and paste this folder from your local box to the server you need to deploy it on. Much better than that git shit, you have so much more control!"

😭

Basically a senior dev that felt attacked because I (still in (IT-) school) could solve his 'oh so hard' programming test 'with ease'. He then went on and wanted to hear one specific answer from me on a very broad question. I (obviously) couldn't read his mind, so he started using that to make me look bad in front of the recruiter.

What a nice working environment...

2nd interview today for a job. I thought it went well but I could tell one guy did not like me. They said they were done after 20 minutes. They told the recruiter I was not senior enough. I have been a dev since 2001. I answered all of their tech questions. Really frustrating.

some senior dev told me about 8 or 9 years ago that i'm going to be a good developer or an alcohol addict in the future. guess what... #teambeer ;)

Got an interview in 3 hours for a senior backend php engineer position. If it doesn't work out im gonna get stuck in a job as a wordpress dev which i hate. pray for me.

We were 6 devs on a big project that needed to be completed in 3 months. Probably my first project as a full-stack dev and the work was very demanding.

The senior of my team was a very sharp and energetic, but also a very "in your face" kinda guy. Like, he was cool, but sometimes a little too much to handle for some people.

Anyway, this guy "Senior dev" worked faster (naturally) and harder than the rest of us and was always willing to help if somebody had problems with a framework, tool or other technology. Also, there was this other guy also a good dev (second best I would say) that just hated the first guy's guts for being "rude and obnoxious" as he put it.

One day, the PM and the senior had an argument about a major change that the PM had agreed to (just to save face with the client) that will force the team to come to work on the weekend. In the end he saved us the trouble of going throught that and the PM had to tell the client that the change wouldn't be made. From then on it went downhill for "Sr. dev" in the company. Until one day he was told that his contract was not gonna be renewed.

Short after, he showed some of us a screen cap. somebody sent him of an email from the "hateful" dev to the PM in which he wrote he had heard that the senior guy was leaving and he couldn't be happier because he was "damaging, problematic and a stressful part of his job". That was such a dick move, we thought he should get back at the guy.

So he sent a fake email to the PM using the "hateful" guy's email ID, that read:

"Dear PM. I'm sorry I said those things about 'Senior dev', I guess I'm just mad that he's a better professional than me and mad that I was born with no genitalia".

After the senior dev left I worked on one more project with the "hateful" dev and he was let go mid project for "not being proactive and making little effort on completing the project".

Unity3D Game Dev Interview

Interviewer: What is reflection and why would you use it?

Me: Gives overview of system and how I've used it in games before.

Interviewer: Sorry that was a trick question, Reflection is really dangerous and slow. You need to go back and learn the basics.

Me: ???...

A huge portion of Unity is built upon Reflection based systems, the entire Monobehaviour base relies on it. Their events system uses it, animation and timeline. I guess their team needs to go back to the drawing board.

How is this person a senior dev?

Never be egoisitc about your code. Its good to feel proud on your code that you did it. but sharing is caring.. don;t be like only I can do this.. ego is not for dev community.. be adaptable for changes whether you learn from junior or senior :)

When you review a PR from a senior dev, find something improvable, suggest it and the dev updates it accordingly.

The first time when this happened made me the luckiest guy. It's still rare, though.

Asking senior dev to help out with a bug I was tackling for several days, and him fixing it in under 10minutes

Me: We should use typescript to enhance our readability and productivity.

Senior dev: No... We don't want to use any other languages except JavaScript.

(A month later)

Too many catch, race conditions and hidden bugs left. 5 hours of debugging

Frontend dev for 10+ years here.

"We can't afford to hire you as a senior, so your job title will be 'Frontend Developer' and your tasks will carry less responsibility than expected from a senior"

One year in, team of 2 handling 3 projects.

After merging with the parent company, we got business cards, mine describe me as a "Senior Frontend UI Engineer".
"Well, our customers only trust seniors, otherwise we can't send you to them".

Meanwhile a former colleague earns >1000€ more a month.

Yeah, fuck you too bosses!

Soooo... My senior dev just dropped a very importand table om our production enviroment.
Time to restore the database.. only 50 GB left

<just got out of this meeting>
Mgr: “Can we log the messages coming from the services?”
Me: “Absolutely, but it could be a lot of network traffic and create a lot of noise. I’m not sure if our current logging infrastructure is the right fit for this.”
Senior Dev: “We could use Log4Net. That will take care of the logging.”
Mgr: “Log4Net?…Yea…I’ve heard of it…Great, make it happen.”
Me: “Um…Log4Net is just the client library, I’m talking about the back-end, where the data is logged. For this issue, we want to make sure the data we’re logging is as concise as possible. We don’t want to cause a bottleneck inside the service logging informational messages.”
Mgr: “Oh, no, absolutely not, but I don’t know the right answer, which is why I’ll let you two figure it out.”
Senior Dev: “Log4Net will take care of any threading issues we have with logging. It’ll work.”
Me: “Um..I’m sure…but we need to figure out what we need to log before we decide how we’re logging it.”
Senior Dev: “Yea, but if we log to SQL database, it will scale just fine.”
Mgr: “A SQL database? For logging? That seems excessive.”
Senior Dev: “No, not really. Log4Net takes care of all the details.”
Me: “That’s not going to happen. We’re not going to set up an entire sql database infrastructure to log data.”
Senior Dev: “Yea…probably right. We could use ElasticSearch or even Redis. Those are lightweight.”
Mgr: “Oh..yea…I’ve heard good things about Redis.”
Senior Dev: “Yea, and it runs on Linux and Linux is free.”
Mgr: “I like free, but I’m late for another meeting…you guys figure it out and let me know.”
<mgr leaves>
Me: “So..Linux…um…know anything about administrating Redis on Linux?”
Senior Dev: ”Oh no…not a clue.”

It was all I could do from doing physical harm to another human being.
I really hate people playing buzzword bingo with projects I’m responsible for.

Only good piece is he’s not changing any of the code.

Called yourself a what? "Chief Technology Officer / Senior Dev" ? For a simple clear cache and cannot do that on your own, you giraffe? Only if I have not pitied you AND YOUR FUCKING EGO, I already sent you a Fucking Love Resignation Letter, you dickhead! You should be ashamed of yourself!!

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

I'm a software developer. Last week I spent half a day teaching a "Senior Data Scientist" how to use git branches. I spent the other half a day teaching him how to use Jira. Now I'm being told that the dev team isn't raising enough Pull Requests. FML

So I’m looking at a senior dev role, and wondering what kind of coding challenges to expect, what have some of you more senior devs had to face in the past?

I have a feeling that a senior dev left a bug on purpose to see if I would catch. Anyone else have that feeling or am I just paranoid?

When you +1 one of your colleagues rants on devRant and realise the whole senior Dev team is on here. Hmmmm.

*me* finding solutions on StackOverflow, Medium, API Docs for hours
*senior dev* walks in and changes one line of code
*works* O.o

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?

Not an enemy yet, but I’ve just debated with a senior dev that said stored procedure is faster, safer, and works better than entity framework

I agree with faster (only a bit) but the rest is just bs

Retarded senior web dev:

shouting 'STOP' to the ones who pointed out his design flaws

cannot accept a js file with more than 100 lines.

nitpicking others not limited to his owm group

eager to try bleeding edge alpha builds packages for large application

left the company before finishing the project he started

Senior JS Dev where I'm contracting can't understand why null != "null"

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.

Boss tells senior dev to show junior dev how to do something. Senior dev says okay. Get back to desks - senior dev refuses to show junior dev because 'if you fuck it up, everything'll break'... How exactly is a person supposed to learn if you won't even let them observe?!

Me: Can I ask you something today? Are you available?
Senior dev: If you help me move to my new desk, then yes.

In the end he didn't even help me.... U.U

Senior dev. "we need a reason why we haven't fully implemented social service signup yet"
Junior dev. "let's say it's new for us"
Senior. "great idea. Let's get this done."
..,
Now try to signup to pixabay using your Google account.... 😒

interview today

me: and can you tell me a little bit more about your development process? e.g. an example dev cycle from reqs to testing and review...?

senior dev interviewing me:
*gives frustrated/annoyed "why tf are you asking these?" look*
So, uh, we don't really use testing for these projects cuz it would make it harder to refactor later.
(and responded nothing else on the topic)

I left shortly after that.

As a senior dev with a house and a good salary im a bit afraid these young devs.

They are hungry, they are intelligent, they work hard, they want my comfort and my job!

I feel like im running naked through a forrest with a ham between my cheeks, chased by a pack of hungry wolves!

And im only 37...

Do you feel the same?

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.

That horrible feeling that you're holding the team back as a junior dev.

What took me two days of struggle, it took the senior dev a glance to solve the issue.

Literately took them less than 10seconds to complete the task which I spent two days both at work and after work of debugging and research to try and solve.

Why are they paying me to work here.

a JUINOR dev role job posting requires 7+ years of experience including 3 years of SENIOR experience, I feel like im in a movie...

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

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

Just over heard, Dev A was reviewing another team's code ...
Senior Dev A: "I don't understand this teams code. I hate WebAPI. Wish we could use X."
Senior Dev B: "Why can't we use X?"
Senior Dev A: "It's frowned upon."
Senior Dev B: "By whom?"
- couple of seconds of silence -
Senior Dev A: "X is not a Microsoft technology"
- few more seconds of awkward silence -
Senior Dev A: "X is magnitudes slower than WebAPI anyway."
Senior Dev C: "What? How much slower?"
- caught off guard..didn't know Senior Dev C didn't have his headphones on -
Senior Dev A: "Um...I don't know, that is what you told me."
Senior Dev C: "I never said that. I've never used X. I prefer WebAPI anyway, but both WebAPI and X use REST based protocols, I doubt X is magnitudes slower. Actually, I think you told me WebAPI was slower."
Senior Dev A: "Different paradigm."
- second or two of silence -
Senior Dev B: "What?"
Senior Dev A: "Hey, did you see on twitter ..."

Have no idea where he thought that conversation was going. Maybe he was hoping the other devs would dog-pile/attack the code. Pretty funny it backfired. His face when Dev C said 'I never said that' was priceless. Like "Oh -bleep- ..how do I lie out of this one? ...quick, distract with random words or a twitter post"

*Senior Dev:* Ah yes, we need to put try-catch in every function to handle errors and Logger.Log() at the beginning.
*Me:* Is not better to define a global error handler and use the stacktrace instead of doing all that?
*Senior Dev*: ...
*Senior Dev*: Is a rule here, do what I'm telling you.

Junior dev: Can I run lint on your codebase
Senior dev: hmmm
Jdev: Its a very nice code inspection tool
Sdev: Go ahead
Jdev: wow 50 errors
Sdev:

public void start() {
new Thread(this).start();
}

Senior dev my left arse cheek

My tech lead (or senior). I had been unmotivated with my dev life until I joined their team. He lit the fire in me by inspiring me and challenging me with my work. Sadly he left the team after 3 months but I'm thankful because he saved me from burn out.

why people around me act like dump. i have recently worked with this site, which is written in php.

customer: (yelling) my website is hacked, fix it immediately
me : ok sir, we will restore your site immediately

after finishing talk with customer. i have checked website, there is no sign of website being hacked. i have checked server logs and website for security breach, there is no sign.

me: your website is not hacked, sir. can you please tell me where you have seen hacked page.
customer: look at those pages

after seen that page i facepalmed myself. it's a bug, person who created that page just splitted string without using any multibyte function, so page is showing with corrupted characters. i fixed it and problem solved. i have told about that bug, to the person who created that page.

me: hey you have used this function which is not able to handle multibyte characters, you should use multibyte character functions for that one.
person: every characters are the same. we shouldn't need to handle that way.

he is actually a senior developer. who don't even know the difference between unicode and ascii characters.

Senior dev at job interview didnt know what is binary search. I was interviewed by him.

Senior PHP Dev touching C++ for the first time at age 32

I get a email every few weeks from recruiters for jobs that want senior level dev with 7+ years experience. In android, IOS, Java, or C#. My LinkedIn and personal site both state I graduated almost a year ago ...

How do you guys deal with "senior" devs that want to use you because they're not so "senior"???

Situation:

There's this SR Frontend developer that keeps asking me for "suggestions" to modernize the frontend.

This dev, was asked a very simple ticket involving some JS and CSS.

I had to do the JS and this dev modified a VENDOR CSS (that was all she did)

She logged 3d6h of figuring out the ticket and "doing a bunch of cross browser testing"

I logged 2 hours to see what to do and implementing the change.

Now she is asking me to join in a group so "we" can come up with a plan.

I hate how people bullshit their way up

That moment when your senior dev saves all dates in MySQL as a string human readable date

<senior dev turns around..making some small talk about the weather and such.. then>
Senior Dev: “Yea, I’m wanting to take my hard drive out of my desktop and put it in my laptop”
<I know his personal laptop is an older 13.3” dell>
Me: “You have a 2.5” laptop drive in your desktop computer?”
<gives me a very puzzled look>
Senior Dev: “Um…no.”
<second or two of awkward silence>
Me: “Well, a desktop hard drive isn’t going to fit in your laptop.”
<gives me another very puzzled look with a touch of annoyance>
Senior Dev: “It might work.”
<senior dev turns back around>
Why the –bleep- do people talk to me!? Now the rest of the day all I want to do is take his computer away from him…poor thing…that little guy has no idea what his owner wants to do to him .

My co-worker, still studying but working as a "senior dev", just decided that we don't need a test/staging environment anymore. We just "validate" (we also don't use the word "test" anymore) newly created features in production.

Makes absolutely sense...

Thank god I have a new job from february on!

The senior dev in my team wants me to convert all the lambda expressions I have written to anonymous inner classes. He says it will increase the code readability.
IT IS NOT MY FAULT THAT YOU CAN'T READ LAMDA EXPRESSIONS!!!!

It's like the dev has something against the new features of Java8

Junior Dev me: ok boss, coding is basically done, just need to do some more system testing.
Senior Dev: fantastic let me take a look.
(3 hours later)
Senior Dev: ok so I've made some small changes and pushed, could you pull my edits.
me: sure
(pulls changes)
(EVERYTHING Is changed)
(try to compile)
(doesn't compile)
Me: sorry, it doesn't seem to compile for me
Senior Dev: I never tried to actually build it, it's only a small change
me:

I dont know what to feel anymore.

Got hired directly without an interview into 'Data-analytics' department in fortune 500 company. This is my first job. Got hired because this company want start a website that cost millions.

Even though I am junior, I can see that this company has no idea about software development at all. No git server, no code review, no quality assurance and no proper workflow. No senior developer to guide us (junior dev) too.

There is one 'senior' consultant that work on automation project here but he just focus on his work and don't help us directly too.

The contract is about 1 year. Still got 11 months to go :/

Damnit! Every time! Our UI Dev asks us to change the API every time he wants something different!

The API is backend -> business logic. You don't change your business according to what fucking color you want on your site!

Sad part is since he's senior I don't want to tell him off

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

Dev: The server is completely down right now. Nobody can access the application, we need to divert some resources to horizontally scaling our app.

Manager: Hm, this was not in the schedule. I need to consult senior leadership on what to do about this. I don’t want to be held accountable for making a decision on this complex and highly nuanced situation.

Dev: No need, I have a solution. Just need a week to build/test/deploy the ability to horizontally scale.

Manager: But that will cause delays to new features.

Dev: New features don’t matter if the app can’t even load.

Manager: Ok you can implement your solution but it can’t take any time. I need those new features out.

Dev: ???????

senior dev cw: find this bug, would you?
me (20 mins later): found the bug, fixed, tested. btw it was bigger than we thought and affecting all users. shall I push?
cw: not yet, let me look into it.
(next week)
cw: find this (same) bug
me: -.-

The dev usually sitting next to me is on vacation. Our senior dev is on vacation. Team analist, on a plane to a Greek beach as we speak. Both architects the company employs, gone for another two weeks or so. Lead analist, you guessed it, on vacation.

I'm enjoying the peace & quite for now but god forbid I run into any problems these next coming weeks.

Senior developer just showed me a "competitor" that seems to do things waaaaaaaaaaaaay better than us on his web site and was telling me:

Senior: damn, I wish I could figure out how they do this. I've been trying for so long...

I write the URL on chrome with dev tools open and literally the first thing that comes on the console is a nice greeting from their devs with links to they github repositories, ends up they are open source...

And now I'm here thinking "WTF!!!! WHY ARE WE NOT DOING THINGS THIS WAY?"

Intern: what’s my purpose ?
Senior dev: you write unit test for my code
Intern: 😓

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

I Remember what my senior told me once:

"You know you're in the wrong job when you see source code filled with comments written by ur senior dev scolding other devs for code fuckups"

My Favorite Senior Dev: Hmm, I don't understand this error.

Neighboring, Competent SQL Developer Coworker: What does it say?

Senior Dev: It says, "Cannot insert the value NULL into column 'person', table 'PEOPLE'; column does not allow nulls..."

*5 minute silence*

Sprint planning meeting discussing UI:
Customer: - Wouldn't that confuse the user?
Senior Dev: - Yes but it will take less development time.
Me (junior): ...

A senior developer would ask me to drink in the bar where we talk about dev and non dev related stuff, almost every night after work

A few years ago we had a pm/senior developer join us and he became my superior. His portfolio was all Microsoft Dev examples and his only answer to any request was yes two weeks.

After a couple of months I had to leave the company because I was working 14 hour days to keep on top the work the muppet was piling up

Five or six years ago I was mining bitcoin. I was among first miners. I had a lot of bitcoin. I sold most of btc for 1$ or under to buy laptop so I can code. Bitcoin price was 1200$ at one point. I paid my laptop 300.000$. I am now senior dev. Fck money.

> be new in a big-ish company
> be working next to a senior dev, who's been working on The Project for 5 months now (15 yrs in company)
> be asked for halp
> senior dev didn't know how to use git push
GIT PUSH
> be Joe's terminally flaccid dick

After arguing about which framework to use....

Senior dev: we could just write it ourselves
Room: yeah, yeah, yeah...
Me: (quiet) noooooooo....

This senior dev of mine is so good that he always reminds me to finish the bugs and yeah, fixed it, and sent the codes to him. The hell's wrong with him is that he hasn't upload the codes i sent to him.

this fucking senior dev, just send the following messages:

pull development,
Did yarn install
now yarn dev does not work.....

BRO: READ THE FUCKING ERROR MESSAGE!
It's plain English!

Seriously wtf.

Here's how I describe my workplace:
- a mid dev that will stay mid forever
- a senior but with junior skill
- a mid but actually a junior
- a verbose dev, people having rough time trying to understand her because her explanation is always blown up
- a PM without enough technical skill
- a dev with personality like a moody teenager
- a contractor but acting like a customer

Did I miss anything? 🤔

Interviewing candidates for a middle/senior dev position:

Me: Imagine you have this button, but whatever it's doing when you click it, it's taking too long to load. How would you improve the speed performance?

Candidate: Redis!

Me: Okay... but how would you find where the bottleneck is?

C: Redis!

Me: How abo-

C: REDIS!

*senior dev comes over to my desk*
"Your code is so wrong I didn't even bother to comment on the review." He proceeds to lecture me about why the code that I modified (a 2 year old file I included a tiny helper module in) needs to be rewritten.

when a senior dev says your code is messy just after you finished refactoring 😞

Being a dev intern is so hard! The company expects me to have knowledge as a senior developer but with a stipend of a janitor! :(

I'm a first year MSCS student, and working in a startup as a part-time engineer. The founder insisted to mark me as a "Senior Engineer" since I was leading a team of 3 student programmers. Deep in my heart I knew I'm at least 4 years away from competent enough to own this title... Today, I got an invitation from a well known company asking me to join their new team as a Senior SDE II, and I suspect this is the reason. I don't know what to do right now... Frankly I only want to ask the HR if he’d consider adding me as an intern instead LOL. I have no working experience in large professional companies before, and I think I will embarasse myself if they interview me about my experience as a "Senior Engineer" which in fact I was merely a Junior dev...

The `sed` command skills of my senior dev (team lead) is equal to every skill I (junior dev) have ever acquired until now as a programmer.

Just amazing !

When you are told to copy some functionality of the global code for a module youre building, and in code review, the senior dev team gives you 42 errors to fix on their own global module

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

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

That moment when a senior dev says "let's use Wordpress AND Laravel for 1 website".

The biggest hurdle I overcame on my dev career was coming back to a full time job after a few years spent on a "hippie phase" combining work as an artisan, content developer and editor, and just a few freelance dev jobs. It was all a struggle to start again thinking of myself as "junior again" surrounded by people ten or fifteen years younger than me. But I kept myself over the tidal web and here I am, a Senior again.

Picture a small product team, the dev side of it has 1 tech lead, 1 recently promoted senior dev, 1 junior dev.

1 - Offer your tech lead a severance package
2 - Hire a mid-level and a junior dev
3 - Give the product lead role to someone in their mid-20s that has no tech or project management background
4 - ???

The next 6 months are going to be interesting ones...

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

After 1 year of working as android dev and coding in java, finally switched to another startup where everything is in Kotlin where I will be the only one maintaining that project.

Me: This code has almost no comments
Senior dev: Code is pretty self explanatory

FML

At least she spent 4 days with me and walked me through the code, so I'm not totally lost which is great!

When you're working on something all day and then the senior dev swoops in and answers your question in 5 minutes.

Started a new job as a senior dev but with a framework I've never worked with and I just feel like I'm slow AF and just not qualified for the job. I'm sure it doesn't help that I'm greiving my dog that passed last Tuesday.

senior dev told me yesterday - stop thinking like a manager, look at the big picture!

shouldn t it be the other way around?

A 'senior' dev just questioned us (by question, I mean scold) when I suggest writing some additional information regarding db patching scheme of our project on our Wiki, just thought it might be useful for other possibly new devs later.

Apparently that would be 'spoon- feeding' them and it is totally NOT GOOD.

Smh.

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

How old are you?
I sometimes feelike the old fart in here.
I am turning 39 on Halloween :)

Interviewed for a Mid/Senior developer role and finally got feedback. The company feels I'm not experience enough for the senior role but think I'm a good fit for the company. Bad thing is they don't have any entry level positions available. I honestly feel like I am ready for a mid level role and maybe even a senior role. They say to keep considering them while they try to get approval for entry level position, but this is a massive company and who knows how long that will take. Recruiter said it's not a no, just not a right now. /:

Oh and going off my last rant, I found out that the senior dev was wrong about set interception being '|' in python, I found out that it's actually a method called interception(set). So even the senior dev didn't know off the top of his head. /:

Have some projects in GitHub but my biggest one is a private repo I'm doing the entire backend and even frontend. Can't share that repo or share details because it's a project a friend (his idea) and I are planning on releasing. (:

Overall feeling pretty bummed because I was looking forward to steady work that'll improve my skills even further... I'm self taught so it's a bit tougher to land interviews because of the automated process most companies have with resume filtering. ):

Going to keep doing small contracted projects until I land another interview. In the meantime trying to keep my spirit up. (:

I thought I was a senior dev. But reading devrant, I realise that I know fuck-all about development.

Just got yelled at by by a senior dev. I know I am not the best developer but...I am depressed now. I wanna be better and prove myself. I admit I am distracted way to easily but I need help bad. Idk how to earn back the respect of my coWorkers.

Conversation in a debug meeting, after a series of confusing failures:

Senior dev: “This is stupid”
Junior dev: “Me too”

when my senior dev told me my logic is awesome that I can be a good programmer

Decrypt api responses in an iOS app which my “senior” dev thinks it is more secure to encrypt responses in stead of setting up a proper SSL cert (they use plain http to save money 🙄)

They disable the encryption since it does not function as we wanted and set up SSL instead🙄

I applied for a Senior dev role at a local company. I am perfectly qualified for this role with over 10yrs experience. Just talked to the owner and their salary target is $80k. FOR A SENIOR ROLE. Ok, dude, you get what you pay for.... I guess I'll keep looking.

*sits at work*

Other dev has a problem, Visual Studio keeps crashing etc.

*Senior dev comes over*
asks what she's struggling with.

she explains it to him, saying it's possibly a port problem.

senior dev goes "ah, yeah that's just gonna take a second"

*senior dev sits down and rolls a new port with two actual dice*

I fucking died.

It's unbelievable how many senior software engineers there are with 2-3 years experience within the industry... damn boy, you just became intermediate, if you're still not a junior

I kinda hate to admit it but they were right. Data structures and algorithms are kinda the shit and you should try to learn and appreciate them. Not just so you’ll use them. But in that learning them helps you become a better problem solver.

There’s a self taught dev that my company works with for really bespoke applications. A senior dev that works with him and helps manage the development process told me that the dev in question doesn’t really know how to implement the finer details. Very telling indeed.

I hate dev politics...

PM: Hey there is a weird error happening when I upload this file on production, but it works on our test environments.

Me: After looking at this error, I don't find any issues with the code, but this variable is set when the application is first loaded, I bet it wasn't loaded correctly our last deployment and we just need to reload the application.

Senior Dev: We need to output all of the errors and figure out where this error is coming from. Dump out all the errors on everything in production!!

Me: That's dumb... the code works on test... it's not the code.. it's the application.

Senior dev: %$*^$>&÷^> $

Me: Hey I have an idea! If test works... I can go ahead and deploy last week's changes to prod and dump those errors you were talking about!!

Senior Dev: OK

Me: *runs Jenkins job the deploys the new code and restarts the application*

PM: YAY you fixed it!!

Senior Dev: Did you sump put those errors like I said.

Me: Nope didn't touch a thing... I just deployed my irrelevant changes to that error and reloaded the application.

This happened at the beginning of my first job:

Me: I want to clarify some things that wasn't specified in my task. I want to see if I need to do them and how I should solve it.
Senior dev: Don't worry about it. If testers pass the task back to you, then you do it. Just do as it is.
Me: 😓

Hmm. Seniors have the half working experience as I do and I am the only not senior one in Dev team.

I adapt code only to "taste" good for code reviewers, but they allow themselves to commit without caring and just saying :"oh unit testing is boring"

Enough with the kindergarten. Time to prepare myself for the next job.

Here at the client site everyone uses Windows 7, since this is not an IT firm. They make jewellery. So I don't blame them.
The problem is their in house dev team are also forced to use Windows.

Today someone from their dev team was with me for a new project. Their senior guy sent us a mail mentioning that the project code is on AWS EC2 instance and we will have to SSH to see it.
I checked the code on my MacBook with SSH and copied it to local using SCP. The dev guy was seeing it in amazement. I asked, what's it?

He just asked, "You don't have to use PUTTY" 😮

I smirked 😏

So, I guess this is some good news...

I'm currently on annual leave, speaking to few colleagues and one of them mentioned that the Snr. dev mentioned in my previous posts has handed in his notice.

We also have a new line manager, so hopefully I'll actually be able to sort out technical debt, implement the changes I want to implement without being blocked off or PRs closed without notice.

So I guess this is a win, also means a new Snr. dev position has opened up so you bet I'm gunning for it when I get back.

Nobody reviews my PR into test branch

The only guy who reviews it is the new senior dev who isn't yet used to how the company works, leaves comments about useless stuff and doesn't fucking approve

Jesus fucking Christ

Not a fight I was involved in but one I observed. A junior dev on my team and a server ops guy had major personality conflicts. One day the server ops guy had enough and physically went after the junior dev. I was senior but still pretty new to my own career and had no idea how to handle it. Server guy got fired soon after. I was glad I didn’t have firing power and that he didn’t even report to me anyways.

TL;DR: When picking vendors to outsource work to, vet them really well.

Backstory:
Got a large redesign project that involves rebuilding a website's main navigation (accessibility reasons).
Project is too big just for our dev team to handle with our workload so we got to bring a 3rd party vendor to help us. We do this often so no big deal.
But, this time the twist was Senior Management already had retained hours with a dev shop so they want us to use them for project. Okay...

It begins:
Have our scope / discovery meeting about the changes and our expected DevOps workflow.

Devs work Local and push changes to our Github, that kicks off the build and we test on Dev, then it goes to Staging for more testing & PM review. Once ready we can push to prod, or whenever needed. All is agreed, everyone was happy.

Emailed the vendors' project manager to ask for their devs Github accounts so we can add them to the project. Got no reply for 3 days.

4th day, I get back "Who sets up the Github accounts?"

fuck me. they've never used Github before but in our scope meeting 4 days ago you said Github was fine...??

Whatever, fuck it. I'll make the accounts and add them.

Added 4 devs to the repo and setup new branch. 40min later get an email that they can't setup dev environment now, the dev doesn't know how to setup our CMS locally, "not working for some reason."

So, they ask for permission to develop on our STAGING server.. "because it's already setup"... they want to actively dev on our staging where we get PM/Senior Management approvals?

We have dev, staging, production instances and you want to dev in staging, not dev?... nay nay good sir.

This is whom senior management wants us to use, already paid for via retainer no less. They are a major dev shop and they're useless...

😢😭

Cant wait for today's progress checkup meeting. 😐😐

/rant

So I've been maintaining our company's web products for a few years now with a great senior dev, but why would it ever make sense to have a

bool somebool = returnsBool();
if (somebool == true)
...

WTF?!?! I still fine them in the code to this day.

Be me
Newb Ui dev
New job , learn c#
Become xaml pro first
Newb ui dev
Today building menu
It's breaking ree.
Ok I go through an fix
Part fixed
No reee
Commit build for other my senior dev
We have online compiler
Receive build fail
Reeee
My code is good
I'm sweating bullets
I call other dev
Yo I f***** up
Help me
Go figure it out ... reeee
I go spend 40 mins
Don't know what is killing build
Reeee intensifies.
Going to shit diamonds
Reeeeeee
Other dev, lol my bad I turned on somethin that break ur build. Your not fired congrats.
Reeeeeeeeeeeeee

Hello! I’m from Nigeria(Africa) and I have two Job offers in Lithuania and Netherlands as an intermediate level dev (software engineer, no senior or junior attached). I am still early in my career, 1.8yrs professional experience. Which would you advise I take and why? Assuming you don’t know how much pay is. Thanks!

Imagine being a senior dev with a green junior that says: "Well maybe there is a better way and I just don't know"

and you say:

"There is, I'm telling you"

only to continue on discussing it more.

Fuck me I'm pissed. This sprint, my tech lead has been away and a senior dev has been covering for him. We plan a load of work and distribute stories and we churn threw it quite well. However, my senior dev says let's not deploy until all the works done. I was like, how is it going to be tested? He was like well it will be fine because it's all one test. Bs. We now have 2 days left, tester is getting stressed because they don't know what to test or what's been finished. Sc