Icon
ElderSoftware Engineer.
Builder Goal: Successfully master the most important parts of software engineering in the AI age and get hired.
5 followers · 13 respects
Build Journey
Day 1 — Season kickoff
Sep 13
Research, Specifications & Architecture
ShippedDefine all core requirements, outline the project, and prepare materials.
Shipped Oct 12
Make tangible contributions to Opensource
In progressComplete the initial functional version and test with 3-5 trusted peers.
Target Nov 2
Get Hired
QueuedPolishing, documentation, and releasing the completed build to the world.
Target Dec 11
Day 90 — Ship it
Dec 11
Begin system design learning.
Started learning about system design. Covered concept such as what a single server is, its limits and the advantages of relational database.
40 completed · 0 missed · 50 remaining
Accountability Pod
Builders who keep each other honest — tap a pod mate to view their public builder profile.
What They're Building
I'm building my career as a software engineer
Why It Matters
for my career.
Success Looks Like
Skills in Practice
Execution Timeline
Verifiable track record of daily progress and shipped deliverables.
Objective
Complete the design and update LinkedIn cover photo.
What was done
Completed the design and update LinkedIn cover photo.
Proof of Work
Objective
Portfolio and profile optimization..
What was done
I started designing my new cover photo.
Objective
Execution
What was done
Today was focused on reviewing previous the weeks of the builder season with other members.
Objective
Revise new week schedule and start.
What was done
Revision completed
Objective
Prepare for the new week.
What was done
Today was about learning about new technologies and how they work and what they are about.
Objective
Revised the plan created
What was done
Revised the plan created
Objective
dive more into what I should learn
What was done
Focused on creating a blueprint I could follow for my job hunting period when it comes
Proof of Work
Objective
Start closing other Knowledge gaps making preparations for job hunting.
What was done
I focused on identifying what to learn next and preparing strategy I could implement for job hunting.
Objective
Complete the course
What was done
Completed the final part of the technical writing course. Covered how to write report as the last topic of the course.
Proof of Work
Objective
Continue with course.
What was done
HOW TO DESCRIBE A PROCESS ? 1. Define the process 2. List all the materials required for the procedure 3. Accompany all the numbered steps with a diagram 4.Insert special notices in boxes, wherever necessary 5. Use the "imperative' or 'command" style for your instructions
Proof of Work
Objective
Continue with the course.
What was done
COVERED THE 4 PARTS OF A USER MANUAL I. GENERAL BACKGROUND of the product and its salient features 2. INSTRUCTIONS to operate, maintain, repair, install, assemble, etc. 3. SPECIAL NOTICES like Note, Caution, Warning and Danger 4. CONTACT INFORMATION of the manufacturer or service provider
Proof of Work
Objective
Continuation on technical writing.
What was done
COVERED THE STEPS TO DESCRIBING AN OBJECT 1. What is it? What is it used for? (Definition) 2. How does it look? (Labeled diagram) 3. What does it consist of? (Components, Parts, Materials used) 4. How does it function? (Operation, Working)
Proof of Work
Objective
Continue learning technical writing
What was done
Today, I covered the different list that makes a concrete definition in technical writing.
Proof of Work
Objective
Continue the course
What was done
I learnt the different categories of classes in technical writing. We have the tools, instruments, machines. All having their separate differences and what makes them what they are.
Proof of Work
Objective
Continue technical writing course.
What was done
I learnt about classes and how they are used in technical writing.
Proof of Work
Objective
Continue learning about technical writing
What was done
Today, I covered the concept of framing. Framing a concept is a combination of “ term + class + defining characteristics “.
Proof of Work
Objective
Continue learning about technical writing
What was done
Today I learnt about the 2 golden rules of technical writing . 1. Level of language. 2. Level of information.
Proof of Work
Objective
Dived into technical writing.
What was done
I learnt about the origin of the word technical meaning “skill, technique, art , method “.
Proof of Work
Objective
Prepare for the new week.
What was done
Set out clear objectives of what to learn and deeply study in this new week.
Objective
Move onto technical writing.
What was done
80% Writing / 20% Code. They have their main focus to be API and Product documentation.
Objective
Look more into Devrel and technical writing roles
What was done
Developer Relations (DevRel) requires a blend of production coding, public speaking, and community building, compensation scales similarly to traditional Software Engineering (SWE) tracks.
Objective
Set miles stones to achieve for the month.
What was done
Complete research on uncommon software engineering roles..
Daily Remark & Notes
Devrel requires a blend of production coding, public speaking, and community building, compensation scales similarly to traditional Software Engineering (SWE) tracks. Technical writing tracks align closely with product design and engineering operations scales.
Objective
fixed error preventing merge by maintainer.
What was done
found an error present in the contribution made by me and corrected it.
Proof of Work
Objective
i made another opensource contribution
What was done
Researched new good first issues to work on and found a good one. contributed to it.
Proof of Work
Objective
Focused on making research on opensource .
What was done
I prepared a playbook strategy on how to approach contributing to OpenSource appropriately through my research.
Proof of Work
Objective
Plan to optimize my week for the tasks to be done.
What was done
I've set my growthhub objectives for the week.
Daily Remark & Notes
3hrs work focus.
Objective
Try something different and break a usual pattern.
What was done
Connected with an individual and told him about the community.
Objective
OpenSource contribution got merged successfully.
What was done
fixed earlier issues preventing merge.
Proof of Work
https://github.com/lingdojo/kana-dojo/pull/30906Objective
contributed to an opensource project.
What was done
I picked one of the first good issues from yesterday's options.
Proof of Work
Objective
Find a good project that meets the requirements above and meets my tech stack requirements.
What was done
I found several good projects that meets the requirements highlighted in yesterday's post thanks to Github Copilot.
Proof of Work
Inspired to build something meaningful?
Join the GrowthHub ecosystem and build your own 90-day verifiable track record.