The Digital Nomad

I have changed jobs frequently over the years and have a strategy now:

1. Understand the Company: Take time to thoroughly understand the company’s culture, values, mission, and goals. This knowledge will help you align your leadership style with the organization’s needs.

2. Build Relationships: Build strong relationships with your team members, peers, and superiors. Get to know their strengths, weaknesses, and aspirations. Building trust is crucial.

3. Assess the Situation: Evaluate the current state of your team or department. Identify strengths and weaknesses, and gather feedback from your team members.

4. Set Clear Goals: Define clear, achievable goals. Ensure that these goals align with the company’s objectives.

5. Develop a Strategy: Develop a strategic plan to achieve your goals. This may involve making necessary changes or improvements.

6. Communicate Effectively: Communicate your vision, expectations, and goals clearly to your team. Maintain open lines of communication, and be receptive to feedback.

7. Lead by Example: Demonstrate the behavior and work ethic you expect from your team. Lead by example in terms of professionalism, dedication, and work quality.

8. Delegate Responsibilities: Delegate tasks and responsibilities to team members based on their strengths and skills. Empower your team to take ownership of their work.

9. Provide Support: Offer support and resources to help your team succeed. Address any obstacles or challenges they encounter.

10. Monitor Progress: Continuously monitor progress toward your goals. Adjust your strategy if necessary and provide regular feedback to your team.

11. Celebrate Achievements: Recognize and celebrate milestones and achievements with your team. This boosts morale and motivation.

12. Learn and Adapt: Be open to learning and adapting as a leader. Stay informed about industry trends and leadership best practices.

13. Lead with Empathy: Show empathy and understanding towards your team members. Be responsive to their needs and concerns.

14. Lead Change Effectively: If your role involves implementing changes, do so with sensitivity and a well-structured plan. Communicate the reasons for change clearly.

15. Seek Mentorship: If possible, seek mentorship from more experienced leaders within the organization or from external sources.

When it comes to code reviews, it’s a common phenomenon that there is much focus and long-winded discussions around mundane aspects like code formatting and style, whereas important aspects (does the code change do what it is supposed to do, is it performant, is it backwards-compatible for existing clients, and many others) tend to get less attention.

The Code Review Pyramid

How to pass any first-round interview

Leveling Up in Job Interviews for Software Engineers

Be clear what you’re trying to say before you write it. Don’t get attached to words you have written; be prepared to scrap what you wrote while you were thrashing around trying to work out what you wanted to say, even if its a whole paper.

Common Bugs in Writing

HN Discussion

A project begins with the excitement and productivity of the initial stages but it can eventually turn into a grind. Thr author highlights the importance of embracing the less enjoyable aspects of the work and finding strategies to push through. Fear of finishing and exposing one’s work to criticism is addressed, emphasizing the need to overcome it and honor the effort invested. The text concludes by emphasizing the deep satisfaction and pride that comes from completing a project, whether it’s the end or the beginning of a new phase, and encourages readers to continue honing their finishing skills.

Finish yoir projects

Productivity

In this passage written by Sam Altman, he shares valuable insights and tips on productivity. Altman emphasizes the significance of compound growth, urging readers to optimize their productivity for long-term success. He highlights the importance of selecting the right tasks and developing strong beliefs. Altman recommends allocating time for reflection, engaging with interesting people, and immersing oneself in nature.

Altman stresses the avoidance of tasks one dislikes and the delegation of responsibilities to others based on their interests and strengths. He encourages considering a major job change if dissatisfaction persists. Altman also believes in the power of learning and emphasizes that individuals can quickly acquire new skills. He encourages surrounding oneself with positive, inspiring individuals who support personal ambitions.

Altman’s system for productivity prioritization revolves around three key pillars: focusing on important tasks, avoiding time-wasting activities, and utilizing lists. He suggests writing down lists on paper, frequently transcribing them, and prioritizing tasks to maintain momentum. Altman advocates for relentless pursuit of important projects and the ability to say no to non-critical tasks. He warns against excessive focus on perfecting productivity systems, emphasizing the importance of working on the right problems.

Altman also addresses physical factors that contribute to productivity, such as sleep, exercise, and nutrition. He shares personal preferences and routines while acknowledging individual variations. Altman underscores the importance of a conducive workspace, including natural light and uninterrupted time. He mentions the use of customized software and the benefits of a work-life balance, nurturing relationships, and engaging in activities that bring joy and mental clarity.

Google Site Reliability Engineer Books

Top 100 Data Structure and Algorithm Interview Questions for Java Programmers

Data Structures for Coding Interviews

Cracking the Senior Software Interview

Top 10 Career Changing Programming Books

Serverless Best Practices

Serverless Microservice Patterns for AWS

How to Get Things Done When You Don’t Feel Like It

HN Discussion

List one task, do it, cross it out

1. What are the project goals?
2. What is the current state?
3. What problems are you trying to solve?
4. What opportunities do you see?
5. What risks do you see?
6. What external dependencies do you have?

Writing Documentation When You Aren’t A Technical Writer

HN Discussion

How to Write Better with The Why, What, How Framework

HN Discussion

Advanced Shell Scripting Guide

HN Discussion

From a former manager

It’s Never 5 Minutes

I found this on Hacker News

The Work is Never Just the Work

HN Discussion