jakefolio's profile picture. Full Snack Developer, CrossFitter, Organizer of @lonestarphp. Engineering Manager at @GoDaddy

Jake Smith

@jakefolio

Full Snack Developer, CrossFitter, Organizer of @lonestarphp. Engineering Manager at @GoDaddy

Jake Smith reposted

Sharing this A+ analysis on the Luka trade by the always insightful @chris_kratovil Makes a ton of sense to me from the #txlege angle - esp considering Lite Patrick likely done next Session. Good stuff. Read it 👇🏼 #txlege #MFFL

LoewyLawFirm's tweet image. Sharing this A+ analysis on the Luka trade by the always insightful @chris_kratovil 

Makes a ton of sense to me from the #txlege angle - esp considering Lite Patrick likely done next Session. 

Good stuff. Read it 👇🏼 

#txlege 
#MFFL
LoewyLawFirm's tweet image. Sharing this A+ analysis on the Luka trade by the always insightful @chris_kratovil 

Makes a ton of sense to me from the #txlege angle - esp considering Lite Patrick likely done next Session. 

Good stuff. Read it 👇🏼 

#txlege 
#MFFL
LoewyLawFirm's tweet image. Sharing this A+ analysis on the Luka trade by the always insightful @chris_kratovil 

Makes a ton of sense to me from the #txlege angle - esp considering Lite Patrick likely done next Session. 

Good stuff. Read it 👇🏼 

#txlege 
#MFFL
LoewyLawFirm's tweet image. Sharing this A+ analysis on the Luka trade by the always insightful @chris_kratovil 

Makes a ton of sense to me from the #txlege angle - esp considering Lite Patrick likely done next Session. 

Good stuff. Read it 👇🏼 

#txlege 
#MFFL

Any tailwinders writing plugins with options in v4? Is it possible to add the options now that the plugin is imported via postcss in the stylesheet? github.com/tailwindlabs/t…


Jake Smith reposted

The Epic Programming Principles: the guide I use to make decisions as a software engineer. Transcending specific tools or frameworks, these principles will help you guide your career, craft, and technical choices. Check the site for a deep dive/examples on each!

kentcdodds's tweet image. The Epic Programming Principles: the guide I use to make decisions as a software engineer.

Transcending specific tools or frameworks, these principles will help you guide your career, craft, and technical choices.

Check the site for a deep dive/examples on each!

Wow @aarondfrancis talk far exceeded my expectations. So vulnerable. So authentic. Y’all need to check out the video when it’s shared out. #CommitYourCode


Great message from @DThompsonDev to kickoff #CommitYourCode, get out there…find a meetup…start a conversation…just get involved! Also hearing him describe the logistics of a conference reminds me of all the joy and pain from @lonestarphp


Jake Smith reposted

Fun fact: you can reduce the memory usage of a Golang program by rearranging your structs. For example, this struct takes up 24 bytes of memory: type Example struct { A int8 B int64 C int8 } This struct, with optimized members takes up 16 bytes: type Example struct { B int64 A…


Jake Smith reposted

ESM really feels like the Python 3 of JavaScript.


Jake Smith reposted

While Texas schools struggle with a huge budget deficits, @SpectrumNews1TX has discovered that millions of Texas education tax dollars are being diverted out of state to the series of charter schools founded by #HISD’s state appointed Supt. Mike Miles.


Jake Smith reposted

When you tolerate an error, you rob yourself of learning. When you ruminate on an error, you rob yourself of happiness. Notice it, improve it, and move on from it.


Jake Smith reposted

I am so happy this is being implemented. If every tab being named `page` in Next.js/Sveltekit folder based routing makes you go loopy, this new VS Code feature is going to be a life saver!


Jake Smith reposted

Use Zod to parse your environment variables once, then use that inference to type process.env throughout your app. Also, a beautiful example of how you can extend an interface from a VALUE, not a type.

mattpocockuk's tweet image. Use Zod to parse your environment variables once, then use that inference to type process.env throughout your app.

Also, a beautiful example of how you can extend an interface from a VALUE, not a type.

Jake Smith reposted

whenever you consider using a modal refer to this site ↓ modalzmodalzmodalz.com


Jake Smith reposted

auto-growing <textarea> without JavaScript! CSS is getting field-sizing: content; to size inputs by their contents. Dropped in Chrome Canary today, demo here:


Jake Smith reposted

What you should say when someone has the idea to rewrite the code/project from scratch (Loki S2E4) youtu.be/e4y6C1urzBc?fe…


Jake Smith reposted

Another great #serverless article by ⁦@theburningmonk⁩. Managed NAT Gateway costs have been a running joke for years, but it’s time for ⁦@awscloud⁩ to stop punishing #ServerlessSecOps & those needing access to VPC resources. #awswishlist theburningmonk.com/2023/09/static…


Jake Smith reposted

🆕📝 Type safe #CSS design systems with @property ✅ not just types during dev ✅ graceful error handling ✅ interwoven type safe variable systems Soon will land in Firefox, making this type of setup cross browser viable 🎉 👀👇 nerdy.dev/cant-break-thi…

argyleink's tweet image. 🆕📝

Type safe #CSS design systems with @property 

✅ not just types during dev
✅ graceful error handling
✅ interwoven type safe variable systems

Soon will land in Firefox, making this type of setup cross browser viable 🎉

👀👇
nerdy.dev/cant-break-thi…

Jake Smith reposted

News is out, I'm speaking at Clarity Conf this year! clarityconf.com/event/2023 This is an in-person event, so pack your bags and meet us in SF this November to get deep into design systems thinking. #clarityconf

clarityconf.com

2023 · Events · Clarity

The event page for Clarity 2023 San Francisco, California.


Jake Smith reposted

Kubernetes Failure Stories Collection k8s.af


Jake Smith reposted

Feedback loops. Feedback loops. Feedback loops. I cannot stress this enough. Want to go faster? Want to be more nimble? Want to be more reliable? Focus on tightening feedback loops.

This is a lovely thread on how "speed is safety" remains unintuitive because our mental models for software are stuck on the wrong physical metaphors. Writing code is less like building a car and more like guiding or instructing the vehicle; feedback loops are everything.



Loading...

Something went wrong.


Something went wrong.