Details
Joined devRant on 12/26/2019
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
-
They must be losing good developers at Google, because all of their shit is slowing devolving into hot garbage. Bug ridden pieces of shit. I wouldn’t even pay to use anything of theirs anymore - you are probably better off somewhere else…5
-
Recommended PHP ORM?
Had a couple bad experiences with Sequelize (I know it's JS, save it). Also, I'd like to try the decorators pattern. I'm also looking for good (and I mean GOOD) relationships management (you are allowed ONE pun about it).
Anyone? :((3 -
Merge VS Rebase:
- Did you pick a side?
- Practical tips? Like dealing with merge conflicts
- Have you ever regretted using either?
My answer
* My team squash-merges all branches to master so we don't really care what the branch history looks like. Master history should be pretty - but a branch history can be ugly and filled with a dozen commits.
* Practical tip 1: use `git config rerere.enabled true`. rerere stands for "reuse recorded resolution" and this means if you rebase often you don't have to resolve the same merge conflict twice.
* Practical tip 2: use `git commit --fixup oldcommithash` and then rebase with `--autosquash`
* I like using Rebase. But I have regretted the amount of time I've spent on trying to rebase old branches with many commits only to give up and to `git rebase --abort` since I realised I couldn't handle trying to reapply all the commits chronogically as the changes in the 1st commit were no longer relevant.46 -
I'm considering quitting a job I started a few weeks ago. I'll probably try to find other work first I suppose.
I'm UK based and this is the 6th programming/DevOps role I've had and I've never seen a team that is so utterly opposed to change. This is the largest company I've worked for in a full time capacity so someone please tell me if I'm going to see the same things at other companies of similar sizes (1000 employees). Or even tell me if I'm just being too opinionated and that I simply have different priorities than others I'm working with. The only upside so far is that at least 90% of the people I've been speaking to are very friendly and aren't outwardly toxic.
My first week, I explained during the daily stand up how I had been updating the readmes of a couple of code bases as I set them up locally, updated docker files to fix a few issues, made missing env files, and I didn't mention that I had also started a soon to be very long list of major problems in the code bases. 30 minutes later I get a call from the team lead saying he'd had complaints from another dev about the changes I'd spoke about making to their work. I was told to stash my changes for a few weeks at least and not to bother committing them.
Since then I've found out that even if I had wanted to, I wouldn't have been allowed to merge in my changes. Sprints are 2 weeks long, and are planned several sprints ahead. Trying to get any tickets planned in so far has been a brick wall, and it's clear management only cares about features.
Weirdly enough but not unsurprisingly I've heard loads of complaints about the slow turn around of the dev team to get out anything, be it bug fixes or features. It's weird because when I pointed out that there's currently no centralised logging or an error management platform like bugsnag, there was zero interest. I wrote a 4 page report on the benefits and how it would help the dev team to get away from fire fighting and these hidden issues they keep running into. But I was told that it would have to be planned for next year's work, as this year everything is already planned and there's no space in the budget for the roughly $20 a month a standard bugsnag plan would take.
The reason I even had time to write up such a report is because I get given work that takes 30 minutes and I'm seemingly expected to take several days to do it. I tried asking for more work at the start but I could tell the lead was busy and was frankly just annoyed that he was having to find me work within the narrow confines of what's planned for the sprint.
So I tried to keep busy with a load of code reviews and writing reports on road mapping out how we could improve various things. It's still not much to do though. And hey when I brought up actually implementing psr12 coding standards, there currently aren't any standards and the code bases even use a mix of spaces and tab indentation in the same file, I seemingly got a positive impression at the only senior developer meeting I've been to so far. However when I wrote up a confluence doc on setting up psr12 code sniffing in the various IDEs everyone uses, and mentioned it in a daily stand up, I once again got kickback and a talking to.
It's pretty clear that they'd like me to sit down, do my assigned work, and otherwise try to look busy. While continuing with their terrible practices.
After today I think I'll have to stop trying to do code reviews too as it's clear they don't actually want code to be reviewed. A junior dev who only started writing code last year had written probably the single worst pull request I've ever seen. However it's still a perfectly reasonable thing, they're junior and that's what code reviews are for. So I went through file by file and gently suggested a cleaner or safer way to achieve things, or in a couple of the worst cases I suggested that they bring up a refactor ticket to be made as the code base was trapping them in shocking practices. I'm talking html in strings being concatenated in a class. Database migrations that use hard coded IDs from production data. Database queries that again quote arbitrary production IDs. A mix of tabs and spaces in the same file. Indentation being way off. Etc, the list goes on.
Well of course I get massive kickback from that too, not just from the team lead who they complained to but the junior was incredibly rude and basically told me to shut up because this was how it was done in this code base. For the last 2 days it's been a bit of a back and forth of me at least trying to get the guy to fix the formatting issues, and my lead has messaged me multiple times asking if it can go through code review to QA yet. I don't know why they even bother with code reviews at this point.18 -
Why has programming become dependency management and third party paid libraries implementation?
I hate it.
I want to code some real hard stuff but everything is already made!16 -
I am the nightmare of the recruiters. They're reaching out to me and I am giving them back every experience I received while I was a junior.
I'm arrogant, not responding, gaslighting, shaming, slow responding, sometimes I build up hope for them and just stop communicating with them.
I am a bit sorry but at the same time it feels extremely satisfying and I feel revenge.6 -
I no longer give a single flying fuck about whether this company I work for lives or dies, whether it succeeds or fails. My compensation has been piss poor compared to the level of dedication I have put in and the level of stress I've endured. Up until now, I was thinking like "well, it's a growing startup, maybe if it succeeds it can have some doors open for me". But fuck it.
I keep hearing about software developers doing pretty well for themselves, but I can barely pay my fucking bills with this shit company in this shit country.
I should've started doing this sooner, and I'm a stupid-ass motherfucker for not having been doing it, but I'll be looking for jobs with actual respectable pay now. I'm not bound by a notice time in my contract, so maybe I'll be telling whatever other companies that I can start with them immediately if they need me to.
Seriously fuck this company and its low-ass compensation. If I'm going to be paid this low, I might as well take a less stressful job with less skill requirements.
I will be jumping ship and I won't be caring one bit if it fucking sinks.5 -
I've lost my passion in writing code. I don't enjoy it anymore. They promised me a promotion a year ago, but it never came. I'm just tired.17
-
Finally finished the longest ticket I've ever worked on in my life. The ticket title and description was a pretty simple and straightforward one: "Upgrade from PHP 7.4 to 8".
If it was only so simple in real life. Our application is mostly done with API Platform framework, which is based on top of Symfony framework which is based on top of PHP language.
Once I did PHP 7 => 8 upgrade I needed to upgrade API Platform 2 => 3. But of-course that couldn't have been done as before that I needed to upgrade from Symfony 5 => 6.
This all was literally an equivalent of touching into a wasp nest - it took me a bit over 5 months and 800 hours of work and there was literally not a single source file left untouched.
In the process of all of this I've ran into literally dozen undocumented feature-breaking changes, broken backwards-compatibility promises and inside out architectural changes - from both the frameworks and the language itself.
Upgrading just one major version of anything SHOULD NOT be so hard. And to top it all up just to think I will need to do this again in a year or two..
Experiences like these really set my hate for time-based model of releases and the state of today's development in general.6 -
Can you fucking imagine this tiny fragment of a large complex software built in nextjs?
How many page.tsx and layout.tsx of that exact file names is gonna be there?
How can you track in this folder hierarchy which page.tsx is for which component etc?
How is this clutterfuck of a structure good and loved and approved by developers?
Nextjs is a fucking double edged sword. As much as how good it is it is also bad as bullshit -
Fucking frontenders…
So tired of your fucking hip things…
Always something new…
Always something ”innovative”
Fucking MB and MB and MB of images…
Make it fast you imbecils! It’s 2023!12 -
I’m about to quit this job, this customer don’t care about the people, they just want quick results and people available 24/7, this is taking my mental health, I think I’ll become a farmer instead.3
-
Man, my product owner is so fucking annoying. I am 50/50 between two projects when really it feels like I'm 100/100 - and the PO of one of the projects always requests that I join daily stand ups and give updates.
CUNT.
I don't always have updates because I'm working with another team. Why are you trying to micromanage me you fuck face. Also, you know when you get those PO's that are totally useless and don't actually bring any real value to the project except in the capacity of being a slimey charismatic weasel? Yah, that's this person.5 -
There is a reason why we have Static Code Analysis tools.
Also, there is a reason why we have options to configure them.
Idiots will either try to follow things blindly, or try to skip it altogether. Depends on the monkey leading the band.3 -
I’ve become the person who I said I’d never be. Writing spaghetti code in spaghetti project instead of trying to refactor methods and classes where I’m adding new features.
Welp. They want it “yesterday” , they’ll have it yesterday.
But hey, the money’s good.8 -
"our placeholder shows an @ symbol, but please don't use an @ symbol!"
i'm so happy knowing that the devs and designers who created this app are earning 20x what i am
🤡🌎6 -
imagine your ego being more important than doing something the right way
welcome to corporate hell
this is one of the top reasons (but of course definitely not the ONLY reason) i'll never join the rat race
would rather be a homeless 🤡 (slowly succeeding in this one)4 -
I sometimes put "[Object object]" in input forms, in hopes of making the devs debugging it lose their freaking minds.8
-
Weekly reminder that RECRUITERS ARE MANIPULATIVE, LYING ASSHOLES BY DEFAULT.
Nothing new happened. I have seen the thread about rec scums in Reddit.5 -
I have to get to the point where withdrawal is complete suffering and anger in order to actually quit lol1
-
Iphone autocorrect is truly revolutionary. I truly need these super common words to constantly be changed to complete nonsense.
"in" to "inn"
"an" to "available"
"do" to "doo" or "dou"
"and" to "abs", "ABCs"
Many, many others.
It took over 20 corrections to complete this simple thought.
Soft locks several times a week so I have to hard restart it in the middle of doing things.
$3500 for a VR headset? Where do I sign up?9 -
Man it always feels like i know nothing. Like when you don't know HTML it feels like you know nothing .
Then you learn js, backend, some database.
But you don't know react so fuck you you know nothing.
Then you learn react, but you don't know vite, next
So you know nothing.
this cycle never ends
FUCK8 -
I'm drunk and I'll probably regret this, but here's a drunken rank of things I've learned as an engineer for the past 10 years.
The best way I've advanced my career is by changing companies.
Technology stacks don't really matter because there are like 15 basic patterns of software engineering in my field that apply. I work in data so it's not going to be the same as webdev or embedded. But all fields have about 10-20 core principles and the tech stack is just trying to make those things easier, so don't fret overit.
There's a reason why people recommend job hunting. If I'm unsatisfied at a job, it's probably time to move on.
I've made some good, lifelong friends at companies I've worked with. I don't need to make that a requirement of every place I work. I've been perfectly happy working at places where I didn't form friendships with my coworkers and I've been unhappy at places where I made some great friends.
I've learned to be honest with my manager. Not too honest, but honest enough where I can be authentic at work. What's the worse that can happen? He fire me? I'll just pick up a new job in 2 weeks.
If I'm awaken at 2am from being on-call for more than once per quarter, then something is seriously wrong and I will either fix it or quit.
pour another glass
Qualities of a good manager share a lot of qualities of a good engineer.
When I first started, I was enamored with technology and programming and computer science. I'm over it.
Good code is code that can be understood by a junior engineer. Great code can be understood by a first year CS freshman. The best code is no code at all.
The most underrated skill to learn as an engineer is how to document. Fuck, someone please teach me how to write good documentation. Seriously, if there's any recommendations, I'd seriously pay for a course (like probably a lot of money, maybe 1k for a course if it guaranteed that I could write good docs.)
Related to above, writing good proposals for changes is a great skill.
Almost every holy war out there (vim vs emacs, mac vs linux, whatever) doesn't matter... except one. See below.
The older I get, the more I appreciate dynamic languages. Fuck, I said it. Fight me.
If I ever find myself thinking I'm the smartest person in the room, it's time to leave.
I don't know why full stack webdevs are paid so poorly. No really, they should be paid like half a mil a year just base salary. Fuck they have to understand both front end AND back end AND how different browsers work AND networking AND databases AND caching AND differences between web and mobile AND omg what the fuck there's another framework out there that companies want to use? Seriously, why are webdevs paid so little.
We should hire more interns, they're awesome. Those energetic little fucks with their ideas. Even better when they can question or criticize something. I love interns.
sip
Don't meet your heroes. I paid 5k to take a course by one of my heroes. He's a brilliant man, but at the end of it I realized that he's making it up as he goes along like the rest of us.
Tech stack matters. OK I just said tech stack doesn't matter, but hear me out. If you hear Python dev vs C++ dev, you think very different things, right? That's because certain tools are really good at certain jobs. If you're not sure what you want to do, just do Java. It's a shitty programming language that's good at almost everything.
The greatest programming language ever is lisp. I should learn lisp.
For beginners, the most lucrative programming language to learn is SQL. Fuck all other languages. If you know SQL and nothing else, you can make bank. Payroll specialtist? Maybe 50k. Payroll specialist who knows SQL? 90k. Average joe with organizational skills at big corp? $40k. Average joe with organization skills AND sql? Call yourself a PM and earn $150k.
Tests are important but TDD is a damn cult.
Cushy government jobs are not what they are cracked up to be, at least for early to mid-career engineers. Sure, $120k + bennies + pension sound great, but you'll be selling your soul to work on esoteric proprietary technology. Much respect to government workers but seriously there's a reason why the median age for engineers at those places is 50+. Advice does not apply to government contractors.
Third party recruiters are leeches. However, if you find a good one, seriously develop a good relationship with them. They can help bootstrap your career. How do you know if you have a good one? If they've been a third party recruiter for more than 3 years, they're probably bad. The good ones typically become recruiters are large companies.
Options are worthless or can make you a millionaire. They're probably worthless unless the headcount of engineering is more than 100. Then maybe they are worth something within this decade.
Work from home is the tits. But lack of whiteboarding sucks.39