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
Search - "senior programmer"
-
Biggest hurdle? Probably other people telling me no.
- My parents wouldn't let me go to college to study CS because 'this computer thing is just a fad and you won't be able to make a living off it'. Instead they pulled me out of school early and made me go study automotive so I could be a mechanic like my dad.
- At 22, my boss at my first tech company job heard I was taking Java classes in the evenings. Told me to stop wasting my money because I'd never be a programmer.
- Got a job at a game development company as a document writer. I could code by then. When I was done with my work I'd look for bugs and send the solutions to the programmers so they could submit them. Tech lead found out and flipped out. Said I wasn't allowed to look at the code because I 'hadn't been hired as a programmer'.
Today I'm a senior developer and pretty happy with my career.
When people tell you that you can't do something, that should be all the motivation you need to work your ass off to prove them wrong.15 -
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 -
A fellow intern recommended the use of windows server for security and speed reasons.
Few details about the situation: windows server got hacked due to a vulnerability which had no patch released yet and this had happened multiple times that year. Also, the company was migrating everything to Linux (servers).
The senior/lead programmer literally gave him a GTFO face and pointed at the door.
Everyone was giving him the GTFO face by the way, he didn't know how fast he had to get out 🤣8 -
So i've been a dev manager for a little while now. Thought i'd take some time to disambiguate some job titles to let everyone know what they might be in for when joining / moving around a big org.
Title: Senior Software Engineer
Background:
- Technical
- Clever
- Typically has years experience building what management are trying to build
Responsibilities:
- Building new features
- Writing code
- Code review
- Offering advice to product manag......OH NO YOU DON'T CODE MONKEY, BACK TO WORK!
Title: Dev Manager
Background:
- Technical
- Former/current programmer
- knows his/her way around a codebase.
Responsibilities:
- Recruiting / interviewing new staff
- Keeping the team focused and delivering tasks
- Architecture decisions
- Lying about complexity of architecture decisions to ensure team gets the actual time they need
- Lying about feature estimations to ensure team gets to work on critical technical improvements that were cancelled / de-prioritised
- Explaining to hire-ups why we can't "Just do it quicker"
- Explaining to senior engineers why the product manager declined their meeting request
Title: Product / Product Manager
Background:
- Nothing relevant to the industry or product line what so ever
- Found the correct building on the day of the interview
- Has once opened an Excel spreadsheet and successfully saved it to a desktop
Responsibilities:
- Making every key decision about every feature available in the app
- Learning to ignore that inner voice we like to call "Common sense"
- Making sure to not accidentally take some advice from technical staff
- Raising the blood pressure of everyone below them / working with them
Title: Program Lead / Product Owner
Background:
- Capable of speech
- Aware of what a computer is (optional)
Responsibilities:
- Sitting down
- Talking
- Clicking random buttons on Jira
- Making bullet point lists
Title: Director of Software Engineering
Background:
- Allegedly attended college/university to study computer science
- Similar to a technical product manager (technical optional)
Responsibilities:
- Reports directly to VP
- Fixes problems by creating a different problem somewhere else as a distraction
- Claiming to understand and green light technical decisions, while having already agreed with product that it will never happenrant program lead practisesafehexs-new-life-as-a-manager management explanation product product owner9 -
There should be a TV show where junior programmers make a software and then one famous senior programmer finds bugs, yell at them and fixes it. The name of the show will be "Coding nightmares".15
-
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 -
I've been a programmer for years now. I've slowly been getting promotions and I'm a senior developer at a large company.
to anyone I look as if I am an extremely good programmer however I constantly feel out of place. I feel like I am way worse at coding than my co-workers and people underneath me but I keep getting complimented on it.
I feel like a fake.
does anyone else feel this?15 -
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
-
At my previous job I was told by "senior" devs that my interest in learning new things and knowing more is not a good thing. And that I should learn to increase my depth in the programming of the product that was being used.
As part of my job I was asked to analyze the product's architecture. I found out that it was needlessly complicated and performed horribly. The senior devs that were on that product for a while had been hiding their mess from the rest of the teams. Needless to say, my report didn't make me very popular with them.
I was asked to help come up with a strategy for testing.
A guy who had just joined our company out of college and me worked really hard for a few weeks and managed to bring testing down from 3 months to around 3weeks. Our reward: he was fired(albeit for different reasons. The company was trying to restructure)
My yearly review was terrible and I was put on 2 months probation. So I quit.
It sucked. And made me question my ability as a programmer for a while. I've floated my own firm and though money is hard sometimes, it so much more rewarding.9 -
Me (as a Senior developer): How will you solve this problem using regular expression?
Junior developer: *Explains*
Me: Good
Junior developer: I truly feel like a programmer when I code regular expressions
Me: Now, we have two problems.26 -
I just had my worst hackathon so far and need to puke my whole toxic hatred, the rant will be full of hate so be warned. (I just don't want to let it go on my girlfriend, but I need to shout it out loud somewhere)
First of all, it is alright to be a beginner at a hackathon. It is also alright to not know that much about coding and want to learn. But it is not alright to lie about your skill, pretend to be a senior programmer and waste my fucking time.
Don't even fucking dare to say your are "fit" in Android development if you just have done some foobar tutorial on YouTube, don't even bother to read the document and have literally non existent knowledge about computer science.
Why the fucking hell do you need to pretend to be a seasoned programmer if you are just a bloody beginner? I mean you are in a hackathon full of computer nerds so soon or later your impostor ass will be debunked so what is the point?
And the other guy. Why the fucking hell did.'t you say that you just begin Python for 3 months? You are not a fucking developer if you just started coding for 3 fucking months. Learn some fucking coding before starting with machine learning you fucking punk ass bitch script kiddie.
Alright, maybe I was too naive to not check my teammates' background before make a team with them. Fuck me and my fucking stupid ass. My dumb ass monkey brain fell for big mouths, I deserved the headache right now and none less.
Lesson learned!9 -
So, today I asked my senior developer a query he took my laptop and changed the ide theme to black.
My doubts were solved, I am enlightened programmer now.8 -
I'm working in a blockchain company for $180 as a junior programmer and there is a mid-senior guy who get ~8 times more than me. So we got a project to make a backend API with its tests. When I was partly completed my part of the project I asked that "mid-senior" to share his code with me. Nothing was done, and he asked me to push my changes to git so he could start to do something (view at my code and start copying). BUT. He couldn't even pull from git. He couldn't use that fucking Visual studio's team explorer and even the solution explorer. Ok, he was working with VS for the first time, but I did too. I cloned the repo gave him the environment to start "working" and get back to my work. After that nothing changed, he was writing each one-lined if block for half hour and the code was very dirty. Finally I've got his laptop and started to writing his part by teaching him all the programming. You may say I'm mad. I really do, I think that I did all project. This is sad... How can people get this much by being this far from the programming? We need really high quality programmers.3
-
Job title: "Junior Application Developer"
Rest of job description: "4 years experience...Career level: Experienced hire/Professional"
Meaning: "Looking for a senior level programmer willing to work for a junior salary."
I hate job hunting.2 -
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 -
First rant (hello everyone), just wanted to share my experience of my recent job search.
I had worked about 2 years for one of the bigger companies in my country when I decided I had enough with their bs (I have some decent rants from that company if someone's interested) and I wanted to move back to my hometown. I applied for a few jobs in smaller companies , one which I personally knew the lead programmer of, and he really wanted me to work there. One other company responded quickly and after a couple of interviews I got an offer from them. By that time I haven't heard anything from the first company, so I called them. The CEO was in a meeting but would call me when he was done about am hour later. Didn't hear from him. So I called them again, this time he answered. He seemed really interested and said they were just working some things out, so I said that I needed an offer soon since I already got an offer from another company. His response (without me telling anything about the other company):
"We're not going to be able to match the salary so if you only care about money you should take that. We want you to work for us because you want to, not because of the money"
Well that doesn't pay the bills, so I simply stated:
"I appreciate your honesty and good luck finding anyone"
I hadn't really understood just how bad that was until I told my wife and she pointed it out. The thing is, the company that gave the offer first was really for a junior role, but they increased the proposed salary when they saw my CV. The shitty company was looking for a senior dev. Yeah, good luck finding a senior dev wanting to work without getting properly paid.
Anyway, took the first offer and haven't been happier!11 -
Me: I need more programmers for the project.
Boss: You have 4 people, that's enough.
Me: I have 3 juniors taking 50% of time of a senior (me) contributing less than a medior and rest of my time goes to managing project. I know that in 6 months time invested in them will start paying off, but right now I need more people. Also I don't have me, by that logic, cleaning lady comes to the office every day and we couldn't work witout her, so there's 5 people, at least.
Boss: You'll manage.
Inner me: I would if I was working 8 hours as programmer without tutoring and managing.
Me: Sigh.3 -
junior programmer look at programming memes:
these are all just memes right right ?!
senior programmer : -
Why management people thinks that a career path for any senior developer is to be a "leader" and be good in business side. Its like saying "hey you are a good programmer, let me take away that work you love to do and do stupid human resource management instead"5
-
I'm a junior programmer at a small company with mostly web dev. I had a C# project and before the deadline I granted access to the project repository one of my boss/senior coder. Several hours later I got an email with the whole project zipped and a note: I made some modifications, check it out.
Why someone doesn't want to use some kind of version control system?1 -
Spent 18 hours debugging and finding a fix for a critical bug, casually told about the fix to a senior programmer and left home. Couldn't go to office the next day and what I see on the day after that is endless mails praising the senior guy for fixing the bug. He stole my fix!4
-
Declined a job offer with a startup, partly because of imposter syndrome. Applied for position as programmer, showed up for interview and got cold feet when it turned out they actually wanted/needed a senior programmer/chief technology officer and offered me the position after having asked me no technical questions, seen none of my code or previous projects.
Still, it was a job that paid money... And I'm still jobless two months later :(7 -
This happened with one of our senior profs during the first year of my college. I wouldn't call him a dev if my life depended on calling him a dev but regardless, I narrate the story here.
We were "taught" C++ by some really dumb professors during our first year of college and it was mandatory that everyone cleared the subject regardless of what field of engineering the students chose. Having already done 2 years of C++, it was quite a breeze for me. But during the final lab exam, one of my friends requested my help in solving the quite tough question (for those beginners). Thinking the exam and teaching was unfair, I stupidly wrote the answer on a piece of paper and passed it to him. One of our teachers, who had seen him ask me, was lying low waiting to catch me in the act and she swooped in and busted our asses kicking us out of the exam hall and sending us to the HoDs office like some prize from her war against academic corruption.
In the end, I failed the exam for cheating and had to redo (not only the exam but the entire lab course).
When I returned to college during the summer vacations to redo the course, I first met the antagonist of our story. Having a huge head that looked like a deformed watermelon and an ego the size of a building, he assaulted us first with a verbal diarrhoea of his achievements as a CS professor. I quickly realised that I was in a class of people who had failed to grasp how to make a program that printed "Hello World". To make things shorter, every question the prof gave us, I managed to solve in a mere matter of minutes, several better than his own solutions. Not having expected a student who knew his shit, he was determined to play me down. He hurled tougher question at me and I knocked them over his enormous head piercing his ego. He asked me such questions as how to reverse 1000 and get 0001 and wasn't satisfied with the several ways I gave because none of it were what he had in mind (which turned out to be storing them in a fucking array and printing them in reverse. That's printing not reversing you dung beetle). I kept my calm throughout but on the day of the final exam, he set quite a tough paper for a class of people who had already failed once. To his utter shock and dismay, I aced that too and I produced flawless code. This man who has an MTech from one of the most reputed colleges of my country then proceeded to tell me that he had to cut my marks because I had used more than one function when the question had asked for one function ( it never said only one). I lost my shit and pointed out that since I was the programmer, it was my wish how I coded. I also explained to him how repeating code is a bad practice and one should use functions to reduce redundancy and keep the code clean. Nevertheless, he lost his shit and he threatened me with consequences as apparently "I didn't know who I was messing with". I handed over the paper and stormed out of the class (though he called me back and tried to argue more with me. I apologized for losing my shit and left when he was done talking). I ended up getting a 'C'. Totally worth it.4 -
Right so I'm new here. I don't really bitch much. Just want to see what it's like.
So I was hired supposedly for my java skills. I've been here 11 months. I've written exactly 0 lines of Java. On plus side I have gotten the opportunity to learn c# on the job but on the downside I spent my first 6 months fighting to get admin rights. I'm on my fourth company laptop (don't ask) and every time I have do the fight again. So I wound up doing a lot of not-programmer-stuff while I was waiting on admin rights. Apparently a lot of this is now permanently part of my job.
I was chatting to one of the more senior guys in another team here and he said he hated the first few years of his career, just doing "stupid front end stuff, move this box over there, make that button look pretty" meanwhile I'm sitting here wishing I could have the chance to at least be writing code4 -
So I just recently found out there's a local idol group named MNL48 in here.
Basically bringing the seiyuu/J-Pop culture in the Philippines.
...
Maybe I should've became an idol instead of a senior high school programmer :/3 -
The `sed` command skills of my senior dev (team lead) is equal to every skill I (junior dev) have ever acquired until now as a programmer.
Just amazing !1 -
I am a junior web developer, currently working in my first job for a small company, I was hired because I have an interest in meteor and modern web dev.
When I say small I mean I am the only full time js dev.
So the project we are working (my first ever professional project from start to finish) is a travel booking web app (being a little vague, for the sake of privacy). I am the lead developer, as a new programmer of a project that is far from trivial. There are no other javascript devs in office, no sort of code review. We have an outsourced dev but as I got in a flow with one dev my boss supposedly told him to do it part time (without discussing with me), but haven't heard anything from him, so assuming he's just disappeared (probably annoyed at being treated like a commodity).
Boss has set up the stages, and forces me to move on to the next stage before that stage has been finished. I will have to go back over the whole thing to finish things off.
He will only hire cheap juniors, one front end guy with barely any experience is styling the site.
He is used to churning out WordPress and Magento sites.
Wish I had a senior I could learn off.
I want to stick at this project and see it through, but i can only see it ending in a train wreck.
At the same time I want out, I want to work under a better team with senior programmers and better code review.
I just have to do my best and see how it goes I guess6 -
Switching from a camel cased standard(js) to a snake cased standard (rust) tutorial
pub fn do_shit() {°°°}
...
pub fn doMoreShit()°°
*Notice wrong case*
To self:
Aaarghbkflahvflw. Why can't you fucking get the damn case right! And you call yourself a fucking senior programmer, you piece of useless shit.
#existentialCrisis
#questioning_life
pub fn do_other_shit()
...3 -
A meeting to redefine the definition of done. Which a "senior" programmer threw in.
3 hours after we are still there to "define"... All of this because this developer and a couple more want to keep a physical board which has no space for a "testing" section, so the tasks need either to be done-but-not-really and this is technically wrong (who cares?) or in-progress-but-not-really which is technically wrong (again, who cares?).
Just effin find a bigger board and don't waste 3 hours of my life and/or start thinking pragmatically and accept tasks can move backwards or have a ticket saying "testing" stuck to them, ffs!
The funny part? This dev is probably one of the grumpiest devs I met when you talk about meetings which are actually useful.4 -
The worst part of being a dev? Working in teams.
And I don't mean that in the "I'm the best ninja code wizard in the whole world and you're all holding me back" kinda way. I'm thinking more in the lines of someone who has to deal with that kind of attitude on a daily basis. As someone who recently was put in a leading position in a dev team, this is by far one of the worst experiences that came with it.
Some examples?
- One dev completely changed the naming scheme for variables in a class he worked on for one. single. bug fix. His reason? He just didn't like it!
- Another one noticed that data he was supplied with was not in the specified format. Instead of flagging this with the project leads, he just rewrote his parser to fit the data. A couple of weeks later the supplier noticed the error, fixed the format and suddenly everyone wondered why the software failed processing the data.
- Or that one senior dev, that just refuses to accept changes because "it was always done like this and it worked" No, it didn't. That's why it was changed!
Once a dev team reaches a certain size, people need to realize that stuff like coding rules and process guidelines are not there to annoy them but to help the whole team work as efficient as possible. I don't care how good a programmer you are, if you can't check your ego you don't belong in any kind of team-oriented development project! -
I have a co-worker who won’t stop “refactoring” our codebase. He will go on a long tangent — under the guise of working on a proper story — and then reveal proudly after a few days that he now introduced a new middle-layer into the code which will help us such and such.
I have never seen any benefit from this. I think sometimes cleaning up variable names is nice, but a lot of the things just add noise and complexity. He’s a junior dev, I’m a senior dev. My progressional opinion is that he is doing a bad job. Management doesn’t know the full extent and the lead programmer scolds him every now and then but in the end let’s the code changes pass code review. “It has already been implemented so what’s the harm”.
Then the rest of us are stuck with horrible merge conflicts. I recently noticed that some new business-important unit tests that I wrote were mysteriously gone. Oops — lost in some misguided refactoring I guess. I’m assuming they were failing after the refactor, so clearly they had to go... Fortunately the underlying logic still works I think.
His main tactic in all of this seems to be to just use argumentative stamina. He will lose discussion after discussion but doesn’t seem to care. He’ll just talk and talk. And the in the end the lead tech gives in. And/or doesn’t have the energy to catch the error introduced.
I swear, the company would be better off without him. Maybe even better if we keep paying him but he just cleans the toilets instead. Sometimes I almost believes he gets up in the morning to come to work and just fuck with people all day.2 -
Here comes lots of random pieces of advice...
Ain't no shortcuts.
Be prepared, becoming a good programmer (there are lots of shitty programmers, not so many good ones) takes lots of pain, frustration, and failure. It's going to suck for awhile. There will be false starts. At some point you will question whether you are cut out for it or not. Embrace the struggle -- if you aren't failing, you aren't learning.
Remember that in 2021 being a programmer is just as much (maybe even moreso) about picking up new things on the fly as it is about your crystalized knowledge. I don't want someone who has all the core features of some language memorized, I want someone who can learn new things quickly. Everything is open book all the time. I have to look up pretty basic stuff all the time, it's just that it takes me like twelve seconds to look it up and digest it.
Build, build, build, build, build. At least while you are learning, you should always be working on a project. Don't worry about how big the project is, small is fine.
Remember that programming is a tool, not the end goal in and of itself. Nobody gives a shit how good a carpenter is at using some specialized saw, they care about what the carpenter can build with that specialized saw.
Plan your build. This is a VERY important part of the process that newer devs/programmers like to skip. You are always free to change the plan, but you should have a plan going on. Don't store your plan in your head. If you plan exists only in your head you are doing it wrong. Write that shit down! If you create a solid development process, the cognitive overhead for any project goes way down.
Don't fall into the trap of comparing yourself to others, especially to the experts you are learning from. They are good because they have done the thing that you are struggling with at least a thousand times.
Don't fall into the trap of comparing yourself today to yourself yesterday. This will make it seem like you haven't learned anything and aren't on the move. Compare yourself to yourself last week, last month, last year.
Have experienced programmers review your code. Don't be afraid to ask, most of us really really enjoy this (if it makes you feel any better about the "inconvenience", it will take a mid-level waaaaay less time to review your code that it took for you to write it, and a senior dev even less time than that). You will hate it, it will suck having someone seem like they are just ripping your code apart, but it will make you so much better so much faster than just relying on your own internal knowledge.
When you start to be able to put the pieces together, stay humble. I've seen countless devs with a year of experience start to get a big head and talk like they know shit. Don't keep your mouth closed, but as a newer dev if you are talking noise instead of asking questions there is no way I will think you are ready to have the Jr./Associate/Whatever removed from your title.
Don't ever. Ever. Ever. Criticize someone else's preferred tools. Tooling is so far down the list of what makes a good programmer. This is another thing newer devs have a tendency to do, thinking that their tool chain is the only way to do it. Definitely recommend to people alternatives to check out. A senior dev using Notepad++, a terminal window, and a compiler from 1977 is probably better than you are with the newest shiniest IDE.
Don't be a dick about terminology/vocabulary. Different words mean different things to different people in different organizations. If what you call GNU/Linux somebody else just calls Linux, let it go man! You understand what they mean, and if you don't it's your job to figure out what they mean, not tell them the right way to say it.
One analogy I like to make is that becoming a programmer is a lot like becoming a chef. You don't become a chef by following recipes (i.e. just following tutorials and walk-throughs). You become a chef by learning about different ingredients, learning about different cooking techniques, learning about different styles of cuisine, and (this is the important part), learning how to put together ingredients, techniques, and cuisines in ways that no one has ever showed you about before. -
Even seniors make mistakes. In case you were ever doubting yourself - just remember that.
I just had a very senior level programmer on my staff add a function to a production system that issues an SQL UPDATE query without a WHERE clause. Fortunately, only the 1st entry succeeded and the rest failed due to "duplicate record" errors. Clearly he had intended to do a SELECT to check if an entry was present. If it was present, do an UPDATE, otherwise do an INSERT (think UPSERT - but done manually). However instead in the insert part they were both UPDATE's. The first update was normal looking but the second UPDATE was just this weird malformed-looking thing where he tried to do an UPDATE but to every field including the key fields. Clearly he was thinking about an insert but actually writing it as an update. Every now and then I need to remind myself that these things happen. The guy's not dumb - just made a mistake.
I'm just happy it "failed unsuccessfully".4 -
I *hate* it when a senior asks me to write a functional test report. Like I thought we hired functional testers to do that sort of stuff? I'm a programmer, I only write 3 things: code, documentation, and more code. Not freaking reports about how something did not work before, and after this 1-line fix does work. Oh and don't forget to include screenshots and a description of the issue. Arghhh4
-
I'm super pissed off... I recently got this job, I've been here for three months but in the current project for a month and a half... in this time I learned Laravel and the project is no big deal, I'm more than happy to learn but I'm working with a "Senior" programmer who "has a lot of experience" and "knows a lot" and "very friendly"... the thing is that we use Jira and BitBucket to assign work and control versions, however, the motherfucker doesn't do a shit and when I ask him about something, he totally ignores me... I checked on the latest merges and tickets and I've done like 50 within this month and a half and he has done like 15... He also made me do a big ass thing with a PDF and at the end he completely destroyed it and just used a table with no styles that looks like shit. He took 40 minutes to tell me something he already knew about the models because "I'm sorry, I got distracted"... What should I do?2
-
When a senior programmer told you they're done implementing the feature but don't know how to write the unit tests1
-
High school robotics team. Total of three programmers and one coach who understands programming concepts, but not syntax or anything. One programmer, putting it bluntly, is incompetent and doesn't even bother to learn anything. The other one that isn't me is apparently fucking lead programmer and team leader (IM A SENIOR. SHES A FUCKING SOPHOMORE. WTF.) and she has done about 5% of the programming this year. I've done the rest with the help of a programmer from Ford whom we bring in. All she does is tell you to do shit for her, and if you don't, she pulls the authority card on you.
And I have maybe three days, after a full day of school mind you, until I need almost every part working on the robot code. Fuck me.1 -
Can I list this experience? Will it look bad?
I am an entry level programmer in a software shop, or whatever they are called. I was given no mentorship on the task I have done. Not even proper documentation and it seems management is passing me around. What I mean by that is that the task I work on no one has ideas about since it seems the last guy who was responsible left. He was a senior though and it seems that I might have been too eager to find a job. Now I am being tasked for things a senior would do but I have the entry pay and knowledge and skill set. 2 months experience...
I am going to design a whole system from scratch and they have not read anything on it. From networking to applications to fees to compliance requirements. Oh the great part is they want it soon, no pressure, but we have to start certification within a tight deadline. This is a great opportunity and maybe a dumpster fire waiting to start. I will gain so much real experience but they are taking a great risk. It seems that is throughout their code and infrastructure though.
I plan to leave after the project. I also will document and hopefully they start reviewing my stuff to catch my incompetence. Not on purpose but from pressure and inexperience, which I hate cause I was excited at first.
I plan to stick the year or until Covid strips work-from-home, cause they are bit “old school”. I will begin my job search as well. I just know I will burn out long term and the money and package is shit.
Do I list them if I leave earlier but finish the project?8 -
I’m really getting fed up with the situation I am in!
I was brought in as a development lead, which in my eyes and from the sound of it leading on the technical delivery, inspiring and leading technical development decisions and generally leading my team (one additional dev) in the delivery of work items and user stories which the PM or Business analyst produces..
Then it “evolved” into what felt more like a development manager where I was reporting to senior management on KPIs and stuff, I sucked it up and did it.
Then they brought in two new people which they call application specialists. These people spend all their time managing existing off the shelf applications, communicating with the vendor, running user groups where they work with our users on moving the product forward and planning the configuration and enablement of new functionality.
Because they are “developing” the application (in the same way a child develops, or the same way a story line develops and evolves) they fall under me..
So now I spend a split amount of time developing software and also managing what I can only explain as project managers, product owners...
Oh but then it gets better!! Now they want me(as well as our info sec lead and our infrastructure lead) to be a kind of all round delivery lead, gauging the requirements of a project, reporting in its risks to senior management, resource planning, everything a PM does! And also be the technical person delivering these projects!
Honestly, it’s seriously starting to take the fucking piss!
I am a technical programmer, a pretty good one if I say so myself, the developer reporting to me is good but needs hand holding which I am ok with! But would never be able to deliver an element of a product by himself in line with what we expect in quality of code..
Why would anyone think you take a person built and only interested in doing a technical role and make then a generic all round manager of a project??
I know why they did it! It’s because there are other managers in our department paid the same “level” as me, but because of their management responsibility’s , I however feel I am paid this much for my technical experience and abilities, thy are just blanket covering everyone the same at this level.
You would never get a manager at this salary scale with the technical skills they need, and you would never get a technical person with the skills interested in doing that type of management at this salary scale!
I’m just a mug and they know it!
So fucking angry!3 -
So this "senior" programmer tells me that redux should only connect to the upmost react component and then IT should pass props down..... Like why even use redux then? WTF1
-
Today a recruiter messaged me on Facebook. Week ago, I left a post with my CV on a programming group-currently I'm looking for a junior JAVASCRIPT (important ! ) /Node.js position, explicitly said so.
R(ecruiter): "Hello sir, we noticed your post with CV on group XYZ, are you still looking for a job?"
Me: "Yes, of course."
R: "We are building a new team in city X, remote work is possible. I will send you job posting right away."
Started reading it, job title is SENIOR JAVA DEVELOPER. Okay, maybe she sent me wrong document, maybe she wanted me to read just a bit about company and every job posting is pretty generic.
Me:" This job posting is for a senior programmer, I take it you're looking for juniors too ? I would happily take it, it's just I want a job to learn more things. Did you read my CV?"
R, annoyed: "Requirements for this position are quite clear, I believe. We are open to working with people with different experience level."
From there, she was pretty negative but I remained sympathetic and agreed to met with her boss next week. After all, maybe he has a position for me.
"Java and Javascript are similar like Car and Carpet are similar" -
I probably knew I wanted to be a dev/programmer in late highschool. I was fascinated by the underlying structure to what I see on a computer screen, and idolized those who "hacked" as a form of political rebellion.
Now I'm in my senior year in college as a Computer Engineering major because CS was ridiculously competitive at this college. I'm actually quite happy about this, because I feel I know more about computers in general by taking this path rather than CS. -
So at work, I was trying to convince a senior programmer to adopt Golang for a new project that would need to handle large amount of throughput as oppose to Django with gunicorn and other optimizations (which is what we usually do).
The response was "we'd have a hard maintaining it, as no one really knows Go and it will be hard to hire people with Go knowledge".
So my question: "in your opinion, is that a good reason?" I have some go experience from other jobs, it seems like a superior solution for this problem.6 -
In reply to this:
https://devrant.com/rants/260590/...
As a senior dev for over 13 years, I will break you point by point in the most realistic way, so you don't get in troubles for following internet boring paternal advices.
1) False. Being go-ahead, pro active and prone to learn is a good thing in most places.
This doesn't mean being an entitled asshole, but standing for yourself (don't get put down and used to do shit for others, or it will become the routine) and show good learning and exploration skills will definitely put you under a good light.
2)False. 2 things to check:
a) if the guy over you is an entitled asshole who thinkg you're going to steal his job and will try to sabotage you or not answer acting annoyed, or if it's a cool guy.
Choose wisely your questions and put them all togheter. Don't be that guy that fires questions in crumbles, one every 2 minutes.
Put them togheter and try to work out the obvious and what can be done through google or chatgpt by yourself. Then collect the hard ones for the experienced guy and ask them all at once. He's been put over you to help you.
3) Idiotic. NO.
Working code = good code. It's always been like this.
If you follow this idiotic advice you will annoy everyone.
The thing about renaming variables and crap it's called a standard. Most company will have a document with one if there is a need to follow it.
What remains are common programming conventions that everyone mostly follows.
Else you'll end up getting crazy at all the rules and small conventions and will start to do messy hot spaghetti code filled with syntactic sugar that no one likes, included yourself.
4)LMAO.
This mostly never happens (seniors send to juniors) in real life.
But it happens on the other side (junior code gets reviewed).
He must either be a crap programmer or stopped learning years ago(?)
5) This is absolutely true.
Programming is not a forgiving job if you're not honest.
Covering up mess in programming is mostly impossible, expecially when git and all that stuff with your name on it came out.
Be honest, admit your faults, ask if not sure.
Code is code, if it's wrong it won't work magically and sooner or later it will fire back.
6)Somewhat true, but it all depends on the deadline you're given and the complexity of the logic to be implemented.
If very complex you have to divide an conquer (usually)
7)LMAO, this one might be true for multi billionaire companies with thousand of employees.
Normal companies rarely do that because it's a waste of time. They pass knowledge by word or with concise documentation that later gets explained by seniors or TL's to the devs.
Try following this and as a junior:
1) you will have written shit docs and wasted time
2) you will come up to the devs at the deadline with half of the code done and them saying wtf who told you to do that
8) See? What an oxymoron ahahah
Look at point 3 of this guy than re-read this.
This alone should prove you that I'm right for everything else.
9) Half true.
Watch your ass. You need to understand what you're going to put yourself into.
If it's some unknown deep sea shit, with no documentations whatsoever you will end up with a sore ass and pulling your hair finding crumbles of code that make that unknown thing work.
Believe me and not him.
I have been there. To say one, I've been doing some high level project for using powerful RFID reading antennas for doing large warehouse inventory with high speed (instead of counting manually or scanning pieces, the put rfid tags inside the boxes and pass a scanner between shelves, reading all the inventory).
I had to deal with all the RFID protocol, the math behind radio waves (yes, knowing it will let you configure them more efficently and avoid conflicts), know a whole new SDK from them I've never used again (useless knowledge = time wasted and no resume worthy material for your next job) and so on.
It was a grueling, hair pulling, horrible experience that brought me nothing in return execpt the skill of accepting and embracing the pain of such experiences.
And I can go on with other stories. Horror Stories.
If it's something that is doable but it's complex, hard or just interesting, go for it. Expecially if the tech involved is something marketable.
10) Yes, and you can't stop learning, expecially now that AI will start to cover more and more of our work.4 -
Hey senior programmer out there. Please give one good reason to continue using JSON.
(When i'm dealing with AJAX, i insert a specific symbol in the string returned by the server and later on the front end , i just split that string to separate my data.
And JSON has become useless to me since16