tl;dr:“I've learned that when I break down my large tasks in chunks that result in seeing tangible forward progress, I tend to finish my work and retain my excitement throughout the project. People are all motivated and driven in different ways, so this may not work for you, but as a broad generalization I've not found an engineer who doesn't get excited by a good demo. And the goal is to always give yourself a good demo.”
tl;dr:“In this blog post, I will make the argument that prompt engineering is a real skill that can be developed based on real experimental methodologies. I will use a realistic example to walk through the process of prompt engineering a solution to a problem that provides practical value to an application.”
tl;dr:5 step process outlining how Mitchell approaches a complex project: (1) Become a user of the project. (2) Learn how to build it. (3) Learn the hot-path internals using “trace down, learn up.” Trace down starts with a feature and trace the codepath that the feature follows. Learn up is about understanding how the various mapped subsystems work. (4) Read and reimplement recent commits. (5) Make a bite-sized change.
tl;dr:"Discussion with Mitchell Hashimoto, co-founder of HashiCorp, who recently returned to the role of independent contributor after stints as both CEO and CTO. We talk about his journey learning to write software, how he came up with the idea for Terraform, and why he prefers slinging code to executive roles."