The Best Software Engineering Advice | Prime Reacts

This is a place for all the things that are awesome on stream. 

The PrimeTime

Advice from 20 Years of Programming Experience

The speaker shares advice based on their 20 years of experience in engineering.

The speaker receives many questions and observes many developers making wrong decisions.

Many developers are seen as slaves to the tech community, constantly chasing the latest meta.

The speaker criticizes the habit of constantly learning new languages and frameworks without a clear career path.

The speaker emphasizes the importance of a long-lasting and fulfilling career path.

Starting Programming Career and Language Choices

Most programmers start with languages like C or Java, depending on their background.

The speaker's initial experience was with Java and C.

Many current programmers start with JavaScript through bootcamps, unlike the speaker's experience.

The speaker notes a lack of common foundational knowledge among programmers due to diverse entry points.

A C or C++ background is considered a superpower due to understanding of computer architecture.

The speaker warns against constantly chasing new technologies and languages found on social media.

The speaker mentions several examples of trendy languages like Gleam, Rust, and Zig.

The speaker discusses the potential of Zig, particularly in low-level programming.

The speaker acknowledges that developers go through phases of learning new technologies but warns against the pitfalls of constantly chasing the meta.

The speaker argues that learning a new meta is often outdated by the time it's learned.

Finding Balance in Learning New Technologies

The speaker acknowledges the value of learning new languages like OCaml but cautions against constantly switching.

The speaker suggests planned meta-learning sessions instead of constantly jumping between technologies.

The speaker describes their approach of mastering one technology while exploring others intentionally.

The speaker reiterates the importance of setting goals and not chasing the latest trends.

The speaker explains their approach to learning Rust, setting specific goals and focusing on proficiency.

Finding Joy and Satisfaction in Programming

The speaker discusses the disillusionment that can occur when the initial excitement of programming fades.

The speaker emphasizes the importance of finding joy and satisfaction in the problem-solving aspect of programming, not just the novelty of new technologies.

The speaker shares their personal experience of finding joy in making their current work more stable and efficient.

The speaker draws a parallel between finding joy in programming and maintaining long-term relationships.

The speaker clarifies that the issue is not with the technology itself, but with the repetition of the same tasks over extended periods.

The speaker distinguishes between happiness (passive) and joy (active) in the context of work satisfaction.

Focusing on Goals and Solutions over the Hype

The speaker argues against seeking dopamine from language changes and emphasizes finding joy in the goal and solution.

The speaker acknowledges the joy in personal development but cautions against using it as an escape from boredom.

The speaker uses their Vim configuration as an example of improving efficiency rather than seeking dopamine.

The speaker clarifies the difference between satisfaction (from building something) and happiness (passive).

The speaker reiterates that finding joy in the goal and solution is crucial for long-term satisfaction.

The speaker acknowledges the importance of money but emphasizes that it shouldn't be the primary driver.

The Impact of Financial Security on Job Satisfaction

The speaker suggests that high income in software engineering can lead to dissatisfaction due to lack of necessity.

The speaker notes that software engineers often earn disproportionately high incomes compared to the median.

The speaker hypothesizes that many problems arise from a lack of necessity, unlike in past eras.

The speaker contrasts the direct impact of work on survival in the past with the often less tangible impact today.

The speaker suggests that working at a startup can be more fulfilling due to the direct impact on the product.

Efficiency vs. Enjoyment in Work and Life

The speaker emphasizes the importance of focusing on goals and solutions, rather than being overly concerned with efficiency.

The speaker and the commenter disagree on the prioritization of efficiency, with the commenter arguing against always optimizing.

The commenter uses the example of relationships to illustrate that not everything should be optimized for efficiency.

The commenter's viewpoint is that some projects should be undertaken for the sake of learning and enjoyment, not just efficiency.

The commenter advocates for a balance between efficiency and exploration, suggesting that sometimes inefficiency is necessary for discovery.

Choosing the Right Tools and Technologies

The speaker emphasizes that the choice of language or technology is less important than focusing on goals and solutions.

The speaker acknowledges that different jobs may require different technologies and that exploring new technologies can improve efficiency.

The speaker explains why they didn't pursue OCaml, prioritizing practical applicability over theoretical interest.

The speaker warns against choosing technologies solely based on potential income, emphasizing proficiency over breadth of knowledge.

The speaker shares their experience of choosing JavaScript for internal tools at Netflix, prioritizing compatibility over optimal performance.

The speaker describes using Rust for initial exploration and then switching to JavaScript for a production tool, illustrating the value of choosing the right tool for the job.

The speaker suggests choosing technologies based on overlap with desired career paths and projects.

Conclusion: Focusing on Problem Solving and Goals

The speaker reiterates that problem-solving skills are more important than proficiency in specific languages.

The speaker emphasizes the importance of making mistakes and learning from them.

The speaker advises choosing the right tool for the job, but acknowledges that sometimes it's necessary to choose the wrong tool.

The speaker concludes by encouraging viewers to focus on their goals and solutions, not just the latest technologies.

The commenter summarizes the video's key points and agrees with the speaker's advice.

The Best Software Engineering Advice | Prime Reacts

Scripts