Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
New kid came to me in my break (while I was playing LoL) saying I should start coding (he had no clue what my role within the company is).
Said that if I won't get a career in league, I could just (as if it's done in a few minutes) learn coding and make a website with thousands of users (as if that is just done like 1 2 3).
Then with a big grin on his face he proceeded to say "if you ever have some issues with making websites, I could just come to him and he can teach me the basics of Javascript, HTML, CSS and PHP".
So I said: "and who are you?"
He told me his name and what he is going to do within the company.
So I said with a big grin on my face: "Ah, so you're the new kid the boss told me about, nice to meet you, from today on, I'll be your Senior."
I then saw his big grin disappear
then with a big smile on my face I proceeded to say: "If you ever have some issues, please come to see me and I'll be happy to teach you the basics of Javascript, HTML, PHP and CSS"
Then he walked away :^)26 -
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 *11 -
So apparently my boss knows the "new senior dev", which I will call 'B'.
Backstory:
Program which I worked on for a year, my baby, is doing fine. Suddenly B decides to update it to "standardize it", against my suggestions/protests. Fastfoward to the following morning, I get to work and there's a bunch of emails from B waiting for me. I'm like "Well there's a meeting in an hour, so no point in answering all of these". 30 minutes go by and then boss shows up in my team's area. Asking for me.
(I didn't know this at the time, but apparently boss knows B. And thinks that B is this amazing programmer and super nice.)
According to boss, B has been trying to contact me all morning about my program failing.
It is at this moment that my mentor stands up to defend me. She basically tells our boss that B is a piece of shit. And I'm just loving it, ++ to mentor for bring awesome.12 -
TL;DR: Got a really horrible supervisor temporarily fired, maybe permanently fired, got a laptop, and realized that senior devs are amazing when they stand up for the little guys
Omg... I love my coworkers!!! So like, I'm an incredibly shy dev, like, I only managed to get my internship purely because of my familiarity with c#, Android/UWP app development (although never apple, which you can read about in my last rant lol), and the API Management framework that they were using, so, long stories short, I'm insanely shy and I get anxious quite quickly in social situations, that'll be important in a bit. Anyways, so, in my previous rant (my first one actually, it was "that" bad...) I had a run-in with a rather unfair supervisor situation where he expected me to work on an iOS app without a Mac machine.
Yup.
So, this is currently a little bit before my shift end, where I'm anxiously trying to get a MacOS VM up and running to be able to copy paste some psudo-code so as not to get in trouble, which is when the senior dev of the team walks by and sees me tearing hair out of my head and being really sad. So what does this god amongst men do?
He comes over and asks me what I'm doing.
Now, I didn't actually notice him, so when he asked me, I was insanely jumpy and scared that my supervisor would appear and be mad at me for not having things done, so I kind of half scream half yelp when he says something, so now he knows somethings up and he acts kind of like I'm an injured deer and slowly asks what's going on.
So, of course I tell him everything that had happened and how the supervisor got really mad about me not being able to develop iOS apps due to not having a Mac, and his expectation of me to get it magically working and getting to work on my module, and the selenium portal automatization, and after a couple seconds of me rapid fire nervous squirrel-like explanation, he holds up a hand and says "He what?!!!!? God dammit, how the hell are you supposed to do that? Jesus, you were supposed to get a company laptop when you got here, where's that??? And if you don't have that then how the hell were you working on the cross platform portion? You need a Mac machine for that, so let me get this straight... You've been frantically trying to find a workaround so that AS (let's call him AS for asshat supervisor (missing an s)) doesn't get mad at you... Who the hell... And this fuckers in charge of the interns??"
He was incredibly pissed off at this point, like, REALLY pissed off... But-
This man had just spoken miracles to me.
Mother...
Fuckin...
Miracles...
So I do what any self respecting intern would do, I start cry laughing and hug said BSD for a quick second (badass senior developer), and I say yep, pretty much ;-;.
And queue AS walking into my workspace and saying
AS- "are you done with the iOS a..."
BSD- "You've got to be kidding me, shut up for a second and sit down"
AS- "?" *Sits*
Me- *hides in corner and cinches up hoodie*
BSD- "Excuse me, but what did you ask benlion to do?"
AS- "Um, I simply told him to start working on the Xamarin app"
BSD- "Yes, but according to benlion, you angrily told him to start working on the Mac portion... Let me ask you something first, why would you do that? It's rude and inappropriate to be hostile to anyone at the workplace, in fact, if he wants to pursue to matter, you can get demoted, actually, if he wants to pursue it, you're fired, and there's no way I'm letting you get a management job again"
AS -"Wow, did benlion really say that? He's obviously lying due to his dislike for me, BSD, it's rather unfair to take his word over his superv..."
BSD-"Oh you did NOT just go there. That's it, stay here. And benlion, come with me." *Points at me*
Me- *Terrified out of my mind, almost to the point of a nervous breakdown because of the argument that I had started* "O-okay o_O"
Long stories short, we come back with his supervisor and he is now relieved of his duties temporarily while this whole thing gets settled...
Oh, and I get my Apple Laptop tomorrow ^-^ so I'm really happy, albeit kind of sad that its my fault that AS doesn't have a job right now ;-;, but he did yell at me and expect incredibly impossible things of me, so, not as bad as I might feel.25 -
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 area5 -
Asked my senior why our software is crashing unexpectedly. He told me that sometimes it is affected by cosmic radiation.
🤔12 -
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.9 -
You know you are a senior developer when you go to stackoverflow with only goal to answer questions.5
-
Yesterday Mr Senior told us that "it's not possible to do that".
I (30 years younger) replied I read about that possibility in the manual.
So he challenged me to do it, laughing at me.
Today I went to the office really angry, I put the headphones on, with the song "Suicide Silence - O.C.D." in loop, and after 5 hours I solved the "big problem".
So, go fuck yourself Mr Senior, and RTFM.
Damn, I'm still listening that song.19 -
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.15 -
Team lead dismisses my request for promotion to senior, "need more experience", 3 hours later get job offer for senior position5
-
🤣🤣🤣
Somehow, my boss got his son, 19, working in a team of developers last week.
Son: i got ton of money and i dont need to do this. i inherit lot of properties from my dad.(trying to sound funny, superior, and boasting of his inheritance knowledge he might have learned in school during java class probably.)
A guy in the team: No you dont. You are like us.😎😎😎
Son: minds his own business now.
Damn that line made my day.
🤗👏👏👏👏
++ for this dude for insulting morons like this at work.
I may have to remove it on boss request if he see it. But for now hit as many ++ to show that idiot no body likes people like him.8 -
At my old company one of my colleagues introduced async / await into our csharp code. He created interfaces and showed us a great structuring of his code. Sadly a few weeks later he left the company, because of personal reasons and a bug appeared in his written service. Our senior developer took the issue and complained for like 1 week. That you can't find anything, that interfaces are useless, that async / await is slow and sucks and that we should stop trying to bring new structures into the code base and do things the old way. In the end he deleted all the great things that my colleague introduced and wrote bad and smelly code.9
-
---- Startup RantLife ----
A senior developer joined the team, let's name him Bob, and this guy is really good no doubts about that.
He made suggestions, some improvements, but Bob is always waving his hands and says out loud that some part of the code base is really really bad.
I kept quiet until one day I had to pair with Bob to check a feature. Guess what happened, as usual, Bob clenched his fist and start pointing that this code is super ugly.
So let's check the history of changes and boom, Bob was the main writer.
That moment, I was completely silent, trying not to smile as Bob came up with an excuse, he never admits that he is wrong, now he needs a scapegoat and he starts blaming the process, the planning...
I believe that being humble and saying sorry is a quality that it requires time to develop.
So don't be like Bob, please :)14 -
Look... I know I'm just a newbie. I started a year ago as a junior. Sure. No one wants to do code review, so I got chosen to do it. People don't like it when their code gets criticised. And you know what? I get it, I should probably be a bit nicer with my comments. I should not suggest I'll make a fork and split internal library into two streams if things continue this way. I should not ask questions that can be understood as me being passive-aggressive.
But holy fucking shit, you're a senior developer. Don't treat Java as a fucking scripting language. Don't have a method that has 600 lines of code, because you're repeating the code! You've already copy pasted this shit, and modified it slightly. Like, couldn't you have created some architecture around the code? How can a senior dev copy-paste code?
Oh and why the fuck did you create a new utility class for functionality I already provide? Look, I admit, yours is a lot better, ok? It has extra functionality. But why the fuck didn't you enhance my utility class? Why did you create a new one? Did you just not want to touch my code, or did you not see it right below your newly created class?
Am I the only one who fucking cares about maintainable code in this company? When I got hired, I was in tears by how frustrating a lot of the things were. No documentation anywhere, not even fucking comments. No processes in place. Want to do something? Source code is your documentation. Fuck you! I busted my ass of to force everyone to document every little bullshit, to re-factor their MRs that I reviewed, and I won't let even a senior fucking dev pollute the code base!
Fuuuuuck... Me...2 -
First broken rule - Publish on Friday
Second broken rule - Delete without backing up
Major screw up - Main folder deleted containing several sites
Major problem - Cannot find anyone on the server team for backups
3 -
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?!3 -
I was expecting a 4th interview this afternoon for a position as a fullstack elixir developer.
Got a response from the CTO.
'Even if you pass all the tests with success, we could not go further because you're a junior and we're looking for a senior'
Well, dude, you've seen me 3 times and didn't understand that I was a junior ? My CV is not enough explicit ? It's written at the top of it...
So after a motivation interview, technical test, technical interview and Phoenix framework interview, they only realized yet the plot.
Good luck for your seniors to pass their knowledge to other seniors.18 -
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.15
-
Yes, senior developers get stuck just as much as junior developers do, the difference is that they get stuck in places that junior developers can’t even access. That is partially because senior developers are expected to do so much more than just simple coding, they need to also grasp and untangle client requirements, communicate clearly and thoughtfully with the team, be some sort of guiding/mentoring/leading figure, make sweeping architectural decisions, and so on and so forth.
A junior developer is struggling with making relevant columns of a table a nice shade of purple. A senior developer is struggling with making sure that implementing new client requirements will not have a destructive impact on the current infrastructure, there will be no regressions elsewhere in the system, tries to pinpoint what prior assumptions the new stuff breaks (it inevitably does), and how to reconcile everything.5 -
Just looking at code, my colleague ("Senior Java Developer"), wrote...
if (process == "null") {...}
As you can guess, process is a String.
I just don't know what I can tell him. It's just so wrong, in every possible way...11 -
What a week
On Monday I was promoted to senior and on Friday the other senior in my group was fired for gross incompetence.
FEELS GOOD MAN8 -
Recruiter: “can you write your own framework?”
Me, after considering for a good minute: “well, I am kinda starting to automate lots of things so I guess if I wanted I may be able to... for sure I’d learn a lot along the way...”
Recruiter: “very good!”
Me:”wait, why would you want that skill?”
Recruiter: “our customers want custom code”
Me:”so you write a new framework every time?”
Recruiter: “ah you have also experience in [x]!”
Some people scare me 😟11 -
*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?4 -
A senior developer come to interrupt me.
Senior developer: blah...blah....blah about this concept...... that concept... So, any new things you learn lately that you would like to share?
Me: I am learning back C++
Immediately he stop me and said, "Why did you learn C++? It is obsolete, no one use it anymore"
Me (in my head): But, you just said what I learn. It doesn't matter if its obsolete or not. Infact you are wrong, C++ is not obsolete anytime soon. I was about to share on webassembly.
Senior developer: So, would you like to join me in a short sharing session this afternoon.
Me: No thanks, I am really busy (just want to avoid at any cost)8 -
"Mature codebase"
"Our entire team are senior devs"
"Almost everyone that worked on the project is still here and available, so nothing's lost! We can ask whatever we need to."
You would think this would mean the code was clean and easy to read, and you could ask the person who wrote it for help. But. no. It's kinda the opposite.
Here's an example:
I'm trying to write a mailer, and I have no freaking clue how to get it working. I talked with two of the more senior devs, and both assured me it was very straightforward, and then walked me through the quite complicated mailer structure and got lost. The first pretended not to, but glazed over a few holes in his tour, and said I could figure the rest out. The second one ended up admitting that he's totally unfamiliar with it -- his last commit on a mailer was from about 8 years ago -- and doesn't know how to get it working anymore.
So, I'm on my own.
I wrote a super basic mailer for debugging (no idea if/how it actually sends a mail, but I think I can construct one?). But whenever I call the mailer, it gets run twice? Somehow? Apparently I need to start a bunch of daemons to get that part of the system to work. Which is cool because they don't work fresh out of the repo. Got some further help, and now my ostensibly working code throws errors for an undefined var that i'm not even using, and to make it easier: without a backtrace. joy! There's so much inheritence and extending and including going on that it's going to take me hours to track this down. ugh.
I'm keeping my paystub in front of me for some desparately needed motivation.13 -
While debugging some java code by our Senior Architect, I found this gem: 5000 padding done manually.
PS: Jr Developer here.
7 -
My boss has no idea what he is doing. Scary for a senior programmer, with 20 years of experience. The guy keeps calling methods statically, in a object oriented project. And can't understand why it won't work.4
-
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!!2
-
Hey junior... when I'm asking a question it's not the answer I'm looking for.... It's your thought process! Just tell me the things you will not do and we can take it from there!4
-
Been reading devRant for a while now and I have to say I'm sad about the way the future of the software engineering looks like. Everyone seems to have a lot of hatred towards certain techniques and/or platforms and sad to say, but you are missing a lot.
I have been in the biz for around 15 years and have worked on Win, Linux, Mac, Unix, Symbian, Embedded etc. using all sorts of tools and languages and I must say it has taught me a lot and given diversity on my career and I hope you could also open your mind and start educating yourselves. Theres a world behind your bubble!
Peace and love!13 -
Dafuq... My new position label is Senior Software Developer.
I do not identify myself as a senior even in my wet dreams.
I'm confused.22 -
Senior showing fellow intern what SQL injection is on the app the intern created :
Senior : "then I hit enter and the query get executed and...
Intern : "don't you dare hitting enter!!!"4 -
No a rant : today one of the top senior told me he liked one of my functions. Thank you so much sensei!1
-
We have a developer that is known for rejecting PR during code reviews.
He sent me a message and asked me to come to his desk to discuss my PR.
He mentioned that he didn't like my solution and suggested to rewrite the code together.
So far so good, he is a senior developer and I'm sure I'll pick something from the pair programming session. He went with his approach and faced some issues that led us to my solution after nearly 2 hours.
I'm not angry because this scenario happened at least 3 times but how do you guys deal with senior developers that are stubborn?7 -
Is there a lot of people in the same boat as me?
I'm a self taught guy. Never in my life had I a senior developer i could bug for answers. Every little bug and inconveniece i have ever experienced - left alone to cope and find solutions. I just feel like sooo burned out. I have some large complex system questions building up and googling doesnt give me the answers anymore. This is frustrating. I'm supposed to be a mid level developer, but I'm acting as a senior to one of my colleagues even though I have so many questions and doubts in my mind. I think I developed a lot of plot holes in my knowledge and I have no real way to know which are which. I feel I dont know so much. Fuck. Where do I go from here?16 -
Today a new person joined the team.
Started bitching about the entire team for not having documentation for our already written code and software.
Asks the manager for a new task that he can take up so that he can write documentation for all our already coded works.
Manager says Go On.
Troubles me with 400 questions every 3 minutes in the name of Knowledge Transfer for writing his documentation.
Sends a proud mail to the team for writing this new documentation that no one else had time to do.
He is a newbie and had no other task to do anyway.
I seriously don't know if I should feel proud of him, for writing new documentation,
Or if he's doing this to defame me.
The team is filled with snakes.15 -
A senior engineer with about 8 experience in my team and company for almost a year now. Believe it or not, still hasn't setup local dev environment.
Every time we ask this person to set it up / refer to guide in Confluence / or just use the docker image the person says ok.
Starts sending code for pull request. The code would not even compile in most cases just from a quick scan. When questioned how was this tested, answer would be more or less 'oh my local setup not working, could you test it out for me.'
Doesn't know how to write tests. Fairly recently instead of storing string values in a list, (I swear am not kidding) decided to come up with 20 string variables.
8 years plus experience! I think this is retarded even for a fresh grad.9 -
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...5 -
The senior programmer at work commits so rarely that in 3 months I committed more than him in 3 years (e.g. 0 times in September)...
What’s the point of having a repo on bitbucket if most of the time the latest code version is only on his machine?
And why I have to recreate and repopulate the db every fucking time because he made so many changes to the structure, which of course conflicts with mine?5 -
A coworker that is producing incredibly bad code and refuses to learn new stuff was declared "senior developer" by my boss. And me with over 20y experience? I am just a junior.. and have to clean up his mess all the time. I guess it is time to find new job.
5 -
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!"
😭4 -
My boss just asked me to participate in a conference call to help an external senior dev implement some stuff/tool into our website.
My boss suspects that he doesn't even know Git...
Let's see how that whole thing will turn out.
My boss told me that he looked at his code and it already looks like an abomination of PHP...
It is enough that my boss usually writes shitty spaghetty code.
I will not sleep well this night.1 -
The fucking hubris on some people... If you don't understand git, in a shop that uses git, how in the name of fucking odin's nutsack do you think you're qualified to be a senior dev? I'm not talking understanding the internals of git, I'm talking knowing WTF a branch even is! Oh, I know, its because you eat lunch with the bossman! Cronyisn is alive and well folks! Now I gotta fix all this shit, or its my fault...3
-
I'm starting my first real/big project! I'm going to program a discord bot for my senior project with Python and I'm gonna have to do it in 25 days. the goal is to get it done in 15 and polish it more from there.4
-
Our junior programmer is stuck in a do-while loop. He starts with a normal question, and then each question after will be "But Why ?", until I am ready to throttle him, or I run out of memory.5
-
- My task is dependent on a senior's.
- I wait for him to finish it for couple of days.
- Once done I went to test it, the value doesn't get updated, it turns out the value is static ... WTFFFFF!
- I assign him a bug task to fix it.
- My task is still pending.
- After couple of days, he assigns me the task of fixing it, with the excuse that he's busy.
Are you fucking serious !!?? What have I done in my life to deserve such senior? all I want is someone I respect and learn from .·´¯`(>▂<)´¯`·. .·´¯`(>▂<)´¯`·.5 -
My interviewer described the team as very experienced, senior algorithm people, so to make sure we don't waste each other's time, I said I don't feel like a senior. He went silent for a bit. And then he said "It's so refreshing to see some modesty in our field."
😂6 -
One day, I spoke to my team which yubi or nitro key to get.
Senior (s) : but what do you need it for?
Me (m) : for encryption. And securing our password managers. Stuff, I guess.
S : encryption is not gonna be a thing. It hasn't and it won't.
M : *leaves*
I've been so baffled I couldn't cope with the situation.
A few weeks later I left the company. There were too many of such people and those products.3 -
When I was a graduate I often had to do proof of concepts and one had to be done by the weekend, I'd only been given it on the Wednesday. After a few sleepless nights I had it working or so I thought. On the Friday afternoon the CTO had a look at it and spotted a bug, he told me about it and I stayed in the office until about 10 when I finally managed to get some kind of fix in place. I emailed him told him I thought but was working and shouldn't happen again.
A few hours later no response I get a phone call from him screaming, shouting and swearing calling me useless and a waste of space etc. Etc. To the point I logged in desperately trying to fix the issue in a very hastily written integration and ended up having quite a major panic attack woke up on the floor and immediately went back to work. On the Saturday morning one of the senior Devs logged in and managed to fix it in the database and everything went fine in the end.
I went into work on Monday fully expecting to be fired from the way the CTO was speaking to me, I went to my line manager at the time and he just said don't worry. I left it in his
hands and things went back to normal. That call put a pretty serious dent in my confidence for years, but I learned a few valuable lessons which I stick to today.
Never work on serious shit after 6, use a second mobile for work which is turned off at 5 o'clock, properly test all fixes and always ALWAYS have someone in between graduates and senior management because honestly they can't handle the shit that's flung from above.1 -
!rant
I met a senior node.js developer for the first time and had a talk with him, really, I did not know how junior I was until I talked with him, everything he told me about node was just amazing, I mean, I describe myself as a good developer but he has the knowledge I would like to have someday, I loved node since I met the runtime and I follow many node/js programmers that are really good at it and I admire them, but having the opportunity to have an hour and something talk with one of them was really amazing and gave me more reasons to succeed and how to take that place, well I have to say this as per what I've already write -> nohomo5 -
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!3 -
!rant
Just overheard a senior engineer say to a junior "I dont tell you to move, I tell you to MOV because you're as stupid as a computer" wow that hurt9 -
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?9
-
Idiot people...
Today someone asked me how long I programmed for iOS, Told him I started really mastering iOS development since Swift was released, as I didn’t really focus on Objective C. He told me if I need any help, just ask him as he develops for iOS since two decenia... He calls himself a Senior web developer. First of all what has web development to do with iOS? And how the f*** can he program for iOS if it didn’t exist at that time.
It’s not because I’m a student I’m that thumb...
learnt the lesson not to believe everything everyone sais.10 -
Hey guys how do you deal with juniors who code like this?
As a Senior this give me OCD and anxiety.
61 -
When a senior developer changes your impeccable code and pushes their ugly indented lines with bad naming scheme without review.
-
When the department’s large plotter printer broke down, the users demanded they still be able to execute their large reports. The area manager understood reality, if we are waiting on parts, not a lot we can do, but one developer decided to re-write the report/application as a web/.asp application. Mind you, he wasn’t a web developer, mostly VB experience, so the ‘report’ executed the same queries and filled up simple html tables. Did it work? Sort of. The output had none of the specialized formatting like headers, grouping, summary calculations, etc. Since the users could see the data in the web browser and scroll left/right, they were OK with the temporary fix. When I heard this:
Me: “You do know the application could output the report in HTML exactly the way it prints to the printer. All we would have to do enable that feature in the application.”
Dev: “Yea, but I thought it would be cool to do it as a web app.”
Me: “OK, but we should just update the app.”
Dev: “Um...that is going to be difficult, the boss liked my idea so much, he wanted the report replaced with my asp application. I deleted the application from source control and from the network. Sorry.”
Me: “OMFG!…tell me you make a backup!”
Dev: “Ha!...no…boss said you would fight innovation. Web is the future.”
Me: ”What is going to happen when the printer is fixed!? Users are going to flip”
Dev: “Oh, we didn’t think of that. Oh well, that’s your problem now.”
Me: “WTF? My problem?”
Dev: “Yea, you are moving to the team responsible for those legacy applications, since innovation really isn’t your thing. I just got promoted to senior developer.”6 -
When your daily scrum takes an hour because your senior developer co-worker gives unnecessary and incredibly detailed updates...
"Well, first I tried hiding the button, but it wouldn't come up when I needed it to, so then I made an options menu, but the sliding transition was difficult to implement, so then I..."7 -
Background: Since last 3-4 months, was working with a senior engineer remotely on a project.
Present: Currently, I am Out of Office and yesterday late night, I opened my official mail and after sometime I got an email with subject: GOODBYE!
It was from him. The same senior engineer with whom I was working. I thought it was a joke. But people don't joke when they send such emails to a huge group of people.
I never knew he was going to leave so soon. I wanted to learn so many things working with him. I used to ask him the silliest doubts ever.
I still wonder why he left the company. I have so many questions to ask him.
I am sad. I am feeling left alone.
It's awkward that today, this very moment, I can't ping him anymore forever.
It's obvious to be more professional and such things are normal.
But, I am fresher and my first project was with him. So, it's kind of tough for me too.
I know this will help me to grow up stronger and teach me that time isn't constant and we need to always be ready and use the right time preciously and deal with the "constant change".
And also, wherever he goes, my best wishes to him and I hope I will meet him some day. -
Spent 6 hours implementing a feature because my senior didn't want to use a 3rd party plug-in.
After said 6 hours, went to look at the plugin's source code to get some inspiration with a problem I was having.
Guess fucking what? Plug-in was implemented exactly as I had done it to start with. Even better, actually, since it fixed some native bugs I couldn't find a way around.
Went back to my senior, showed him both sources and argued again in favour of the plug-in.
Senior: "Meh, I'm not sure. Don't really like to keep adding plugins"
Me: "Why? Do they cause performance hits? Increase memory usage?"
S: "No, not all. But I don't like plugins"
/flip
We ended up using the plug-in, but I "wasted" a whole day doing something we scrapped. Guess I learned some interesting things about encryption on Android, at least...6 -
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.U3 -
today is one the worst day of 2018, after this
https://devrant.com/rants/1571445/...
I was looking through the websites which were made in the company last year, and while looking at a website I said: "this website is looking total shit, what the fuck is this".
Guess what, the guy who made the website was there and more worst he's my senior, I'm currently doing a project with him. He was not happy with this comment ( I thought the guy who made this left the company ). I totally fucked up.
Now I will search for another job. I can't bear this.4 -
Working on my senior project tonight I went from "oh my god I'm so far behind I'm never going to get this done in time" to "I can't wait to show my advisor tomorrow because I've gotten so much done"
Feels good -
sometimes I can't understand how I got my senior web engineer position at my age.
but then I look at my fellow senior cursing about some stuff that he doesn't understand and doesn't want to understand (today it's npm) and then I feel ok again :D1 -
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 Java89 -
This is deployed on PROD(!) from my Senior Dev's app. Have I told you devs how much I hate this guy already?
7 -
Me: *Make a PR*
Seniors: *takes 5 days to review* This must be changed
Me: Okay. *Make changes and PR on same day*
Seniors: *takes another 7 days to review* Oh, you also need to change this
Me: really? Okay. *do the changes*
Seniors: Well, I'm gonna accept it. But maybe you should rework all the integration later.
Me: what.
I'm super tired of this shit.10 -
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.2
-
Layoffs happen all the time. But when you survive it and come back the next day and see the empty cubicles occupied by very senior devs who were really close to you and mentored you.
Had to go through this twice, 2014 and 2016. Thankfully we still meet up at Hooters every Friday and rant, and that's our version of a 'weekly' -
How do you deal with someone like this?
I've got this dev at my workplace that is terrible to work with, he's 2 main reasons why I say this:
1. He has no clue about team work, every piece of code he writes is written as if he is the only person that has to ever touch that
2. He's overtly protective and opinionated on things that make no sense, they're non standard "rules" that he sets and enforces by replacing others code with his own (often times you see quite large PRs and after inspection you realize he rewrote parts of code to follow his style). These "rules" also take up a really long time to follow and would make any actually experienced developer question this guy's knowledge, one example of this is where he repeats the same code over multiple components for "encapsulation reasons" and God forbid you create a global helper of some sort, he'll straight up remove it the next chance he gets. Another example is that all his components or utilities live inside 1 base directory, so you have roughly 300+ components in a /components directory, all with non standard names so you can't tell which is related to which.
I hate working with this person, it's annoying and it also sucks because he's sort of a more "senior" Dev so managers take his side most of the time.3 -
!rant I need job advice. Please reason with me.
I am 26, got 2 years of experience in c# and unity3d.
I did some research and it turns out that the minimal paying average with my job/experience over the whole country is at least 300€ a month more than what i get payed currently.
I made a list of pros and cons, and am just not sure what would be smartest to do in the long run. Here is a list for both options, please chime in on me if you can!
Points for current job:
Permanent contract (hard to fire me etc.)
Get to make mostly mobile games but nothing really big
Fun small team whom i get along with (i am on the spectrum and can be hard to deal with social or costumer related things)
Rarely any overtime (i like to know my hours)
Easy but slow jobs (badly organized, drag on forever)
Rarely challenged and thus boring me
I get to shoot nerf guns at colleagues whenever
Low chance of a 300€/m pay increase (not worth it to boss, financials aren't that great but the company is promising)
Points for any other job:
Unknown working condittions
I am probably bad and uknowledgeable about any tool they give me to work with because my experience is so monotone
Start on short term contract again all over
At the least a 300€ net increase a month
Prob closer to home then 1h drive away
I get to learn new things but give up on games/apps as i know them
Probably get knowledgeable seniors
Probably end up in a bigger more serious company where i am just a number
I am bad in new social envirnoments, oh the angst is real
And a few things besides it are that i personally only have as goal to own my own house with my fiance as soon as i can. And this means i will need to take out a 200k loan or something along those lines, to be paid off over 30 years max.
This means that the permanent contract is very valuable in my eyes, but so is monthly pay increase.
I want to have fun in my job, i want to learn new things and better ways. But i also want to be able to say "enough" to something if it overwhelms me. I just know some things are not for me and i would mess up if i were made to do them. I fear that to not be an option in a big company. I would be forced out of my comfort zone without any regard for me or my learning curve.
Any advice is welcome. Please keep it general if you can so others can learn from this as well. Seniors advice will probably be helpfull to all starting programmers!10 -
So I am helping coworker with debugging a weather forecast feature on a digital display solution we sell to hundreds of companies.
He says he just doesn't know why but the forecast data isn't correct.
I open up file where forecast data is stored and the data hasn't been updated in 6 months.
Thats when he realizes no one has paid the forecast service provider in 6 months...
And this guy is supposed to be senior to me?1 -
Another gem from same co-worker who is a "Senior Developer". Unnecessary function that fills a dropdown box(?!) with numbers 1-100. I really really hate this guy.
Bonus: Best Practice Example of Naming Variables...
4 -
Senior group project in college.
When you decide to meet up and one member doesn't show up at first meeting.
So I sent an email about the research I did on the feasibility of the project and how to implement a core requirement. 2 days later & no response yet..
Why do I think I'm gonna be the one the pull off the application by myself & then have to put name of people who have no idea how I got it to work..8 -
Senior[0]: emacs is the best text editor
Senior[1]: yeah, right. It literally stands for Emacs Makes A Computer Slow.
ME: GNU loves recursive acronyms, don't they?
Senior[0]: lol
Senior[1]: lol
ME: what?
Senior[0]: he obviously made it up
Senior[0]: no, I didn't. Use vim ffs. -
Recently got promoted to Senior Engineer position. Should I be worried for not knowing what that 'Senior' means? 😳21
-
Our smart and very professional sales guy strikes again,
I had to do some research on if I could print a pdf file directly from the server (be it php / nodejs)
When I told him I had found a solution he said, good job and went away, I was like...hmm k..
A few days later he came to my senior being mad that the project wasn't done in time.. And we were like.. Dude... What project!?
Apparently he made a deal to have a working demo in two weeks, but we (our dev team) never got that message...3 -
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*5 -
Seriously, how the fuck is it possible for someone to be a senior engineer after only 1.5 years in the industry?
I have been working for 5 years and I don't dare to say it because I have seen real seniors with 15+ years of work experience and how they work. A completely different level. Hell, I refuse opportunities that announce they want senior engineers for that reason.11 -
Back when I used be a junior fresh out of school, my senior used to say, when releasing a first version or a major version of any software, app or website always implement easy to fix bugs.
End users or clients, especially the ones that tasked you with the creation of it, will look for a bug until they find one, if it isn't one you will spent hours trying to figure it out, instead give them one.
You know how to fix it and the client is satisfied they found one.
To this day, i still do that, although mostly not even aware of it. Eg: I know that's a bug but i'll fix that when (not if, when) they complain about it.
I even find myself telling the juniors, i develop with, giving them similar if not the same advice.
And that is what experience means, skill is something they teach you in school.
Experience is what makes you a senior or a junior, not your level of skill or the amount of keywords on your Linked In profile.2 -
So, first a bit of background:
We've got a parent class, owned by another team, and two child classes, owned by my team. One of the children is unused. (Already sounds bullshit right.)
On to the story:
6 months ago, I had to modify one of the children (add new functionality).
I try to modify the base class to add it, the senior dev in charge says "no, just add it on the child". So I do, then merge it in.
Yesterday I wake up to a high priority bug. Turns out the senior guy wants to add another child class, and wants the functionality I put in my class on the base class.
Even commented on my PR from 6 months ago asking why I didn't do that.
The fucker opened up a high priority issue assigned to me, asking ME TO DO THE CHANGE I WANTED TO DO 6 MONTHS AGO THAT HE SAID NO TO.
Fuck this shit. I have a meeting with him and my boss in an hour. My boss is pissed, I hope he tells the other guy to go fuxk himself and do the change himself.14 -
This happened a couple months ago, but I wanted to share this one, since it still baffles me.
We were hiring and had this weird candidate. The team said no to the guy after the interview, management still hired him and pressured us to train him, which cost us tons of hours we had to somehow squeeze in during a hot phase of our project.
After almost 3.5 weeks training he had to hand in a small component. What he handed in was brainlessly duplicated, half of the stuff in there wasn't even used, the other half wasn't working properly. At the review we asked questions about the code he handed in - he could not answer one of them.
We then had a big argument with management to let the guy go, which they eventually unhappily agreed to.
The icing on that cake of a story: Turns out, the guy was hired as a senior dev with a way higher paycheck than most of the devs on the team. Wtf?!9 -
Why are some seniors just so full of themselves? I mean... Yeah I know that they know more than me (junior) but common, you don't have to rub it in my face! Tho I'd rather have it that they rub it in my face than them explain it with the most difficult terms / hardest words they could find in the dictionary!!
I also don't need them to complain that I'm on a different platform than them (while they help me)4 -
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.2 -
So I finished all my tasks for the sprint (3-weeks long) in the first 2 days.
Shit that happens when senior team members underestimate your abilities...4 -
Junior developers:
"I have no idea how to solve this one problem; I'll never get good if I just keep Googling for the answer"
Senior developers:
*46 tabs open to Google and StackOverflow for one problem*
src: https://twitter.com/DavidKPiano/...
Gotta say, it's spot-on14 -
I'm having a strong urge to kill that asshole that asked me, on a SECOND interview for a SENIOR position if I knew what ORM was!!!
Are you making me fucking waste my time you fucking cunt???
Did you fucking read my CV?
Obviously not because you would have seen several ORM technologies on it you fucking piece of shit.
You made me waste my time, and now I have no choice but to slice your fucking throat!
I'll be waiting for you, in the dark you mother fucker.16 -
„Please do not ask any questions in the meeting next monday, I don’t want to be embarrassed!“
- The senior giving me and two colleagues an introduction into his field of work...
WTF1 -
I'm in a company with no senior devs I can look to for mentoring. How do you go about scaling with the company without a developer more senior to guide you during development?
I feel like I'm always second guessing decisions.14 -
So this post by @Cyanide had me wondering, what does it take to be a senior developer, and what makes one more senior than the other?
You see, I started at my current company about three or four years ago. It was my first job, and I got it before even having started any real programming education. I'd say that at this point I was beyond doubt a junior. The thing is that the team I joined consisted of me and my colleague, who was only working 50%. Together we built a brand new system which today is the basis on which the company stands on.
Today I'm responsible for a bunch of consultants, handle contact during partnerships with other companies, and lead a lot of development work. I'm basically doing the exact same things as my colleague, and also security and server management. So except for the fact that he's significantly older than me the only things that I can think of that differentiates the seniority in the team are experience and code quality.
In terms of experience a longer life obviously means more opportunities to gather experiences. The thing is that my colleague seems to be very experienced in 10 year old technologies, but the current stuff is not his strong side. That leaves code quality, and if you've ever read my previous rants I think you know what I'm thinking...
So what in the world makes a person senior? If we hired a new colleague now I'm not sure it'd be instantly clear who should guide and teach them.8 -
Seriously.
Don't call yourself "Senior Software Developer", if you write shitty code, and have less experience with the technology stack than the other team members!12 -
Hello senior devs.. . What happens if you screw up? I mean if a junior dev screws up, the senior helps.. right?6
-
When you're working on something all day and then the senior dev swoops in and answers your question in 5 minutes.
-
I always thought the hate on senior developers doing stupid stuff was exaggerated... Mine just pulled an entire table, then used 4 for loops to reduce the records by criteria... I don't think he knows what the where statement is in SQL!1
-
It is so comforting when senior senior senior engineers also tell you they have no idea why a fucking test spec occasionally fails. Literally, the spec is fine and all but sometimes, it just decides to say fuck off.3
-
Don't use your senior software engineer title or years of experience as reasons in a debate or argument about software
My manager was asking me what steps needs to be done to perform a disaster recovery for our cluster( on production). I will be honest here, I have not maintained this type of cluster(kubernetes) in production before. However, I have enough understand of the system to answer my boss question. I basically told him there are A, B, C you have to do.
My senior developer jumped in and said "No you should do A,C, B because C is more critical than B. " I then replied to him: "I understand your point, I notice that too, but .." Before I can even finish my sentence, this dude has already rolled his eyes and interrupted me very loudly: "Have you worked with these systems on production before? I did". The asshole knows I haven't maintained Kubernetes on production yet of course.
I got super pissed at him and pretty much shouted back to him and my manager: "Just because I haven't worked on this system on production yet, does not mean my argument is wrong" .
I then dragged my managers, that asshole, and other engineers in a room and settle this out. In the end, people agreed with my steps over that asshole senior engineer dude because I gave them rational reasons.
The conclusion is: Your senior title is given by the company, It doesn't mean anything to me. Also, it doesn't make you more right than another person just because he has a "lower" title than you.1 -
Going over his first iteration of his assigned project...
Me: "This looks awfully familiar..."
"Senior Developer": "Well, I took some inspiration from your apps"
Me: "No, you copied and pasted all of it, down to my breadcrumbs..."
Senior Developer: "No, I only made it LOOK like yours, I didn't copy any of your code..."
Really?! REALLY?!
7 -
So why the fuck did you go into code that I've written, change the name from "mode" to "type" throughout the >1500 lines of code that's relevant to the feature, and then move on to change my implementation to something that is arguably not common practice for the language and framework we're using, and in turn create duplicate state? And why the fuck weren't these changes in separate clear commits, but instead scattered over multiple commits? You're supposed to be senior!4
-
When some seniors backup any file with .<n> on production system. Like if 15y of dozens of different blah.exe.1 to blah.exe.27 are of any value but bloated directories...5
-
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.2 -
I got invited to take part in the "senior" games in my town. The person inviting me is in their 80s. They said people in their 50s, 60s, 70s, 80s, and 90s will compete. I told them I am not yet 50. They were oh, okay. I said, I will tell Ed at work though. He could be in them!
Then I told Ed about this. He laughed. Then I said he could be in them. He told me to get out of his office, jokingly. I asked him if he was going to go to HR. He said yes. Then he said it was really funny I got invited.
Ed is great to work with.2 -
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 junior8
-
A senior dev I’ve interacted with only on Twitter, whom I looked up to, who has blog, newsletter, buzzword tweets and all that jingles.
Met them IRL today.
Dayum 😷
They talk about all the things they know about, on the internet. But, shocked to see how many simple things they didn’t know.3 -
Web Juniors: “Why use a single grid element when several flex elements layered like haphazard pancakes will do the trick?”2
-
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.1 -
Working on this bug for a day. Frustrated Friday afternoon. Decided to explain to my manager and senior why I can't find a fix and while explaining it to them, I eventually figured out the problem and fixed it.
I just realized I used my manager and senior as rubber ducks. -
Brought to you from the 5000+ line Java file. Contained within the 1500 line method. I bring you the following pattern. Let's guess all the ways we could've done this better?
- Streams
- For loop
- Iterator
What gets really fun is when this you get this pattern doubly nested so you have a random i's and j's floating all over the place.
Note: this isn't ancient code it was developed about 3 months ago.
[Code has been lightly anonymized]
4 -
We're both senior devs, I use nodeJS/Python. Stop forcing your Java *superiority* shit on me. I can write the API using either language. Also fuck your JVM. FUCK THAT SHIT4
-
My project manager, after 11 years of experience.
"What is the svn function replace?"
He used svn for more than 4 years at the very least.3 -
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 start2 -
Meeen fvck this shit. After my student loan I’m out in this shit ass company men.
So I’m fixing a frontend bug. I’m so into it that I opened more than 10 tabs. So i called my senior on what I found then he want to test something on my workstation so i said im cool with it and then i closes all the TABS man. Comeon!!
Ps: the tabs are sequentially opened to track the bug.13 -
Just passed technical verification for senior dev, then went to subway. Question from the lady behind counter where tougher :P2
-
So in the project I’m working on we were about to do a push to live, no major functionality just minor adjustments and nice to have stuff. One of the things I did was a reminder, nothing special just sends an email out if something hasn’t been done for 3 days and then sends an email every day following. Push to live and every thing goes fine with no issues. Day 1 there are no issues. Day 2 there are no issues. Day 3 and I’m inundated with people telling me that the emails are getting sent to practically everyone, shit. What have I done? What have I missed?
So I start looking at the live database hoping for a data problem, no such luck. I look at my code looking for something blatantly obvious but nothing. I start replicating the data but I can’t reproduce this bug and it’s annoying the hell out of me. I checked one of the emails that the client sent to us more thoroughly and seen that it was sent at 07:01. This is odd as our webjob runs at 1am so I start looking at environmental factors and started looking at release management, more out of hope than expectation. I check the staging environment and see that the webjob ran at 7:00. Coincidence I thought, the webjob gets packaged on the release pipeline and everything in the database was dummy data anyway but I’d better check anyway. The database was an exact copy of the live database, turns out a “senior developer” wanted to sanity check everything by running live data through the code so he copied the database over. It was fine for the first couple of days but the data was now 3 days out of date triggering my email code and I get hit with the shit storm. I’ve never met such an incompetent developer in my fucking life, functions 700 lines long, classes that are over 20000 lines, repetition every where and the only design patterns he’s used is when he picks up a child’s colouring book. I can live with the fact that he writes code like someone on their first day of University But copying a database because he wants to “visualise” the fucking data is absolutely farcical. No wonder the project is fucked with a “developer” (in the loosest possible use of the word) is at the helm. -
You know you are worth for Senior when you explain a Task to some Junior 20 times in about 1 hour and you are only a bit upset about it. And the best is: you could have done it by yourself in 3 minutes2
-
When you are a junior dev and you ask howto do some shit to a senior dev. He answers vaguely and you have to keep asking during the wholr process instead of getting a full answer from the beginning5
-
I discovered a commit message from one of my (senior) colleagues today. It made me shudder. It read, 'Just adding some changes made outside of source control and deployed (over last 12 months)'.
I genuinely think he can't follow any processes he didn't design. He controls the servers too, so it's not like any pipeline would prevent him from just doing what he wants. It's a bit scary to be honest, he thinks MD5 is a secure password hash! -
Just what the fuck is up with the senior devs in my team? Just because it's my first job as a developer doesn't mean I can't be right at times. Why can't they fucking digest that they could be wrong at times and me trying to tell them what could be improved is just for the product and has nothing to do with their egoistic selves.4
-
TL;DR Shit programer trying pass off stealing code as "Recycling"
Backstory:
Client hires senior dev. He lied and knows nothing. Has been causing havoc in production since day 1. My crusades to defend production have been without much success.
Since he wants to LITERALLY put his name on every big project, he finds any reason to make a new version of it (or make a slight astetic modification) to say he did something.
The client doesn't know or care about the programming side of things. Which means it is incredibly difficult to get him to understand the issues this brings. Not to mention that the "senior dev" is acting as a consultant to the client, altering the facts.
Story:
The piece of shit, is trying to make a new version of a big project. It was originally made by my mentor. Again, if you are using someone else's work to complete your own, I don't care. But if you take 99% of another person's work and then say...
"I took and existing project, which was similar to what I'm trying to make. Then I modified it to fit our needs."
Fuck you man!
You took someone else's work. Now you're trying to present it as your own. No references to our team. Again, there is literally nothing new about this project. It's exactly like the original. The client didn't even ask for this.3 -
I just solved (high level with a bit of POC) a problem that has been an issue for my team for over a year...
Not sure how I should feel...2 -
TL;DR The "senior dev", that the client hired on their end, is acting as a middleman between me and the project requestors. Taking the credit for my work.
I've already bitch about this before. I've been in a crusade to defend the production server from this fraud for a long time now.
But most recently he has removed me from all meetings with the actual project owner. I create the solutions, then he goes through them to understand it a bit. He proceeds to present it to the project owner in a way that almost blatantly says that he made it.
I'm sick and tired of working with this asshole. He is literally useless, worse he is slowing things down and breaking others.
I'm just gonna begin countering this... -
Well, that's how much it costs to hire a senior developer. I think I'll just go back to being a junior dev :-D.
2 -
Coworker pushed some changes and gave me good reason to rant.
Here's my story:
I start implementing a new feature, senior reviews it and suggest some changes, which are actually good ideas. I continue developing and implement the suggested changes.
The next day, senior keeps working on outdated source and makes similar changes like i did on the day before. Just pushes it anyway and breaks fucking everything.
The api now contains redundant information.
My classes still exist, but aren't used anymore. Let's keep some redundant code in the project, because deleting it is so much work.
All the unit tests broke, but he just commented them out, so everything is green again. We have now 0 tests which actually do something in the project, but at least the build is green...1 -
Finished all my tasks for senior promotion ... Teamlead was like ... What promotion? I thought you wanted to stay medior? RLLY????
While he kissed asses for his senior promotion, not even having a skillset for teamlead nor senior... -
Another nice rant while I try to find a job.
I make an interview with the senior dev (they are small and don't have a hr).
Everything sails snooth and they tell me "We will tell u something at the end of august"
Well yesterday I wrote to them, asking for news and not only they give me a negative response... (after they also said they forgot about me) but.... THE WROTE MY GODDAMIT NAME WRONG!
Like my email has my name in it, I presented my self and I closed the same mail with my signature. Yet they write a completly wrong name.
Like wtf!!! you can't even look for my name? it feels like they don't even know who I was.
I can say I'm lucky not to work for them.6 -
So I've been hired as a senior software developer with all the tags included (mentoring, innovating, pushing forward changes) for a company that is trying to move away from waterfall development (yup, it's 2019 and this exists) to a more iterative workflow.
I was initially hired and sent out to do some "field work" abroad for 3 months and then worked "remotely" from the local office with our field partners.
During all this time it seemed that my ideas go through smoothly, there was a lot of chatter about how things are moving forward, how new projects, innovations and new methodologies are implemented.
And yet, after my "remote" work has finished and I have to do things locally more, all of the skeletons fell out. It's just talk, nothing seems to be changing at all and yet any attempts to talk with the brass is like hitting a brick wall.
Not only that, I've been handed a 12 year old project with no possibility to refactor, no technical documentation, very few comments and in a terrible style.
The atmosphere in the company is odd as hell. People are either not very initiative, nor they seem to really care about all of the "changes" that "should be happening".
It almost feels that I've arrived in a company that still lives in 2007 more or less.
Should I quit, or perhaps it's a little "too soon" (have spent 7 months in the place already)? What I don't want is to get in the same train again (work for a company for 8 - 12 months, feel burned out because of the divergence between actual things done and "plans" and then change the job).5 -
Senior dev:- "Limit your commits to have maximum 10 changes"..
Also senior dev:- Doesn't approves pending merge requests for days...5 -
I checked out this new hybrid app that was released by some local senior developers.
Turns out that on my user profile, my user ID is set as the value of a hidden field and changing it to any other user ID and saving the form will update the profile of that user. Including changing the password.
The password reset form also allows me to change the user ID to reset that user's password.
Speaking of passwords, the value of the password field on the profile is my actual password in plain text.
Yes, I said this app was released by a couple of "senior developers". One has over 15 years of experience and the other works at an IT company that builds online banking systems. They appear to have outsourced this side project to some other development team but... Come on. At least take one quick look at the source code before releasing it, why don't you?
I don't even...1 -
To senior devs: How do you manage half a dozen projects at once and decide when to prioritize time and do the small tasks yourself and when to let your team members learn and let them take their time...all while you're working on something exhaustive yourself?1
-
Everyone knows how hard it is to get your first job. Everywhere wants 1-3 years of experience.
What noone tells you thought is that's hard at the other end. When you're looking for architect/tech lead roles you will see loads of postings but upon investigation they're just mislabeled senior developer positions.
And of course, if you're looking for good money, it feels almost impossible to get beyond the screening stage... -
So this happened a few days ago
I was working on a module assigned by my senior, and was the sole developer on that module. Just when I was breaking my head to get a bash script correct (was writing a bash script for first time), my senior comes and looks at my messy script and goes "No, no, no, no that's not how you do it. "
Takes the keyboard and starts editing my script opened in vim.
Did some cool restructuring, taught me a few things about bash and while talking to me kept the keyboard back at its place.
I keep my hands on keyboard while talking to him and press
[Escape] :q!
And as I pressed Enter my face went purple/blue thinking this is not good. 😨
(I have a habit to quit as I had almost never edited and saved a vim file before)
And he sees that face and says
what happened?
No nothing. Everything's cool.2 -
Ok, so I need some clarity from you good folk, please.
My lead developer is also my main mentor, as I am still very much a junior. He carved out most of his career in PHP, but due to his curious/hands-on personality, he has become proficient with Golang, Docker, Javascript, HTML/CSS.
We have had a number of chats about what I am best focusing on, both personally and related to work, and he makes quite a compelling case for the "learn as many things as possible; this is what makes you truly valuable" school of thought. Trouble is, this is in direct contrast to what I was taught by my previously esteemed mentor, Gordon Zhu from watchandcode.com. "Watch and Code is about the core skills that all great developers possess. These skills are incredibly important but sound boring and forgettable. They’re things like reading code, consistency and style, debugging, refactoring, and test-driven development. If I could distill Watch and Code to one skill, it would be the ability to take any codebase and rip it apart. And the most important component of that ability is being able to read code."
As you can see, Gordon always emphasised language neutrality, mastering the fundamentals, and going deep rather than wide. He has a ruthlessly high barrier of entry for learning new skills, which is basically "learn something when you have no other option but to learn it".
His approach served me well for my deep dive into Javascript, my first language. It is still the one I know the best and enjoy using the most, despite having written programs in PHP, Ruby, Golang and C# since then. I have picked up quite a lot about different build pipelines, development environments and general web development as a result of exposure to these other things, so it isn't a waste of time.
But I am starting to go a bit mad. I focus almost exclusively on quite data intensive UI development with Vue.js in my day job, although there is an expectation I will help with porting an app to .NET Core 3 in a few months. .NET is rather huge from what I have seen so far, and I am seriously craving a sense of focus. My intuition says I am happiest on the front end, and that focusing on becoming a skilled Javascript engineer is where I will get the biggest returns in mastery, pay and also LIFE BALANCE/WELLBEING...
Any thoughts, people? I would be interested to hear peoples experiences regarding depth vs breadth when it comes to the real world.8 -
When do you see/perceive-that a Dev transit from junior to senior?
I'm an undergrad, working, by now, for 9 months in companies meanwhile studying, I have found that I didn't really had any difficult time dealing with the requirements/specs in the working environment, I always found myself being able to adapt to the problem and deal with it, and by this way of doing I can hardly see myself as a junior. What do you think about? (Excuse me for any mistake, I'm drink)2 -
Hey guys, I need some junior advice. I work at a small startup in a team with 2 other backend developers.
The "new" guy studied at a university for a few years. He writes beautiful code. I try to learn from it and use his short hands a lot. I came from highschool and don't have a degree in it (yet).
I recently wrote a piece of code which handles some timeslot logic. I was really proud of it.
New guy needs to fix a bug and add a few things. He completely refactors my code and makes it more structured and partly better. The logic stayed the same.
It sort of bothers me that he touches my (precious) code. How do you guys handle these things?21 -
Just explained 3 senior devs what cherry-pick is.
Dunno if I should quit or get them fired.
Thoughts?5 -
Guess who just spent the entire day before launch debugging why compose doesn't work on an ec2 instance where I DIDN"T INSTALL FUCKING DOCKER
I guess this is the key difference between me and seniors. Seniors know where to look where shit breaks because they have been breaking it for at least 5 years.7 -
Never understood why people bloody love their code. It's good to be happy about it, but
beats the zest for refactoring or any other sort of improvement.
Took me an hour to explain a senior dev why his changes introduced bugs in build.
Literally landed to the point reverting his commit and demonstrating the damn build to work.
To which he replies what if the data is corrupt
Damn it's not the data, it's your bloody senses.2 -
How do you define a junior/senior dev?
I've been a professional developer for about 5/6 years now.
Would taking a "junior" role be a step down? Or does the term not really matter?3 -
"basically I have quite the experience and last job I was senior"
"How much experience do you have with [language] in specific?"
"About 4 years"
"Ah so you are medior, we are searching for a senior."
Seriously, who came up with the stupid idea of "must have 5+ years in a tech to be senior"?4 -
- Seriously, I should do some work in my senior project.
- (looks at code and stares for an hour)
- I'm hopeless
- (go to sleep)
Repeat next day -
Senior developer :: So, how's the work for maintaining the code base going.
Me(Intern) :: It's pretty easy because I have treasure
Senior developer :: what treasure ??
Me(intern) :: Stack Overflow.
Senior developer be like
-
Boss explaining a bug found in my senior developer's (yes, that one) application...
Boss: "This shouldn't happen, this presents a security issue since these records should not be visible at this point."
"Senior" Developer: "You're right. Hmm, what should I do about that?"
Me: *face palm*2 -
Haven’t written code in months. Is this what it means to be a “senior developer”?
I’m not sure if it’s a blessing or a curse tho. I kind of feel it’s the former 🤣🤣🤣4 -
Can I go to CTO and demand that he will demote a "senior engineer" (who takes senior's paycheck) who don't know what "race condition" is, and how to design/deal with it?
Why? Why I can't?15 -
While addressing a Senior Dev's (SD) query from another team.
SD: why is this field mandatory? Can't it be just optional? Any other work around?
Me: Is your code changes already pushed in Devo? In that case, we provide a value which will work since you are not concerned about it.
SD: Yes. It's pushed till production. And, I want to test changes in Prod.
Me: (shared some codes) and explained that this feature for testing is only available in Devo.
SD: I know that. (Shared me a ticket) I want this field to be optional. That's it.
Me: (read the entire ticket. Didn't find anything related their) Told him, I will discuss with team. And meanwhile, for Devo, you can use this value.
Next morning, I accidentally came over some other ticket raised by him only which had the correct doubts regarding request to support this field in production
Now, I don't know why did he share a wrong ticket with me.
And, how will it even help him if that field was even optional.
THAT JUST WONT WORK IN PRODUCTION.
I will discuss with my team and see what can happen. -
When the company transition you from a Junior to a Developer and they start dumping all these projects on you
-______________________-3 -
ffs our senior dev is on a two week vacation... 4th day and my outlook already looks like fucking mordor5
-
+7yrs experienced dev start at the company. I need to onboard this person.
Gave 2 simple bugs to solve, it couldn't solve either. Asked so many questions that I had to stop, solve the bugs myself and give the solution. Which raises the flag that this experience might be a lie.
This person doesn't really listen, so I don't want to tutor. Even though I can already feel that my manager will say that part of the responsibilities of being a senior as I'd like to be, is to tutor newcommers (I can count on my fingers the amount of seniors who actually tutor, but I know this is not an excuse).
Guess I will feel forever frustrated that I cannot get the damn title.7 -
I hope, that the next time you ask for a raise, they ask me what I think... So that I can say "well it cannot even go check a database to see what it has at its dispoal... Demanded 2 big resources stop their work to listen to his fake problem statement.... Only to realize he didn't even check the fucking database..." please move this person back to being a junior... This is basic level shit man..🦄
-
A colleague went on vacation, as the lead mobile engineer I had to cover his work. Switching between iOS dev and Android dev usually is fun. Integrated and deployed a dozen tickets for each platform within 12hrs.
-
Trying to learn a bizarre custom javascript wrapper that was used to communicate with complex mobile RF devices, the point being was to control them, but damn thing did not work for crap even if you tried hard.
When any of us devs asked the senior "dev" who designed it if there was any documentation on it so we could actually get started on working, he literally told us we sucked ass and that we were pieces of shit that knew nothing of programming.9 -
Isn't pair programming kind of stupid in a workplace environment when you pair a junior and senior?
In that you that you pair someone that would be able to solve the task himself and one that needs still help to solve the task.
Why shouldn't the junior struggle on his own a bit before asking questions?6 -
today our senior dev said that (part of my code) is crap...I asked him how to do this the wright way...he did'nt answer.... :/5
-
So asked to help out on an extra project that another Dev ( who is a senior developer ) is working on and I go to clone the repo but find 15 or so commit messages on the master branch saying "Work on feature x" (not an actual x). This is going to be fun...
-
After working about a year at a new company, I realise multiple things.
1. Just because their older, or senior, doesn't not mean they know everything.
2. I really like helping other people with coding.
3. I am underpaid for the amount of work I do.
I do the same job as the senior devs, and also take on a more leadership role. The coming talk about my pay will be interesting to see..3 -
Junior Dev about 18months in my current job and I've got a problem
Started to feel not wanting to code at work, despite working on a greenfield project thats critical and using new tech. I get a little defensive about PR's over stupid small things (PR was once rejected due to auto indentation "not to standard").
Talked with boss (who I get on well with and like) and thinks my problem is I've lost confidence coding. Trys to get more senior Dev to on side to help me out more.
Same senior Dev is really close with other junior on my team - pair on alot of stuff all the time, have lunch and spend free time together, and will work way past working hours just to try and finish something that day (even though it's not due that day).
(Probs working ~60h weeks, where as I'm ~42h and contracted for 37h. I'll work on if I need to but tries to have balance)
Senior and other junior tend to ignore tickets on the board, do the work and then when I pick it up they say "I did that last night". No docs, no PR for me to ask about how it was done (as they merged it themselves). (They have previously completely refactored my branch in the past overnight then not told me atall)
I'm not saying its favouritism here, but I'm not happy with the situation. I feel I can't ask questions as they are always together or they discuss the problem themselves and just give me the answer (not really acknowledging my points). I dont tend to ask for help from this senior Dev now as I don't feel it's worthwhile learning wise for me.
Other people in the team are great but working on other aspects so not a direct one-to-one alignment (others are DB Dev & principal senior dev)
Furthermore I'm wanting to possibly work on full stack web or more architecture stuff, both which are not in my current teams remit (backend up to API).
So - what do I do? Try and remedy the situation in the current team as best as or look for a new teams as cut my losses.
I'm torn between the 2 and I'm unsure how to get out this rut. I feel I need to find a solution to this soon though
(Sorry for the long rant folks)4 -
Any senior dev who get less paid in terms of his juniors or am I the only one?
If anyone who is in same shoes like me please suggest how to cope with the feeling of unrest and feel less miserable.6 -
My co-worker ask me today, what is the different between Junior and Senior developer. We can’t call a person senior developer because they have been doing junior stuffs for long time.1
-
Code verification
senior dev: You wrote this code yourself?
Me: Yes sir, it's clean right?
Senior Dev: Prove it
Me: Blah Blah Blah...
Senior Dev: Damn, You the realest -
I wish senior people would just admit if they don't know something or are unsure. I hate spending time implementing a feature and spending more time troubleshooting it only to ask for help and be questioned why I'm "doing it like that" in the first place...
YOU TOLD ME THIS IS HOW IT IS DONE!!!1 -
Question: Devs with 3+ years of exp.
Do you like coding? Or do you like HLD/LLD or general tech solutioning more?15 -
So I'm thinking about programming an app for iOS and Android in C# for my senior project.. but since I lack creativity I can't think of something..
-
Worst one was in my first ever web developer job. It was a small company where everything was done in Adobe ColdFusion. Was there for 2.5 years before they went bankrupt and I got made redundant.
So when it came to look for another job, I was hoping to get another ColdFusion related job. But a lot of company's requirements were pretty bullshit. Junior position, but must have 5 years experience.
After 4 months of looking, eventually found another job but as a PHP developer. But since my PHP skills were beginner's level, I had to start from a new graduate level salary all over again. Felt like the past 2.5 years at my first job was a waste of time. -
Had a discussion with a fellow coworker about users experience.
This guy actually trying to convince me that the backend is more important for ux then the ui. And this guy is a senior with over 12 years experience. Damn this one is really stupid 🤦♂️🤦♂️14 -
Soo I finished my apperenticeship a year ago and I do not have any higher degree what so ever.
"I am contacting you for a senior position at [...]"1 -
Do people know of good resources (books, blogs, YouTube channels, whatever) regarding advancing to the higher levels of the tech industry?
I can find lots of resources for how to get started in your career but as I've advanced it gets harder and harder to find guidance (this is not surprising, but still lamentable). I am currently one promotion away from Senior at my company and I have no idea what to expect beyond that.
Any suggestions?2 -
I know a senior developer that knows quite a bit, im glad, this is how we grow. He has a habbit of wanting to be the main attraction in all conversations, either tlaking louder than others or sticking to a point in a subject he is not correct in to try force his opinion (i dont speak kuch around him because of this exact reason).
Today we talking about react, we have been working together as i am suppose to transition into senior and we are going incremently rewrite the application in react. So learning react was fun as you could imgine. I came from a background already knowing this and being exposed and that is react and react native. For skme reason i let him talk but he doesnt me especiallt knowing im correcr about something because we have the internet to check things. He looks at me and literally goes red in his face when i suggest standards that would make the code easier to read. Less to type and all the small things and showing him old things i worked on to give a base for him to work off and be there when he needs. Allnhe does is complain and i dont know how to tell him he has a way of approaching a situation not the best andni worry for other junior/mid developers that has to work with him because he will make them believe they are wrong and when they arent hust because he wont calm his ego. We are suppose to be in the community all together to build platforms and progress the sector and better the lives of people. Not waste time picking on eachother. We have prefeences abd we can debate that is important as it allows us to doubt and then make us want to learn more. I just wish there was a way to tell him because we all know. Noone would want to work with someone that is suppose to better you in your career and as a person1 -
Hey read this. This shit is funny. HAHAHA
I was fixing a bug right. The bug was throwing InverseOfAssociationNotFoundError in our rails admin page when deleting a user. So the director of engineering called and we had an argument because he was insisting that the error InverseOfAssociationNotFoundError is OUR IMPLEMENTATION. HAHAHAHAHA. my goodness. I showed him that the error comes from the constraints when deleting a user. A table has no relation to the user table but my senior added it anyway for some reason. I was mad and laughing at the same time because I showed him the documentation and the simple fix. These idiot keep flexing his 30 years of experience. HAHAHA3 -
I am gonna freak out, a week and a half to go back to school and I still haven’t figured out what to do for senior project.
What did you all do for your senior projects if any?
I have an idea but I’m scared I’ll have to work on my own.
Heeeeeelp11 -
Shit my "Senior" Dev coworker days:
"Well, logically, lies are more important because it takes more effort to remember the lie, who you've told it to, and any extra stuff you made up to keep your story straight. Then, when you have more than one lie, you work even harder to keep them all in line".1 -
"Oh, sorry I didn't write you back! I checked 3 hours ago, and we only add the data once in our database before sending the notification to your endpoint, so everything is fine! Check if you run the same functio twice, it's an easy mistake!"
You. Fucking. Moron. You send the data 2 or 3 times (at random) every fucking time. I have nginx logs showing that, and I've fucking shown them to you TWICE. I don't fucking care if your DB is fine, check how many fucking times you POST the damn data. We're already 2 days behind schedule because you can't be arsed to check your own damn code. Ffs. How can you even be a senior developer?! -
Our lead dev has convinced the board to move the new software suite forward into .Net Core 3. Much of his reasoning is sound, a mainstay of which is the cost and ease of hiring developers to actually make and maintain it.
My own roadmap with the company focuses around one of these products, so I am to become the core developer and maintainer. Given thats the case, given that my primary skill is with Javascript/Node and given that we have deadlines, I am going to make the case today that this product might be better built in Node.
We are going for a microservices architecture. Combined with Typescript for type safety as the code base gets bigger, I am not sure I can think of many real advantages to choosing .NET instead. It will benefit from its async I/O later too, as the plan is to build in API driven dynamic UI down the road.
He is a fierce man, and I am the junior. Wish me luck.7 -
So the issue is that if you refresh the page the method that saves the data is triggered again and it retrieves over data from the controls to overwrite the new data you just saved
My senior developer told me the solution was to impliment ajax on that page...
What the fuck? That doesn't stop the method from being triggered when you hit the refresh button on the browser -
This got me fucked up. Listen yo.
So we have this issue on our modal right. The issue keeps poppin. It's a hotfix because its in prod. So my senior and I were on it. After a few hours, I showed him the part of the code that is buggy. It's 50 lines of code of nested if-else, else-if. And so we're still fighting it. He redid everything since we're using angular2 he did a subject, behavior-subject all that bs and I was still trying to understand what's the bug, because it's happening on the second click and so I did my own thing and found the cause bug and showed it to him, its this:
setTimeout( () => {}, 0)
the bootstrap-modal doesn't allow async inside it (I dont why, its in the package). So he explained to me why it's there. So I did my own thing again and find a workaround which I did, a one-line of angular property, showed it to him he didn't accept it because we'll still have to redo it with subjects and he was on it. I said ok. Went back to my previous issue. The director came in and ask for a fixed, my senior came up to me and told me to push my fix. Alright no problem. So we good now. Went back to our thing bla bla bla, then got an email that we will have a meeting, So we went, bla bla bla. The internal team wants a support for mobile, senior said no problem bla bla bla, after the meeting he approaches me and said (THIS IS WHERE IT GOT FUCKED UP) we wont be supporting bootstrap4 anymore because of the modal issue and since we're going to support mobile and BOOTSTRAP4 grid system is NONINTUITIVE we are moving to material design because the grid system is easier. I was blown away man. we have more than 100 components and just because of that modal and mobile support shit he decided to abandon bootstrap. Mater of fact its the modal its his code. I'm not expert in frontend but I looked at the material design implementation its the same thing other than the class names. OHHH LAWD!3 -
So I became a team leader ("promotion").
One of the team is a senior by title, but fuck he is just a refactoring machine. Seeks for architecture design in fucking everything. Even in fucking tests instead of just writing them he is inventing convoluted architectures and systems...
Fuuuuuuck - just write the fucking tests, no one gives a shit if you have a fucking factory in the test case! -
What is your main responsibility as a Senior Engineer? Let say Senior software engineer or Senior Devops or Senior Data Engineer?
I need some references to put in my onboarding task. Thanks!!5 -
don't you just hate, when this happens? translated from Slovak we call this "the system of the falling shit" you know this under "hot potato"
email:
from: marketing coworker
to: senior dev 1
* asks for a lot of stuff, deadline yesterday, high priority, on a site for which the jenkins build is crashing every once in a while, because we are migrating all the time so some folders are already deleted or not created yet and the build config is really strict *
forwarded from: senior dev 1
@senior dev 2
forwarded from: senior dev 2
@senior dev 3
forwarded from: senior dev 3
@junior me
ಠ_ಠ fuck me i guess ¯\_(ツ)_/¯1 -
The number of times I have been contacted by companies because they have seen my website and Github account saying they are interested in someone like me, to later be rejected because my lack of experience from working on any companies.
I know they want seniors but how is one supposed to climb from junior to senior when companies only want 5+ years experienced seniors.
I know the fact that I am a junior dev, but I would like to say don't judge a book by its cover. It's the skill not # of years that matter, no?5 -
How do you deal with the fact that sometimes a junior dev will have a better solution than a senior dev because he knows more on the technology/language for this new project? Maybe for this technology he should be the senior one... But how do you deal with these situations?3
-
Just now while having dinner, we saw Troy was on TV. The part where Achilles' younger brother went onto himself, disguised as Achilles, into war... even when Achilles said we're going home.
In my mind, seeing it as... That's how a junior developer fucks up when he is overfilled with enthusiasm and patriotism towards company and deploys on server with senior's credentials, even though senior said "NO DEPLOYMENTS ON FRIDAYS"... and now everybody has to deal with this shit. -
I am supposed to hire a Senior Dev for my startup but I'm kinda confused as to what should I do to make sure someone is good enough. People often write 5-8+ years of experience yet turnout to be fakers and I really can't afford that right now. Any tips on hiring somone senior or more experienced than I am..7
-
I just had to convince another "senior" dev that Magic Numbers are bad. Her argument was that the API already knows the mapping so creating another mapping on the front end was overkill and not needed when you know the value you need to compare against.1
-
Trying to configure a smartphone which was already optimized for elderly users, with a more simplistic launcher, larger font size etc.
But the underlying Android 7 and its apps still keep showing up with their inconsistent UI and nagging messages and suggestions.
Is it even possible to configure any Android device to make it really simplistic and distraction free like, say, a classic NOKIA before the age of smartphones?
Culprit no. 1 Google and Android system. Suggestions about features keep recurring, even after stating that we are not interested in the feature.
Culprit no. 2 WhatsApp, unfortunately still the most popular messaging app in Germany, so this crappy bullshit software by Mark Fuckerberg's company has to be installed. Even to me as a tech savy developer, WhatsApp has a confusing user interface that tries to promote features like status (their versions of stories) without any option to hide / turn off.
How shall an 80 year old senior learn to use the app when they previously only used SMS and voice calls? I don't know.7 -
@highlight
disabled: Set<string> = new Set();
@highlight
<input
class="form-control"
id="pushBack"
type="text"
[attr.disabled]="disabled.has('pushBack') ? ' ' : null"
[(ngModel)]="local.pushBack"
/>
---
Do you know what's wrong with this code? If you know and you are a junior how would you tell this to your super boss without hurting his feelings?7 -
I recently got promoted to "Senior Software Engineer", but plan on leaving my company in the next few months. Should I put this new title on my resume or keep it as "Software Engineer"?
There are no new responsibilities with the new title.2 -
A friend of mine gone through 6 interviews, 2 Technical Interviews with tests, 1 personality test, the overall of all of this process was positive . As the recruiter feedback of each step of the recruitment process.
Yet they didn't hire him because they wanted a "Senior senior" as they said.
What does that mean ?
(he already has 6 years of experience and a bachelor's degree. The job is based in holland)5 -
"The Senior Developer told me I was wrong but I proved that he was in fact wrong." - Why are there so many rants like this? What's the significance of the "Senior" part? Are you just telling the world you are better than "Senior" or do you just want to put them down?3
-
How do you deal with a toxic workplace environment. More specifically a senior that don't want to take responsibility and a SM that takes on more a role of a project manager than a scrum master?
Any advice would be great
For context I am a junior but work for nearly 2 years on this project2 -
HOW ABOUT YOU ?
To me the difference between #senior and #junior is :
senior able to teach and junior able to learn this much depends on technical skill.2 -
so they brought a senior engineer to our (very small) dev team. I feel like poking my eyes with a nail looking on his code.1
-
How are you handling junior/senior relationships, were you are the junior and have the feeling of being a burden on the senior?6
-
How does it feel to be a Senior Dev? Is it really that bad?
https://youtu.be/MbUvTbD9q4A
https://youtu.be/owRtiOaVY_k4 -
Love the way our "senior" dev jumps into a project without reading the docs or even comments for that matter, removes and shifts things around then sits with me for 3 hours wondering why it won't work.
-
My coworker and I were supposed to direct a senior project for a local university. Somehow, the professor did not get our project submissions. No senior project this semester 😞
Top Tags
Weekly Rant
View