#Learning
23 notas · última:
How I use LLMs as a staff engineer
The author uses LLMs as smart autocomplete, a tutor for new domains, a fallback for bugs, and a proofreading tool, while avoiding them for full drafts and familiar production work.
How to Help Someone with Their Code Using the Socratic Method
The article argues that giving direct answers blocks learning, while Socratic questioning helps learners reach conclusions themselves and strengthens debugging, assumptions-checking, and long-term reasoning.
Learning in the Forest
The post argues that teams should optimize for learning over immediate production, because tasks, pairing, demos, and pacing can build skill, energy, and future throughput while juniors learn.
Stuck in a Rut as a Programmer? It’s Not Your Fault.
The page argues that programmers often feel stuck because their work becomes repetitive and their language or stack was not really chosen by them. To break the rut, it recommends learning, writing, researching, pet projects, sharing, and reading.
The Secret Life of a Microsoft MVP
The post describes MVP life as ongoing community work: learning fast, sharing practical experience, balancing a day job, and handling criticism while helping others and staying current.
Writing Toy Software Is A Joy
Argues for building toy programs (regex engines, OS kernels, chess AIs) as the fastest route to real understanding, and against outsourcing that struggle to an LLM.
You Don't Have to Read Every Page
Management books work better as references than narratives — put them down, come back when a new challenge makes a specific chapter suddenly relevant.
Bloom's Taxonomy for Developer Mastery
00:07:14 — Bloom's Taxonomy Applied to Developer Knowledge
How I Learn Technical Things Fast
The page lists eight habits the author says help him learn faster: prepare fundamentals, focus on one task, study in immersive settings, work on weaknesses, use active recall, seek feedback, think from first principles, and teach.
Unlocking high software engineering pace: Build less, ship frequently, learn faster – Jim Grey on software management
The article argues that teams should ship the smallest useful version early, get real-user feedback, and learn faster instead of spending many sprints building a full feature before anyone can use it.
The Best Programmers I Know
Matthias Endler argues that strong programmers read references, understand tools deeply, read errors carefully, break down hard problems, keep learning, and stay humble, patient, and simple in their work.
How to Understand Complex Coding Concepts Using the Feynman Technique
The article explains the Feynman Technique as a way to understand coding concepts by simplifying them, checking gaps in your explanation, and revising until you can teach them clearly.
Pragmatic Thinking and Learning: Three takeaways
The post says this book links learning and programming, explains skill stages, contrasts focus and diffuse thinking, and suggests practical habits like writing ideas down, taking walks, and learning by doing.
Learning is optimized when we fail 15% of the time
Research from the University of Arizona argues that learning is maximized when failure happens about 15% of the time, with performance around 85% accuracy in simple two-choice tasks.
If you’re not spending 5 hours per week learning, you’re being irresponsible
The article argues that knowledge is becoming more valuable as goods and services are demonetized, so people need regular deliberate learning to stay competitive. It outlines six skills and urges a weekly learning ritual.
Is It OK For New Programmers To Blog About What They Are Learning?
The video answers a beginner programmer’s question about blogging while still learning and treats it as a valid way to share progress and advice from experience.
Takes Notes on Everything
The author argues that taking notes on what he reads helps him separate signal from noise, distill what matters, remember technical material, and build a useful public record for others.
How I became (and stayed) a successful programmer
The author says longevity in programming comes from learning from better programmers, leaving the comfort zone from time to time, and solving problems independently before asking for help.
ShuHaRi
Shu-Ha-Ri describes learning a technique in three stages: precise imitation of one master, learning principles from other sources, and then adapting practice through one’s own experience.
How to Better Retain Information from Books, Articles, and More
The piece argues that people forget most of what they read or hear, so retention depends on a system: take notes, review them regularly, and use objects or mementos to trigger recall.
5 Ideas to Create an Amazing 2015
Leo Babauta argues that an amazing 2015 comes from building habits one at a time, committing fully, reviewing weekly, relying on accountability, and treating setbacks as learning.
Don’t Overwhelm Yourself Trying to Learn Too Much
The post argues that software developers should avoid trying to master too many technologies at once, and instead rely on just-in-time learning, a solid base, and one or two areas of focus.
4 Things I Wish I Would Have Known When I Started My Software Development Career
The author says his career improved only after he stopped chasing one right way, learned by building, focused on broader skills, joined community, and made side projects a priority.