North
@north3141Like you and me, they just want to learn.
Life is good. - I look forward to my morning routine and start it after waking up. - I look forward to the workday and start it after my morning routine. - I look forward to exercising and exercise after the work day. - I look forward to dinner and have dinner after exercise. -…
"Show me your flowcharts and conceal your tables, and I shall continue to be mystified. Show me your tables, and I won't usually need your flowcharts; they'll be obvious." Sometimes communicating at a lower-level is the best way to communicate at a higher-level.
"Experience is not a very pleasant teacher, but in some cases it's the only the effective one." Such an important idea. Yet another point for Ben Franklin.
I'm a believer of skimming many books when you're younger, and then over time doing more and more re-reading of fewer books. Gotta start by exploring! Don't commit to fewer books too soon!
A big thing to watch out for: taking lessons from some first experience with something as generalizable. The outside view says it's very difficult to tell whether a lesson is general or particular.
Gotta respect bottlenecks. There's often one component which is holding up the rest, and trying to push through on account of the other components being ready to go is often a bad way forwards.
TODO Think more about the idea of a privileged class which is for the best, and yet substitutable. It's a powerful idea which applies to many fields.
A tip for communication: perform multiple passes at different levels of abstraction. For each pass, there might be multiple topics. The goal is to end up with each topic scoped to people's ability to absorb it singularly.
The main problem software engineering teams solve at large companies is deployment at scale.
Being a great programmer is all about knowing when to making exceptions to rules. This is very hard to teach. By its very nature, there's no rule for how to do it.
Time locality is an important idea. e.g. it's immensely more effective to do a post-mortem soon after a project finishes, as opposed to long after it finishes
Very well said
lots of problems seem to be a result of people not being able to tell the difference between two perfectly distinguishable things when they're referred to by the same abstract noun
It's difficult to describe how to write good comments. It's similar to describing "how to think".
"Can great developers be taught?" is an insanely overlooked question with far-reaching implications
Why, what, and how are actually extremely related terms in a way I think is often overlooked. In some sense, they are defined relative to one another. How is a lower level view of what, and what is a lower level view of why.
Idea: comment checker which uses LLMs to detect when comments have fallen out of date relative to code.
At one point I thought looking like you went to the gym meant having big muscles. Now I realize that looking like you go to the gym means being generally fit.
United States Trends
- 1. Kash 649 B posts
- 2. Houston 32,3 B posts
- 3. Texas 181 B posts
- 4. #FayeYokoYentertainAwards 65,1 B posts
- 5. SPOTLIGHT COUPLE FAYEYOKO 67 B posts
- 6. Iowa State 10,2 B posts
- 7. #HookEm 15,5 B posts
- 8. #LAGalaxy 1.990 posts
- 9. #BYUFootball 1.050 posts
- 10. Fauna 86,3 B posts
- 11. Ewers 10,3 B posts
- 12. McCabe 39,8 B posts
- 13. Wray 53,7 B posts
- 14. #Toonami 2.689 posts
- 15. Junior Bergen N/A
- 16. Elko 3.368 posts
- 17. Aggies 12,7 B posts
- 18. Oregon 36,5 B posts
- 19. Big 12 30,3 B posts
- 20. MLS Cup 4.098 posts
Something went wrong.
Something went wrong.