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!

Manager: Why haven’t you shipped any code today? It’s almost lunch.

Dev: Stuck on a bug

Manager: I’ll help you

Dev: Please don—

Manager: Have you tried thinking outside the box?

Dev: …Dear god please end my existence

Manager: You could try stack overflow too, have you ever used that site before?

Dev: 😮 🔫

Manager: Also sometimes bugs are caused by npm modules so rule that out first

Dev: *On knees praying to Zues for forgiveness and/or conveiniently placed lightning strike*

Deep learning!

I’m a fast learner too 😂

For the greater good ?

His last day...all mouse devices

weedX 😂😂

My motivation to stay awake tonight.

Sadly I don't know the source

That fortune cookie is definity meant for programmers.

Given the latest trend, i thought you guys might like this : https://twitter.com/steevedrew/...

So i saw this on fb today..
Haha

rant

my friend sends this to me on WhatsApp😣

Government on crypto currencies

Government - "You could loose all your money"
Government Again - "You could loose all your money"
Government in loop- "You could loose all your money"

News - "Government planning to ban crypto currencies"

-Market crashed

Government - "Told Ya"

Red Sox: Super secure.

Dev: Microsoft is shit

VS Code: (ಥ⌣ಥ)

Dev: Oh not you dear! You're not like the other guys

VS Code: (｡◕‿◕｡)

Strongly typed SMS

Google => googled

Duck duck go => duck duck went?

🤔

macOS treats chess like it's the System32 file in windows

try {
❤
} catch(e) {
🍺
}

Yesterday. It took me way to long to figure out why my mouse wasn't working....
Thanks, dear colleagues!

😐

😂😂😂😂😂😂

Seems appropriate.

That moment when

Just signed a contract for a new room!

This means I'll be going from 500kbs to a general 30-50mbs 😍

Everyone loves a bit of banter

I was told during my initial interview that the book "Clean Code" is their Bible here.

And it's true. It's lying, unread in drawers and shelves all over the office.

Solution to all of our Git problems

I imagine two dev colleagues sitting next to each other, on their phone, each feeling very secure in the anonymity of devrant.

As a programmer, I'm outraged.