Coleton Gorecke (@coletoncodes) profile picture

Self Taught Software Engineer. I talk about life, software engineering, productivity, and growing your own solo software business. Building. Writing. Creating.

United States
Joined April 2018
I have a graveyard folder with fifteen repos, three years, and $1,608.35 to show for it. For years I told myself the comfortable story: I have too many interests. I'm a curious person. It flattered me. It was bullshit.
1
30
I don't have too many interests. I have too many unlaunched ideas. Wrote the whole thing down. Read it here.
1
12
PrioriPlanner made $978.58 in two years. ProAct made $629.77 in nine months. Same engineer, similar app. ProAct asked for money on day one, and then I actually told people it existed.
29
I built an email signup that fired confetti across the screen when you hit submit. It saved nothing. No database, no list, not one address. I made the part that looks like it worked. I skipped the part where it works.
29
Mine has fifteen repos, three years, and $1,608.35 to show for it. A repo nobody uses and a paycheck from one company dry up the same way: the day somebody decides you aren't needed. A graveyard is not a backup plan.
192
The next decade doesn't belong to the best coders.
1
51
Everything between the idea and the working product is approaching free. The bottleneck moves upstream.
1
2
The job was never about the code. It was always about what the code unlocks. The code just got cheap. The unlocking didn't.
"Here's a rough version. Does this solve the problem?" That's the product engineer posture. The ticket-taker posture is "I'll let you know when it's done."
1
44
The first one gets feedback on day two. The second one gets feedback never, because the thing they built was wrong and nobody told them until it was too late. Ship before you're ready.
6
Stop measuring your week in tickets closed. Start measuring it in problems solved. If you shipped four features and none of them moved a metric, you didn't have a good week. If you shipped nothing but figured out why a feature wasn't landing, you did.
1
1
44
Velocity is a measure of motion, not direction.
6
Talk to a user this week. Not through a PM. Not through a survey. A real conversation. Ask them what they were trying to do the last time your product frustrated them.
1
41
You'll learn more in twenty minutes than you will in a month of grooming sessions. The PM's summary of a user conversation is not the conversation.
4
Ramp's engineering principles include "build what the customer really needs, not what they ask for" and "build opinionated systems."
1
1
42
Ramp expects engineers to understand the problem deeply enough to have an opinion. Not "implement the ticket." Not "ask the PM." Have an opinion.
1
10
The companies that win now aren't hiring better coders. They're hiring engineers who refuse to be ticket-takers.
12