Details
-
AboutJunior backend/devops developer
-
Skillsgolang, docker, typescript
-
LocationAt Rutee's
Joined devRant on 3/4/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
-
Why the fuck does teams' meeting overlay automatically focus on the mute or webcam button, NOW I CAN ACCIDENTALLY TURN THEM ON
Time to dig into the settings2 -
!rant
Just deleted 6 files and simplified a process significantly, omg it feels so good to throw stuff out
My product owner was once under the impression that writing more code was something I enjoyed doing, but it couldn't be farther from the truth.
Writing new solutions and patterns is fun, adding anything other than that is just more future maintenance work1 -
What is it with people just blindly fucking copy pasting from a different project, seeing it work and then submitting it for review.
You copy 2 lines, one of which fixes the thing, WHY KEEP THE OTHER USELESS IRRELEVANT PIECE OF FUCKING SHIT IN THE FUCKING CODE WHY BOTHER WITH KEEPING IT IN IT'S MORE TECH DEBT BECAUSE NOBODY WILL KNOW WHY IT'S THERE
WHY DO I CONTINOUSLY HAVE TO POINT THIS OUT IT'S SO FICKONG TIRING TO CONSTANTLY HAVE TO BE THE ANNOYING REVIEWER WITH +20 COMMENTS ON SMALL PRS IM SO FUCKING TIRED OF BEING 'THAT GUY'
In my language it's called being 'slordig'. Whenever I submit sometning for review I always go over the diff to see is I missed anything that is no longer required and remove it WHY DONT THEY DO THAT TOO
And then their PR stays open for 2 weeks like they forgot about it and during standup they say 'its in review' like I havent already looked at your piece of shit code
FUCK2 -
Around a decade ago, I was fiddling with ajax in jQuery. This piece of code had me stumped for around 2 days, why? Because success is written with 1 final S in my native language...
$.ajax({
'succes' : function(data) { },
});7 -
Me: * About to send e-mail *
Me: Does this look good? Shall I send it?
Colleagues: Yup, looks good
Me: * Sends e-mail *
Colleagues: Perhaps say something about X and mention Y at the end
-.-3 -
* Sigh * Found this in an open source project, time to make a PR that'll never get looked at. \
(first and last lines)8 -
I'm so tired of finding great repos and then discovering that they're just abandoned. 0 response to PRs or issues.
How long is appropiate to wait for an author to respond before you can consider your own version to be the 'new fork'?7 -
Me: Writes down 'npm install '
Me: Copies the install command and pastes it
Me: Run 'npm install npm install package'
Every fucking time2 -
!rant
I've been working with Golang for a while now and I've come to love the generics they introduced. Making stuff type-safe is a bit of a hassle, but it pays off greatly.
One thing I had yet to consider though, is that functions are also a type, so that those could be made generic too.
func DoThing[F func(string) | func(int)](callback F) {...}
Now you can deliver both function types and I can differentiate them using a type switch.
Weird that sometimes my brain doesn't make that connection immediately...1 -
Anyone else does this?
I can't for the life of me maintain focus during long boring meetings about new designs etc. For 2 years now I've gone by doing all kinds of stuff during meetings and only ocassionaly join in when I totally disagree with something.
Often I only need to chime in at the end anyway, either meeting notes get shared or I ask someone what was discussed the previous day.
Makes me realize how much time gets wasted7 -
I'll be giving a workshop in a few weeks to my colleagues and I'm in need of browser-based workshop software. Given the nature of our own work stations, I want it to be browser-based to prevent any issues from arising.
The program is written in golang and we use some azdo-based libraries. Self-hosting preferred, I need to connect some dependent programs.
Do you guys know any good ones? -
Why do people continue to ask me why I'm not just sending any - ANY - error/exception message in full length to the user.
Am I going nuts? You can't tell me that this is a good idea right?13 -
Me: Hey I haven't used these repos/tokens/files in a while, let's remove them to clear up some space
Day later, a colleague: Hey Alex, could you update this repo/token/file?
EVERY FUCKING TIME1 -
One of our internal apis returns an array in which the first element is metadata about the request.
Why would anyone want to punish their users like that6 -
How many times do I need to tell you, markdown does not convert a single linebreak to a new paragraph.
STOP WRITING LINES THAT ARE MORE THAN 300 CHARACTERS LONG IN A MARKDOWN FILE HOW THE FUCK AM I SUPPOSED TO REVIEW THAT.9 -
Stackoverflow, gorm.io and reddit all went down while we were researching documentation. Thanks Cloudfare1
-
Have private dependencies anywhere and the `getting started` becomes 2/3 steps longer, and gives twice the headaches9
-
I'm getting more and more triggered by my colleagues overusing words in seemingly random fashion.
The word 'perspective' comes up at least 6 times during a meeting, from an x perspective, from a y perspective. It would be fine in a design meeting but it's used _so fucking much_ I cringe every time I hear it.
Another one is 'standard', that gets put in front of every word nowadays, standard process, standard protocol, standard machine, standard pipeline. What does it mean? No clue, what does it add? Nothing.
'Please put this add the standard location.'
Where?
'The default one'
What?!
I remove it from documentation every chance I get.
Furthermore, some documentation changes make small pieces of information super long. A nice summary list of features? Make it at least 3 sentences for every bullet point. 1-sentence info with a reference link to more info? Scratch that let's include all information in that reference paragraph anyway. Sometimes they even expand English expressions for no reason, making them longer and harder to read.
WHYYYY
We always complain about shit documentation and yet we're oblivious to the fact that our own docs are so bloated. Stop repeating information, stop using useless adjectives, just put it all in 1 sentence and add dozens of code examples. One piece of code says more than a billion words.
I'm not innocent either. As a teen I was great at writing long pieces of text that seemed like a great read but were actually way too bloated for the information I needed to convey. It was great for reaching word limits.
Now I'm trying my absolute best to be as concise and to-the-point as possible because I know that nobody likes reading and people just want the information that they're looking for.
Even this rant is overly long, but thank god that it's just a rant and I can let off some steam.
Btw same thing goes for diagrams, too many icons, too much text, too many lines. When I try to submit a clean-as-fuck diagram I get asked to add more info/features to which I say No, we're already at the max.
I even got a PR for review that made some changes to add unnecessary information, I pointed it out and never heard anything from them again. I rejected the PR, and never saw a new one.
* Sigh *
It's just so strange to me, it's never clear to me why these things happen. I'm too much of a coward to point these things out unless they endanger the quality of the product. But maybe they just need somebody to tell it to them.6 -
When a non-descriptive error occurs while uploading to a system and all you can do is incrementally remove your changes to deduce where the error started popping up
-
So I'm gonna send the e-mail with these 4 questions, is that OK or am I missing anything?
"Go ahead"
* Clicks send *
"Could you also ask..."
NO! DON'T SAY THAT'S IT'S OK TO SEND IF YOU STILL WANT TO ADD STUFF TO IT!1 -
Using a library that is a wrapper around an API, seems to work fine and I can connect to the api with my credentials.
Cue me, a responsible dev, wanting to use Dependency Inversion using the library's interfaces so that I can mock them easily in tests.
var test lib.IObjectManager = lib.ObjectManager{}
Error: Return type of method 'GetA' is A and should be 'B' according to the interface!
Error: Return type of method 'GetE' is *E and should be 'E' according to the interface!
Clearly nobody ever tried to use that interface :/ -
My dumbass removes a setter and then starts wondering why the API isn't accepting any query parameters anymore1
-
One of our juniors was adding a feature and made a small mistake in one of their (copy-pasted) unit tests by forgetting to cast a return value of a mock
So he spent a ton of time changing the main code to do type checks, try/catching and error handling.
Poor soul realized the mistake in code review one day later2 -
I've never rejected a pull request, I just out in loads of comments with constructive criticism.
When shoukd you reject and when should you just sdd in comments?7 -
We have a role/team/user system where we can add people to teams so they can see our code.
Every time I have to add people to something, 20-something emails arrive to inform the new users' managers and let the user know that a request has been made.
Never do I feel as anxious as when all these emails go out and everybody sees my name and I immediately feel like I fucked up -
I'm a strong believer in the triple-A unit-test pattern: Arrange, Act and Assert
Anyone else that uses this for their tests? Do you see any cons to using this approach to writing tests? Are you using an alternative?11