Knowing how to do something and doing that something are very different things

I wonder what would have happened if Jaco and tony rice played together

With all this AI tooling out there now, I feel like the resume is dead…if it wasn’t already. What takes its place?

Interviews are the plinko machine of human interactions

A key part of leadership to me is knowing what details matter and which do not

Trying to include “and” instead of “but” everywhere I can. Surprisingly happens more than I expected. Changes the audience demeanor in a meaningful way.

The best way to improve at programming is to pair with someone better than you.

The minimum viable product is the one customers will buy. It ain't viable otherwise.

What’s the AI landscape for sql? Should I be advising new devs to deeply learn this skill or is this something that AI is doing easily these days? #ai #SQL #CareerDevelopment

I spent 3 hours today to get a slider carousel to work in a NextJS app. Granted my experience in this ecosystem is low, but the layers of abstraction between NextJS, TypeScript, and React is a lot to traverse.

I got mine in 2015. I still wear it to this day. And I still miss @WagonHQ every day

The high % of the YC W24 batch that uses @posthog and @porterdotrun is a powerful indicator that these two companies are onto something big.

Does anyone use #ractors in #ruby? Curious of your experience

There are so many cool figma plugins that make ui ux so much easier!

I find myself doing NextJs dev and trying to get pixel perfect. I still find the @FirefoxDevTools the most useful when working with css and html. Something just smoother and clearer about it to me.

I’ve retired from software… process. No scrum, dds, tdd, stand ups, devops, sre, micro services, retrospectives, pre and post mortems… Instead, we just build and run software together. We do use an issue tracker and a good readme. Everyone posts an eod update to our group with demo/insights from their day. Plain and simple. It’s pure bliss.

Wrote a little something. In admiration of some of the best programmers I've ever worked with:

Has anyone written something great about how to model your Rails-based SaaS app with Users, Teams, Organizations, and Subscriptions so that you don't regret it later?

Is this true?

SQL doesn't have to be scary or unreadable. Using CTEs and properly formatting your SQL can go a really long ways. Lets start with CTEs. They're like a temporary view that you can build and refer to later, here's an example: with late_invoices as ( SELECT id, account_id, amount, created_at FROM invoices WHERE created_at >= now() - '1 month'::interval AND status='unpaid' ) Then you can query it simply with: SELECT * FROM late_invoices Or, we could join against the account table to get the users email to contact. SELECT * FROM late_invoices, users WHERE late_invoices.account_id = account.id; How else do you make SQL readable? Well consistent formatting goes a long way, don't put too much on a single line. Personally for formatting I'm in camp CAPITALIZE SQL keywords, lowercase all else. Indentation matters to. I make sure to align my columns I'm selecting from, tables I'm querying from, and then for my WHERE clause when I have ANDs I make sure to align it so the condition all aligns (two spaces before your AND. It's hard to see on twitter, but copy and paste the CTE and it'll make a bit more sense.