A team in our company has spent a few weeks building an application where we would pick what days we are remote and where we are going to work.

Now today, manager decided that on top of regularly updating that remote schedule we’d also have to ANNOUNCE in a channel on Teams that we’re remote on that day………. Supposedly for good moods and work life, this is such a waste of time I can’t even….

I should complete that the application let’s you see if anyone in the company is remote and where they can be found 🙄

so true...

developer: *deploying spaghetti code to production*
hacker: *alters the code with an injection*
developer:

What do you think?

Very bad feeling

Reddit never fails: someone git init the constitution

surprise API

Website: "Here is your PDF! You can download 1 more PDF today. Get unlimited downloads with a PRO account!"

Oh do I?

*deletes cookies and local storage*

*downloads another one*

Website: "Here is your PDF! You can download 1 more PDF today"

yay!!! Another PROD issue on something that we've had PROD issue on and well should be an easy fix... Cuz the root cause is prolly bc the idiot that implemented the logger had no idea what the fuck they were doing... And well the whole team didn't bother to ask me (and never listen to me anyway).... WHO WOULD PROBABLY SHOW THEM HOW THEY FCKED UP...

BUT ....

¯\_(ツ)_/¯

I think the weekly rants just exist because @dfox & @trogus got banned from stackoverflow and they still have questions.

When it comes to learning cutting edge tech... Go build already!

I found Rust intimidating.

I read the first few pages of the official book, got bored, gave up.

Few months later, decided to write a "simple" tool for generating pleasing Jetbrains IDE color schemes using Rust. I half-finished it by continuously looking up stuff, then got stuck at some ungoogleable compiler error.

Few months later I needed to build a microservice for work, and against better judgement gave Rust a try in the weekend. Ended up building an unrelated library instead, uploaded my first package to crates.io.

Got some people screaming at me that my Rust code sucked. Screamed back at them. After lots of screaming, I got some helpful PRs.

Eventually ended up building many services for work in Rust after all. With those services performing well under high load and having very few bugs, coworkers got interested. Started hiring Rust engineers, and educating interested PHP/JS devs.

Now I professionally write Rust code almost full-time.

Moral of the story:

Fuck books, use them for reference. Fuck Udemy (etc), unless you just want to 2x through it while pooping.

Learning is something you do by building a project, failing, building something else, falling again, building some more, sharing what you've made, fighting about what you've built with some entitled toxic nerds, abandoning half your projects and starting twelve new ones.

Reading code is better than reading documentation.

Listening to users of your library/product teaches you more than listening to keynote speakers at conferences.

Don't worry about failures, you don't need to deliver a working product for it to be a valuable experience.

Oh, and trying to teach OTHERS is an excellent method to discover gaps in your knowledge.

Just get your fucking hands dirty!

Apple legacy recovery...

🍰

Today I navigate the devRant oceans for the 157,680,000 second.

Who knew this place would be still pumping some of the greatest devs I've come to appreciate so many years later, it's not the vibrant place it once was, but it's still full of hidden gems.

post malone
get malone
put malone
patch malone
delete malone

A big shoutout to all software vendors, who, at the top of their product homepage, simply explain to you in 2-3 non-bullshit sentences what their product actually does, and what it is used for. I fucking love you.

And a big fat middle finger to all the rest with your useless buzzword gobbledygook. Go to hell.

I just wonder If a app/website HRrant exists where time to time HR's talk about how antisocial, strange creatures they met. 😂

When the interns mess up big time, good orgs support them. 😭💙

Every single diagramming tool.

All the SaaS ones are either way too limited in function, or proprietary vendor-locked.

All the FOSS/desktop ones have a 90s UX experience.

I really want to make a great, comfortable-to-use diagramming tool which just directly uses SVG as the file format, but without the "FUCK IT DOESNT ALIGN CORRECTLY AND WHY IS THIS ARROW BEHIND THE REST" experience...

But I know deep down that it's hard work, and I'll probably get stuck delivering the gazillionth lackluster, bugged diagramming app.

I give the same answer to every Junior

I quite forgot this gem.

Adventures in security land.

The “legendary” lead dev authored a ticket that logs raw credentials for a third-party tool we’re using, and logs partially-obscured consumer passwords. His reasoning: “for debugging. And customer service!” And then argued with me over why that’s bad! Seriously?

Then in the release channel, he and the release manager are talking like I’m pestering them with my findings. Things like “I have some Root-induced changes coming” and “Fixed those, but she’ll probably have more...” etc.

Like come on.
I’m even being nice here, but you seriously need to stop screwing this up.

They also didn’t bother merging the fixes into the release branch, so I needed to re-review the entire (large) ticket on its own branch. Doubles the effort since I can’t easily see what changed.

The lead dev also only updated a few of the specs (despite me sending him a list), so there’s a bunch of failing ones now. Makes me unsure if he actually fixed everything.

Maybe I’m just being touchy, but ugh. Freaking annoying people.

At least he owned up to being the author this time instead of saying someone else (who wasn’t in the history...) wrote it. -.-

The answer they deserve

* googles how to handle fame *

Similar with pluses on devRant

@ most of yall

Little me sees Monitor.
Monitor depicts Things.
Box make beep boop.

"Cool! But why?"

That's basically it.

my laptop as soon as I start building my app locally

So I moved from being the TL of a small team to a member of another team a month ago.

A dev from the old team sent me this today morning. He also sent some examples of what he found "cool", and tbh I'm pretty proud of those modules. I tried being very modest there, but I'm very happy 😅

Client: THIS IS CRITICAL, SOME DATA HAS BEEN DELETED, WHAT ZE FUUK HAPPENED, UNDO THIS FAST
Us: so after carefully reviewing the code, related resources and the network traffic we conclude that was never sent in the first place.
*closes issue*

I'm glad we got such a meaningful bug report on the same day a production system started failing, one big deployment that that was like a boss with 3 phases, an unnecessary long meeting and an app developer that that wanted me to break HTTP standards.

So true!

Talk about scaremongering. This is the best thing to happen in the academic community in eons.

https://bbc.co.uk/news/...