raiderrobert

raiderrobert, 11 days ago to random

Discovering that you're wrong & then changing is an underrated superpower. 💪

raiderrobert, 8 days ago to random

How do you pronounce epoch?

raiderrobert, 8 days ago to random

The best software engineers write and have a process to write well. 🧵

Here are 5 common phases of writing:

• plan
• draft
• revise
• edit
• proofread

raiderrobert, 9 days ago to random

Code as if the person maintaining your code is a very dear friend.

heidilifeldman, 9 days ago to SantaFe

Voted in #SantaFe #NewMexico today, a place where the Democratic primary determines some of the ultimate races. One race really struck me as emblematic of the future, assuming constitutional democracy survives in the U.S. 1/

raiderrobert, 11 days ago to random

How do you pronounce sudo?

nixCraft, 13 days ago to random

what is a PR? give wrong answers only.

raiderrobert, 9 days ago to random

How do you pronounce etc (the directory)?

raiderrobert, 13 days ago to random

People without dirty hands are wrong.

Doing something makes you right.

FluentInFinance, 14 days ago to random

My credit score went down when I paid off my car.

My credit score went down when I paid off my student loans.

The system punishes you for not owing money.

They want you to be in debt constantly.

Credit reporting agencies told me: "You should get more loans to increase your credit score."

Credit scoring is one of the biggest scams.

raiderrobert, 14 days ago to random

I was fired from my first dev job.

It was 2011. I was trying to get a proper job after doing a couple of start ups with friends.

After 1 interview with the CEO, I got the job.

I was elated.

It was only part time, 20 hours per week. A lots of people were on vacation in my first couple of weeks, so it was slow to start, but I knew I'd get going there eventually.

45 days in, it was time for my check-in with the CEO. (1/3)

raiderrobert, 16 days ago to random

We think of software engineering ability wrong. We treat it like knowledge when it's more of a skill.

Sure. There are algorithms and data structures and code patterns and architecture and thousand more nouns. And yes, you can "know" them.

And yes, there's a use in knowing them. It's not trivia.

But it's not the demonstration of skill to know them.

raiderrobert, 17 days ago to random

"Master leetcode hard questions. Get the job. Change the color of buttons."

The most popular approach continues to be the data structure and algorithm (DSA) live coding exercise.

They're very hard to remain good at, and so historically, it was argued if you know them, you're very good at coding. But they mostly give noise, rather than signal.

I have some ideas of what could be done instead, and I advocate for that approach when I'm hiring.

What do you think is the best way to get away from t

raiderrobert, 18 days ago to random

It's important to remember some basic math realities as an engineering manager:

• avgs are pathological liars
• the "average of average" isn't a thing
• low population size is common, and makes your statistics not significant
• inconsistent rates (requests/min, etc) don't imply anything is wrong; see low population size

raiderrobert, 18 days ago to random

Numbers don't lie, but they often fail to tell the truth.

The average and stddev however are pathological liars.

raiderrobert, 20 days ago to random

The Real Engineering Career Ladder

Jr - how do I even code?
Mid - I can code!!!!! Code EVERYWHERE!!!
Sr - how do I solve the same problem with less code?
Staff - delete like 90% of this code
Principal - I miss coding

raiderrobert, 20 days ago to random

For minimal amount of "I know how to code", I propose the following:

• value types: integer, string, booleans
• variables/constants
• control flow: if/else
• loops: for/while
• structure: maps/arrays
• functions: basic declaration

raiderrobert, 20 days ago to random

Go where there be dragons.