Details
-
AboutGeneralist.
Joined devRant on 11/4/2020
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
-
I've experienced it many times before but it's a really refreshing experience every time it happens. Motivation. It comes in many forms and means a lot of different things directly but an unchanging attribute of it is that it makes things way too easy and your work becomes enjoyable once it comes into the picture. Even dive into a dumpster of legacy spaghetti and dishing out nasty code review feedbacks feels GREAT when you're motivated. Context: I've spent like several months low on motivation, and it was one of the least productive times I've ever had, and now I just feel nice, y'know, able to actually do stuff and do it right.
Anyway. Rays of motivation to you, reader. Balance your workload so that you don't lose it like I did a while ago, and stay safe out there. It matters.1 -
Unguided code style decisions and the whole personal style things sometimes display an intention behind a piece of code. They can hint on semantics and relations between the pieces of data or operations, like it's often the case with grouping that doesn't separate bunch of statements with a blank line. Sometimes, they can even carry an emotional message. Love, hate, grudges, deepest affection for some golden hammer feature of the language, everything is on the table actually. For instance, this is what fear looks like:
3==o -
To be honest, the majority of my work is just man and grep, and these two things already somehow make me better than the vast majority of my colleagues. Impostor syndrome doesn't think so though.7
-
I hate that trend of making things more lax in terms of implementation quality while writing it off with a simple but stupid "oh computers are faster now, users have the RAM, yadda yadda". Yeah but back in a day things were actually running pretty damn fast in comparison while doing it on hardware that is totally potato in comparison to what's used now. This trend eats away ANY gains we get in terms of performance with upgrades. It deprecated the whole notion of netbooks (and I kinda liked them for casual stuff), since now every goddamn one-page blog costs you from several megabytes and up to tens of megabytes of JS alone and lots of unnecessary computations. Like dude, you've brought in a whole Angular to render some text and three buttons, and now your crappy blog is chewing on 500 MB of my RAM for whatever reason.
Also, Electron apps. Hate them. Whoever invented the concept, deserves their own warm spot in Hell. You're doing the same you would've done more efficiently in Qt or whatever there is. Qt actually takes care of a lot of stuff for you, so it doesn't look like you'll be slowed down by choosing it over Electron. Like yeah, web version will share some code with your desktop solution but you're the whole reason I'm considering your competitor's lack of Electron a huge advantage over you even if they lack in features.
Same can be said pretty much about everything that tries to be more than it should, really. IDEs, for example, are cancerous. You can do 90%+ of what you intended to do in IDE using plain Vim with *zero* plugins, and it will also result in less strain on your hands.
People have just unlearned the concept of conscious consumption, it seems.28 -
I'm frustrated with an abundance of different *Ops we're having right now. You can spell a random word followed by "Ops", and it's probably a thing. I get that Ops people in general are important but when there is stuff like GitOps, MLOps, FinOps, it gets confusing pretty damn fast. There's no value in all these titles besides "duh" usually, since Ops are just Ops in most situations. They kinda can slap a tracing tool or two on top of your code base but in general they just do Kubernetes (with whatever's hip like Jaeger, etc.) nowadays and that's it. Hell, even "DevOps Engineers", for a majority of cases you'll encounter, are basically just Ops with a misleading prefix since it's just a way people call them nowadays for whatever reason.3