Hackernews posts about sean goedecke

1. Practical AI techniques for daily engineering work – sean goedecke (www.seangoedecke.com)
   2 points by rbanffy 24 days ago | discuss
2. Practical AI techniques for daily engineering work – sean goedecke (www.seangoedecke.com)
   1 points by rbanffy 26 days ago | discuss
3. Why DeepSeek is cheap at scale but expensive to run locally (www.seangoedecke.com)
   328 points by ingve 17 days ago | 228 comments
4. Diffusion models explained simply (www.seangoedecke.com)
   168 points by onnnon 30 days ago | 36 comments
5. The first big AI disaster is yet to happen (www.seangoedecke.com)
   111 points by rbanffy 6 days ago | 134 comments
6. In defense of shallow technical knowledge (www.seangoedecke.com)
   108 points by swah 24 days ago | 78 comments
7. Strengths and limitations of diffusion language models (www.seangoedecke.com)
   72 points by rbanffy 27 days ago | 7 comments
8. The Illusion of “The Illusion of Thinking” (www.seangoedecke.com)
   57 points by jonbaer 9 days ago | 51 comments
9. The Illusion of "The Illusion of Thinking" (www.seangoedecke.com)
   6 points by gfysfm 10 days ago | 1 comments
10. In defense of shallow technical knowledge (www.seangoedecke.com)
    6 points by ingve 23 days ago | discuss
11. The first big AI disaster is yet to happen (www.seangoedecke.com)
    5 points by swah 8 days ago | 5 comments
12. Say "But Yes", Not "Yes But" (www.seangoedecke.com)
    4 points by olibaw 5 days ago | 1 comments
13. It's Not Your Codebase (www.seangoedecke.com)
    3 points by ingve 19 days ago | 1 comments
14. AI interpretability is further along than I thought (www.seangoedecke.com)
    3 points by emschwartz 11 days ago | discuss
15. Practical AI techniques for daily engineering work (www.seangoedecke.com)
    3 points by swah 28 days ago | discuss
16. How to work in tech when your job isn't safe (www.seangoedecke.com)
    3 points by mooreds 29 days ago | discuss
17. Arguing point-by-point considered harmful (www.seangoedecke.com)
    2 points by alexharri 11 days ago | discuss
18. John Henry and the large language model (www.seangoedecke.com)
    1 points by ingve 15 days ago | discuss
19. What did DeepSeek figure out about reasoning with DeepSeek-R1? – sean goedecke (www.seangoedecke.com)
    4 points by rbanffy 5 months ago | discuss
20. Engineers who won't commit force bad decisions – sean goedecke (www.seangoedecke.com)
    3 points by rbanffy 4 months ago | 2 comments
21. Protecting your time from predators in large tech companies – sean goedecke (www.seangoedecke.com)
    3 points by rbanffy 5 months ago | discuss
22. Crushing Jira tickets is a party trick, not a path to impact – sean goedecke (www.seangoedecke.com)
    2 points by rbanffy 5 months ago | discuss
23. How I ship projects at big tech companies (www.seangoedecke.com)
    1425 points by gfysfm 7 months ago | 381 comments
24. Mistakes engineers make in large established codebases (www.seangoedecke.com)
    811 points by BerislavLopac 5 months ago | 368 comments
25. Knowing where your engineer salary comes from (www.seangoedecke.com)
    335 points by mooreds 2 months ago | 178 comments
26. Getting things “done” in large tech companies (www.seangoedecke.com)
    315 points by swah about 1 month ago | 218 comments
27. How I use LLMs as a staff engineer (www.seangoedecke.com)
    248 points by gfysfm 4 months ago | 195 comments
28. Grifters, believers, grinders, and coasters (www.seangoedecke.com)
    232 points by rbanffy 7 months ago | 118 comments
29. The good times in tech are over (www.seangoedecke.com)
    185 points by swah 3 months ago | 252 comments
30. What it's like working for American companies as an Australian (www.seangoedecke.com)
    138 points by gfysfm 5 months ago | 173 comments
31. Ratchet effects determine engineer reputation at large companies (www.seangoedecke.com)
    115 points by rbanffy 5 months ago | 41 comments
32. Great software design looks underwhelming (www.seangoedecke.com)
    102 points by pierremenard 3 months ago | 15 comments
33. Good engineers are right, a lot (www.seangoedecke.com)
    97 points by rbanffy 4 months ago | 63 comments
34. How I got promoted to staff engineer twice (www.seangoedecke.com)
    92 points by brunocvcunha 6 months ago | 83 comments
35. Crushing Jira tickets is a party trick, not a path to impact (www.seangoedecke.com)
    89 points by scarface_74 5 months ago | 81 comments
36. Using squeezed wav2vec2 to automatically detect owl calls (www.seangoedecke.com)
    77 points by gfysfm about 1 year ago | 8 comments
37. Patience too cheap to meter (www.seangoedecke.com)
    76 points by swah about 1 month ago | 25 comments
38. What can strong engineers do that weak engineers can't? (www.seangoedecke.com)
    74 points by gfysfm 6 months ago | 81 comments
39. Glue Work Considered Harmful (www.seangoedecke.com)
    64 points by polyphilz 6 months ago | 48 comments
40. To avoid being replaced by LLMs, do what they can't (www.seangoedecke.com)
    57 points by gfysfm 4 months ago | 79 comments
41. Engineers who won't commit (www.seangoedecke.com)
    53 points by kiyanwang 2 months ago | 59 comments
42. Protecting your time from predators in large tech companies (www.seangoedecke.com)
    51 points by alexmolas 5 months ago | 38 comments
43. Why does AI slop feel so bad to read? (www.seangoedecke.com)
    46 points by scarface_74 5 months ago | 31 comments
44. The future of AI is Ruby on Rails (www.seangoedecke.com)
    42 points by daviducolo 3 months ago | 35 comments
45. Writing a tech blog people want to read (www.seangoedecke.com)
    38 points by gfysfm 5 months ago | 3 comments
46. I don't know how to build software and you don't either (www.seangoedecke.com)
    32 points by gfysfm 7 months ago | 53 comments
47. The future of AI is Ruby on Rails (www.seangoedecke.com)
    23 points by swah 3 months ago | 8 comments
48. What's next after the AI bubble bursts? (www.seangoedecke.com)
    21 points by gfysfm 3 months ago | 26 comments