Dan Goslen

A code review is not a performance review

Locale access forced us to rethink our auth model. Locale isn’t just another resource. It qualifies access to every other resource. That led to a few shifts: - Treat it as a dimension - Compute context, don’t persist it - Compose checks in one policy call wfl.io/3QmtHOQ

@TimStodz send

My companies make over $2 million per year combined. Copywriting is a huge part of their success. I recently recorded a 45-minute copywriting masterclass. Now I’m gonna give it to you for free. Like, retweet, and reply "send", and I'll DM it to you. (Must be following)

@Gehan_Mendis Thanks for sharing!

Four Tips When Joining a New Team by @dangoslen link.medium.com/AoQx8Tb5nxb

@burgessdryan Two things I've seen - Make it easy to change (like good code) - Celebrate when they add or update it (just like a first deploy to production)

How do you incentivize better documentation in your team?

@codewithvoid Code reviews Not using ORMs

programmers, name one topic you can talk hours about...

@nat_snacks C?

What coding language is this? █ █ █ 　　 █　 █　 █　 █ effectiveness enjoyability

@dinkydani21 Just finished @tommycaldwell1's "The Push" and really enjoyed it!

In desperate need of books to read! 📚 What's on your list this year? ✨ Non-fiction is great but pls no startup/business books (wanna escape to relax) 🙏

@kelseyhightower Or at least, the questions everyone else thinks aren't worth asking

@burgessdryan 3

I’m working on a house project today. How many times will I have to go to Home Depot?

@curtiseinsmann We had an architect join our team a few years ago that did this well. During the first few weeks, he read and re-read every doc. ever put together on our system. When he finished, he understood our system better than we did. He earned our trust and respect almost instantly.

You can tell a lot about how good a software engineer is when you see them join a new team. The good ones won't immediately criticize the tech stack and start suggesting improvements. They'll seek to understand the product's technical fitness, and *why* it came to be that way.

@kelseyhightower golang. It isn't verbose, has good conventions and style guides, is strongly typed, and has a lot of power as you get more and more comfortable with it.

Enjoying the day off today. Reflecting on the year, proofreading some chapters for my book on code reviews, climbing, and trying to slow down for the holiday break. I hope you can find time to slow down in the next week too. See you in 2023! Excited about what's in store. 🎉

4⃣ Build for an audience Don't build for just your own team. Hold a daily demo and invite other teams to see what you're building. The "pressure" to show something "cool" will be a good litmus test for what to build. And it might spark other ideas for other teams.

3⃣ Prefer fast feedback Find some way to start an action and show output easily. Even if you don't need an API, build a simple (and even broken) API just to show "something happened". Logs can even be useful if done correctly

Spent this past week building a proof-of-concept application around a rules engine. And we had a blast! So much fun coding and experimenting. If you are wanting to build a PoC app anytime soon, here are my top takeaways from building one. 🧵

@trashh_dev in which direction?

did you know: the number of stickers on a laptop correlate with programming abilities.

@bdougieYO 2

How many people in a 2 pizza team?