AboutI always assume the newbie. You'll find between design and code.
Joined devRant on 10/31/2022
Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple APILearn More
My colleague wanted me to examine a script issue. I open it up, and it took several minutes to comprehend how it worked. Once it finally clicked:
Me: I can’t decide if this is idiotic or genius.
Colleague: Well, YOU wrote it.
Me: Oh… Genius it is, then!
TLDR : Some dude was immediately fired by creating union. The email from the CEO of Sii Poland (one of the biggest software houses in the country) shocked the whole IT community14
so current elon - Twitter situation is like this:
EM - i will buy this company for 44B
Twitter: what!? 44B for this crap? our ESOPs will make us millionaires! sure , go ahead.
EM - Sike!! i was kidding. no deal
Twitter - NO BACKSIES!!! *sues*
EM - ugh, okay. i will buy this company, but i want full ROI in next 5 years + 50% of you are fired
Twitter - Whaaa!!!
i guess some disaster was expected from this takeover and twitter mgmt throwed themselves on the axe on their own.
but it's wierd why every CEO change comes with an immediate firing of staff16
I am back after 5 years
It's been a long time
After working for a shitty company, I ended up working for a startup for an interesting big project as a software architect
It was a good experience just for some stuff, but I hated every moment we needed to build some demo or prototype for potential customers or allies
I was tired... 2 years of demoing is too much. And finally I got a Senior Devops in this company working in Kubernetes
I finally discovered my role and my position, I want to solve problems for other devs and myself. I help anyway in the final product, because fast and reliable build and release cycle need to be a must
I wish everybody could find their main role. I took 12 years to find mine lol
JUST ONCE DOCUMENT YOUR FUCKING LIBRARY!
YOU RUIN MY DAY, MAKE ME WORK 12 HOURS A DAY, TO RESOLVE SUCH BASIC FUNCTIONALITY
YOU FUCKING CLOWN!!!!!!!!!
I'D BETTER DELETE THE ENTIRE APP AND START FROM SCRATCH, WOULD BE EASIER THAN USING YOUR SCUM OF THE EARTH PIECE OF SHIT LIBRARY4
So uh... I got fired today. I asked them what could be the reasons. They told me that I am "capable" and a bunch of positive things. I asked them can't the reason they fire me is due to all the positive things. Is there a particular reason?
I asked them the reasons again and again. They say was all fine.
Then the email stated I am fired due to "Not working, not contributing and underperforming". Which I asked them to clarify.
They say they prefer someone who has a corporate mentality and is obedient. As more ideas will cause "unrest" for the company.
I am genuinely confused.
Anyway, I am back to freelancing.19
After over 20 years as a Software Engineer, Architect, and Manager, I want to pass along some unsolicited advice to junior developers either because I grew through it, or I've had to deal with developers who behaved poorly:
1) Your ego will hurt you FAR more than your junior coding skills. Nobody expects you to be the best early in your career, so don't act like you are.
2) Working independently is a must. It's okay to ask questions, but ask sparingly. Remember, mid and senior level guys need to focus just as much as you do, so before interrupting them, exhaust your resources (Google, Stack Overflow, books, etc..)
3) Working code != good code. You are an author. Write your code so that it can be read. Accept criticism that may seem trivial such as renaming a variable or method. If someone is suggesting it, it's because they didn't know what it did without further investigation.
4) Ask for peer reviews and LISTEN to the critique. Even after 20+ years, I send my code to more junior developers and often get good corrections sent back. (remember the ego thing from tip #1?) Even if they have no critiques for me, sometimes they will see a technique I used and learn from that. Peer reviews are win-win-win.
5) When in doubt, do NOT BS your way out. Refer to someone who knows, or offer to get back to them. Often times, persons other than engineers will take what you said as gospel. If that later turns out to be wrong, a bunch of people will have to get involved to clean up the expectations.
6) Slow down in order to speed up. Always start a task by thinking about the very high level use cases, then slowly work through your logic to achieve that. Rushing to complete, even for senior engineers, usually means less-than-ideal code that somebody will have to maintain.
7) Write documentation, always! Even if your company doesn't take documentation seriously, other engineers will remember how well documented your code is, and they will appreciate you for it/think of you next time that sweet job opens up.
8) Good code is important, but good impressions are better. I have code that is the most embarrassing crap ever still in production to this day. People don't think of me as "that shitty developer who wrote that ugly ass code that one time a decade ago," They think of me as "that developer who was fun to work with and busted his ass." Because of that, I've never been unemployed for more than a day. It's critical to have a good network and good references.
9) Don't shy away from the unknown. It's easy to hope somebody else picks up that task that you don't understand, but you wont learn it if they do. The daunting, unknown tasks are the most rewarding to complete (and trust me, other devs will notice.)
10) Learning is up to you. I can't tell you the number of engineers I passed on hiring because their answer to what they know about PHP7 was: "Nothing. I haven't learned it yet because my current company is still using PHP5." This is YOUR craft. It's not up to your employer to keep you relevant in the job market, it's up to YOU. You don't always need to be a pro at the latest and greatest, but at least read the changelog. Stay abreast of current technology, security threats, etc...
These are just a few quick tips from my experience. Others may chime in with theirs, and some may dispute mine. I wish you all fruitful careers!214
I’m fucking done….
I don’t even know what to tell.
I’m a CTO in a startu. We have pretty good traction, my salary is about average senior dev salary (plus 10%).
I’m good financially.
But I have no more pleasure in work. Like at all.
“This API call performance is bad”
Yeah I know, maybe you shpuldn’t try to call it for 1000 objects at the time ?
“We need to reduce Azure cost”
Yeah I know, but are you ready to live with performances downgrade it will generate ?
“I don’t understand on what thing you worked past week, where is a devops card ?
Fuck you, I’m in extenuating fire mode, I don’t have time for a fucking devops card
Thank you for your imput, Blazor WAS created to avoid JabaScript
“The client has only 1.000.000 records and API doesn’t return them all”
Use fucking paging moron. And BTW, I’m adding “number of authorized requests” shortly.
I can go on and on and on for hours. But the idea is : I completely lost the will or motivation to do anything. I’m considering just to quit and go back to be Junior dev for a random company.9
Have a question about raises.
Working in europe as a junior dev (had 2.5 year experience prior) but lowballed myself (because I had a 1.5 year gap from development) and started working here for 2.5k euro/month salary.
After my 3 months probation I noticed that Im doing better than 60% of my team and as soon as my probation ended I messaged my manager and asked for a raise to bump me up to 3.5k/month.
I am waiting for a raise for the past 7 weeks already. My manager keeps telling me that decision is greenlighted because I got very strong and positive feedback. However CTO is on vacation, once he comes back manager will be on vacation and so on. Basically a corporate clusterfuck.
So basically I will have my raise request approved what? 8 weeks after my original request? Also add a couple more weeks because I guess new contract will be signed from the beginning of next month, not retrospectively. So when I will actually get that increased salary? What the hell.
Since my original request havent even reached CTO yet Im thinking of amending my original request and asking for a bump up to 4k or quit the company and go contracting for the same 4k and pay 17 percent for taxes instead being employed fulltime while paying around 43% for taxes.
I am just pissed off that its taking 2 months to just get the 'okay' and I guess will take 3 more weeks to sign the new contract. It shouldnt be like that, I lost money while waiting so I think it would be fair enough to ask for a bigger bump.4
A young guy I work with burst into tears today, I had no idea what happened so I tried to comfort him and ask what was up.
It appears his main client had gone nuts with him because they wanted him to make an internet toolbar (think Ask.com) and he politely informed them toolbars doesn't really exist anymore and it wouldn't work on things like modern browsers or mobile devices.
Being given a polite but honest opinion was obviously something the client wasn't used to and knowing the guy was a young and fairly inexperienced, they started throwing very personal insults and asking him exactly what he knows about things (a lot more than them).
So being the big, bold, handsome senior developer I am, I immediately phoned the client back and told them to either come speak to me face-to-face and apologise to him in person or we'd terminate there contract with immediate effect. They're coming down tomorrow...
So part my rant, part a rant on behalf of a young developer who did nothing wrong and was treated like shit, I think we've all been there.
We'll see how this goes! Who the hell wants a toolbar anyway?!376
Recruiter: "Take this culture survey. It's not a test. There are no right or wrong answers."
Me, internal voice: Then why give me a list of words to choose from that I think describe me best and another list of words to choose from that describe how I ought to behave at work? Clearly, there's a matchup you're trying to do here. So clearly there's going to be a wrong answer if I don't choose enough of the former to match the latter.4
So because of the sheer number of interviews I’ve been doing I’m starting to get a bit brazen with them since I’ve started to really not give a fuck about most of them and I’ve started to notice patterns in common lines of questioning resulting in this unexpected gem today:
Interviewer: So we always start our devs off on the bottom end of our salary band.
Dev: Either give me the top or I’m not interested.
Interviewer: 😡. But if we start you at the top of the salary band we’ll have nothing to give you later. 🥺.
Dev: No need, I’ll take the money up front. Companies don’t give raises these days anyway, it’s just a carrot to dangle in front of the naive.
Interviewer: 😡. Well if all you care about is money so focussed on money you’ll just leave if a better offer comes around!
Dev: All the more reason to give me the highest number possible to defend against that possibility.
Interviewer: 😡. But there are other devs on the team with similar experience that will be making less than you.
Dev: Sounds like they fell for the negging and guilt tripping you are currently attempting on me in order to save a buck. Salary is not based on your skills or experience anymore, it’s based on your ability to negotiate. Here’s mine.
Interviewer: ………………. I’ll pass you along to the hiring manager.
Dev: ???? wtf
HOW THE FUCK DID THAT ACTUALLY WORK ARE YOU FUCKING KIDDING ME I WAS TRYING TO GET THEM TO HANG UP FOR SHITS AND GIGGLES AND NOW I’M LOOKING AT A 20K RAISE ALL BECAUSE I CONTINUALLY TOLD THEM TO GO FUCK THEMSELVES??? THIS IS ACTUALLY WHAT IT TAKES TO BE TREATED PROPERLY BY A COMPANY???14
I don’t have a real way to find a good company.
As a rule of thumb I avoid startups.
This doesn’t mean all new young tech companies are bad. I avoid the startup rethorics. Those are 🚩 for both new and old companies.
And I avoid crypto, nft and other scam businesses. There’s an high chance that the owners will run away with the money and leave you without a job.6
Got laid off last week with the rest of the dev team, except one full stack Laravel dev. Investors money drying up, and the clowns can't figure out how to sell what we have.
I was all of devops and cloud infra. Had a nice k8s cluster, all terraform and gitops. The only dev left is being asked to migrate all of it to Laravel forge. 7 ML microservices, monolith web app, hashicorp vault, perfect, mlflow, kubecost, rancher, some other random services.
The genius asked the dev to move everything to a single aws account and deploy publicly with Laravel forge... While adding more features. The VP of engineering just finished his 3 year plan for the 5 months of runway they have left.
I already have another job offer for 50k more a year. I'm out of here!13
I hate backendphobia! It feels like so common nowadays. People scare other people with backend being too hard and stuff, and that feeling of scariness is something that infects lot of people. Please stop fearing the backend!
Yes, some backend stuff can be hard, but there's no good reason to fear it. I just hate it when I go to a new team and they all seem to be backendphobics idiots. I've build enough backends to not give in to the fear, pls stop scaring people.12
now a funny thing that happened to me a few weeks ago:
a recruiter contacted me on linkedin... wait, don't laugh yet, that's not the whole joke (this time)...
...asking whether I'm interested in something, I was like yeah, but I'm looking for part-time because i'd like to not have a mental breakdown after 6 months this time...
her response: "well... I don't have any part-times, but I have an almost part-time..."
" 'almost part-time'? first time I've heard that phrase, what exactly does that mean?"
"it means about 160 hours"
... i sit in confused silence for a bit, then write back as I calculate: "i'm assuming you mean 160 hours a month, which is 40 hours a week, which is 8 hours a day, which is full-time. please point out where am I mistaken."
recruiter: * crickets *8
[A thread for those who are curious]
Is monthly salary of USD 4,500 a below average or average salary in your country?
For a software engineer (full stack) (regardless of tech stack), experience more than 5 years.
(Please do let me know where you from as well, just want to know)
In my country (Malaysia) it is consider above average.8
upcoming life choices :
- leave home( and a lifestyle where i live/eat rent free, save 90% of pay check, start work at 12pm and end at 4pm but still renowned for being the most productive engineer, workout and party) to live near office and wfo 3 days/week
- quit a relaxed job + look for a similar role in highly competitive/unstable economy + stay at home with parents who are very much controlling, and repeatedly quarrelling amongst themselves and/or with me/my choices
yepp, both points are true about my home life: its a physical paradise as well as an emotional hell1
Ask questions during interview.
Ask about trainings - it's usually a good sign when company offers training budget. Ask about specifics - sometimes it's a shared pluralsight account, and nothing else, which means that that had an idea and half assed it into existence.
Ask tech recruiter about overtime, a good sign is when they have no idea or say that it must be budgeted and scheduled - it means that it does not happen often.
Ask if it is possible to select and change projects, and how often it happens - if often, it may be bad low level management, or people learning new things and jumping between projects.
Also make sure to ask about rules for promotions and pay rises. Good company wił have a clear set of rules in place.
All of the above apply to mid to large companies.
For small company, i'm sure it will be different.3