Docs | Smarter.Codes - User contributions [en]

Public:Engineering Speciality Maturity

2026-09-30T10:25:37Z

Tushar Goswami:

In your Software Engineering career you grow in these 2 directions

# Growth in [https://docs.google.com/document/d/1F2asbpWRgNF91nhxbNSewgIGs9hlBGHpoMpiuYAEits/edit?tab=t.0#heading=h.pr0uj126po8v Engineering Specialty]. Eg. Developer, to DevOps, to Big Data Engineer
# Growth in [[Public:Engineering Maturity|Engineering Maturity]] . Eg. Engineer, to Senior Engineer, to CTO
{| class="wikitable"
|'''Job Title'''
|'''Engineer & Senior Engineer'''
|'''Tech & Team Lead'''
|'''Head, VP, CTO'''
|-
|'''Specialties'''
|1-2 Specialties

Full depth
|3-6 Specialties

Half Depth
|All Specialties

Surface Depth
|-
|Implementing
|[https://www.reddit.com/r/learnprogramming/comments/1bhnmf8/comment/kver3ww/?utm_source=share&utm_medium=web3x&utm_name=web3xcss&utm_term=1&utm_content=share_button Fundamentals of Programming]

* Book: Think Like a Programmer
* Book: The Pragmatic Programmer

Book : Beyond Vibe Coding

(fundamentals may vary for roles like Ontology or QE
|[https://www.thoughtworks.com/en-in/radar Technology Radar]
|[[:en:List_of_emerging_technologies|Emerging Technologies]]
|-
|Goals
|2 week Sprints, Quarterly Goals
|Quarterly-Yearly Goals
|1-10yr Goals
|-
|Communication
|[https://app.asana.com/1/1198058329453637/project/1213061764081619/list/1213061766604616 Communicate like Engineer]
|[https://app.asana.com/0/portfolio/1210686940780986/1210687183787031 Communicate like Leader]
|Communicate like Thought Leader
|-
|People
|Upskill anyone who is provided to you
|[[Leaders Developing People]]
|Maintain Job Architecture like this, and create new ones
|}
[[Category:Engineering]]

Public:Engineering Speciality Maturity

2026-09-27T07:37:30Z

Tushar Goswami:

In your Software Engineering career you grow in these 2 directions

# Growth in [https://docs.google.com/document/d/1F2asbpWRgNF91nhxbNSewgIGs9hlBGHpoMpiuYAEits/edit?tab=t.0#heading=h.pr0uj126po8v Engineering Specialty]. Eg. Developer, to DevOps, to Big Data Engineer
# Growth in [[Public:Engineering Maturity|Engineering Maturity]] . Eg. Engineer, to Senior Engineer, to CTO
{| class="wikitable"
|'''Job Title'''
|'''Engineer & Senior Engineer'''
|'''Tech & Team Lead'''
|'''Head, VP, CTO'''
|-
|'''Specialties'''
|1-2 Specialties

Full depth
|3-6 Specialties

Half Depth
|All Specialties

Surface Depth
|-
|Implementing
|[https://www.reddit.com/r/learnprogramming/comments/1bhnmf8/comment/kver3ww/?utm_source=share&utm_medium=web3x&utm_name=web3xcss&utm_term=1&utm_content=share_button Fundamentals of Programming]

* Book: Think Like a Programmer
* Book: The Pragmatic Programmer

Book : Beyond Vibe Coding

(fundamentals may vary for roles like Ontology or QE
|[https://www.thoughtworks.com/en-in/radar Technology Radar]
|[[:en:List_of_emerging_technologies|Emerging Technologies]]
|-
|Goals
|2 week Sprints, Quarterly Goals
|Quarterly-Yearly Goals
|1-10yr Goals
|-
|Communication
|[https://app.asana.com/1/1198058329453637/project/1213061764081619/task/1218892295634429 Communicate like Engineer]
|[https://app.asana.com/0/portfolio/1210686940780986/1210687183787031 Communicate like Leader]
|Communicate like Thought Leader
|-
|People
|Mentor anyone who is provided to you
|[[Leaders Developing People]]
|Maintain Job Architecture like this, and create new ones
|}
[[Category:Engineering]]

Public:Engineering Speciality Maturity

2026-09-27T07:33:32Z

Tushar Goswami:

In your Software Engineering career you grow in these 2 directions

# Growth in [https://docs.google.com/document/d/1F2asbpWRgNF91nhxbNSewgIGs9hlBGHpoMpiuYAEits/edit?tab=t.0#heading=h.pr0uj126po8v Engineering Specialty]. Eg. Developer, to DevOps, to Big Data Engineer
# Growth in [[Public:Engineering Maturity|Engineering Maturity]] . Eg. Engineer, to Senior Engineer, to CTO
{| class="wikitable"
|'''Job Title'''
|'''Engineer & Senior Engineer'''
|'''Tech & Team Lead'''
|'''Head, VP, CTO'''
|-
|'''Specialties'''
|1-2 Specialties

Full depth
|3-6 Specialties

Half Depth
|All Specialties

Surface Depth
|-
|Implementing
|[https://www.reddit.com/r/learnprogramming/comments/1bhnmf8/comment/kver3ww/?utm_source=share&utm_medium=web3x&utm_name=web3xcss&utm_term=1&utm_content=share_button Fundamentals of Programming]

* Book: Think Like a Programmer
* Book: The Pragmatic Programmer

Book : Beyond Vibe Coding

(fundamentals may vary for roles like Ontology or QE
|[https://www.thoughtworks.com/en-in/radar Technology Radar]
|[[:en:List_of_emerging_technologies|Emerging Technologies]]
|-
|Goals
|2 week Sprints, Quarterly Goals
|Quarterly-Yearly Goals
|1-10yr Goals
|-
|Communication
|[https://app.asana.com/1/1198058329453637/project/1213061764081619/task/1218892295634429 Communicate like Engineer]
|[https://app.asana.com/0/portfolio/1210686940780986/1210687183787031 Communicate like Leader]
|Communicate like Thought Leader
|-
|People
|Mentor anyone who is provided to you
|Hire / Remove People
|Make Job Architecture, and tables like these
|}
[[Category:Engineering]]

Public:Engineering Speciality Maturity

2026-09-27T07:30:42Z

Tushar Goswami:

In your Software Engineering career you grow in these 2 directions

# Growth in [https://docs.google.com/document/d/1F2asbpWRgNF91nhxbNSewgIGs9hlBGHpoMpiuYAEits/edit?tab=t.0#heading=h.pr0uj126po8v Engineering Specialty]. Eg. Developer, to DevOps, to Big Data Engineer
# Growth in [[Public:Engineering Maturity|Engineering Maturity]] . Eg. Engineer, to Senior Engineer, to CTO
{| class="wikitable"
|'''Job Title'''
|'''Engineer & Senior Engineer'''
|'''Tech & Team Lead'''
|'''Head, VP, CTO'''
|-
|'''Specialties'''
|1-2 Specialties

Full depth
|3-6 Specialties

Half Depth
|All Specialties

Surface Depth
|-
|Implementing
|[https://www.reddit.com/r/learnprogramming/comments/1bhnmf8/comment/kver3ww/?utm_source=share&utm_medium=web3x&utm_name=web3xcss&utm_term=1&utm_content=share_button Fundamentals of Programming]

* Book: Think Like a Programmer
* Book: The Pragmatic Programmer

Book : Beyond Vibe Coding

(if you're an engineer but non-programmer like Ontology Engineer, then suggest what is "fundamentals" in your space)
|[https://www.thoughtworks.com/en-in/radar Technology Radar]
|[[:en:List_of_emerging_technologies|Emerging Technologies]]
|-
|Goals
|2 week Sprints, Quarterly Goals
|Quarterly-Yearly Goals
|1-10yr Goals
|-
|Communication
|[https://app.asana.com/1/1198058329453637/project/1213061764081619/task/1218892295634429 Communicate like Engineer]
|[https://app.asana.com/0/portfolio/1210686940780986/1210687183787031 Communicate like Leader]
|Communicate like Thought Leader
|}
[[Category:Engineering]]

Public:Engineering Speciality Maturity

2026-09-27T06:54:02Z

Tushar Goswami: Created page with "In your Software Engineering career you grow these 2 directions # Growth in [https://docs.google.com/document/d/1F2asbpWRgNF91nhxbNSewgIGs9hlBGHpoMpiuYAEits/edit?tab=t.0#heading=h.pr0uj126po8v Specialty]. Eg. Developer, to DevOps, to Big Data Engineer # Growth in [https://www.amazingcto.com/roadmap-become-cto-career-promotion/ Maturity]. Eg. Engineer, to Senior Engineer, to CTO Category:Engineering"

In your Software Engineering career you grow these 2 directions

# Growth in [https://docs.google.com/document/d/1F2asbpWRgNF91nhxbNSewgIGs9hlBGHpoMpiuYAEits/edit?tab=t.0#heading=h.pr0uj126po8v Specialty]. Eg. Developer, to DevOps, to Big Data Engineer
# Growth in [https://www.amazingcto.com/roadmap-become-cto-career-promotion/ Maturity]. Eg. Engineer, to Senior Engineer, to CTO

[[Category:Engineering]]

Public:Engineering Maturity

2026-09-27T06:53:59Z

Tushar Goswami: Created page with "In your Software Engineering career you grow in maturity. Eg from an Engineer, to a Senior Engineer, to a CTO. Inspired from [https://www.amazingcto.com/roadmap-become-cto-career-promotion/ Amazing CTO book] this evolves your Job Titles as follows # Engineer # Senior Engineer —chasm1-- # Tech Lead # Team Lead / Engineering Manager —chasm2— # Head of Engineering # VP of Engineering # CTO Most engineers stay before Chasm1 (which is perfectly alright). Because wha..."

In your Software Engineering career you grow in maturity. Eg from an Engineer, to a Senior Engineer, to a CTO. Inspired from [https://www.amazingcto.com/roadmap-become-cto-career-promotion/ Amazing CTO book] this evolves your Job Titles as follows

# Engineer
# Senior Engineer —chasm1--
# Tech Lead
# Team Lead / Engineering Manager —chasm2—
# Head of Engineering
# VP of Engineering
# CTO

Most engineers stay before Chasm1 (which is perfectly alright). Because what works before Chasm1, doesn't works afterwards. Same with Chasm2.
[[Category:Engineering]]

Public:Market Sizing

2026-09-22T02:39:57Z

Tushar Goswami:

[[File:TAM segregrated by Engagement.png|thumb|Read more about Marketing Sizing and ICP from [https://www.udemy.com/course/abm_masterclass/learn/lecture/31609354#overview ABM MasterClass Course > Chapter7 and Chapter8]]]
To market to your audience you first understand your market. This is done by [[google:market+sizing|Market sizing]].

[[File:Public:TAM-Image.png|600x600px]]

== Examples ==

=== 1. Fast Food Restaurants space ===
[[File:Public:TAM-SAM-SOM-EVG-Market-Sizing.png|600x600px]]

=== 2. Database as a Service space ===
[[File:TalkingDB Market Sizing.png|none|thumb|600x600px|Notice the 3 citations at the bottom of the screenshot]]
Full Deck : [https://canva.link/9csqivi7w9581nl TalkingDB - Pitch for Eureka 2026]

== Tools ==
There are various online tools you can use to calculate the TAM, SAM, SOM

When writing SAM often entrepreneurs just assume some % of market they "wish" to capture (that's called top-down approach). Instead use the [https://www.scalepath.io/post/top-down-bottom-up-difference-total-addressable-market-tam bottoms-up approach] as shown in this here : [https://youtu.be/Zauegs7RljM Video: Market Sizing for B2B using LinkedIn Campaigns]

[[Category:Marketing]]
[[Category:Product Management Artifacts]]

Public:Market Sizing

2026-09-22T02:37:50Z

Tushar Goswami:

[[File:TAM segregrated by Engagement.png|thumb|Read more about Marketing Sizing and ICP from [https://www.udemy.com/course/abm_masterclass/learn/lecture/31609354#overview ABM MasterClass Course > Chapter7 and Chapter8]]]
To market to your audience you first understand your market. This is done by [[google:market+sizing|Market sizing]].

[[File:Public:TAM-Image.png|600x600px]]

= Examples =

== 1. Fast Food Restaurants space ==
[[File:Public:TAM-SAM-SOM-EVG-Market-Sizing.png|600x600px]]

= 2. Database as a Service space =
[[File:TalkingDB Market Sizing.png|none|thumb|600x600px|Notice the 3 citations at the bottom of the screenshot]]
Full Deck : [https://canva.link/9csqivi7w9581nl TalkingDB - Pitch for Eureka 2026]

== Tools ==
There are various online tools you can use to calculate the TAM, SAM, SOM

When writing SAM often entrepreneurs just assume some % of market they "wish" to capture (that's called top-down approach). Instead use the [https://www.scalepath.io/post/top-down-bottom-up-difference-total-addressable-market-tam bottoms-up approach] as shown in this here : [https://youtu.be/Zauegs7RljM Video: Market Sizing for B2B using LinkedIn Campaigns]

[[Category:Marketing]]
[[Category:Product Management Artifacts]]

Public:Market Sizing

2026-09-22T02:28:57Z

Tushar Goswami:

[[File:TAM segregrated by Engagement.png|thumb|Read more about Marketing Sizing and ICP from [https://www.udemy.com/course/abm_masterclass/learn/lecture/31609354#overview ABM MasterClass Course > Chapter7 and Chapter8]]]
To market to your audience you first understand your market. This is done by [[google:market+sizing|Market sizing]].

[[File:Public:TAM-Image.png|600x600px]]

= Examples =

== 1. Fast Food Restaurants ==
[[File:Public:TAM-SAM-SOM-EVG-Market-Sizing.png|600x600px]]

= Tools =
There are various online tools you can use to calculate the TAM, SAM, SOM

When writing SAM often entrepreneurs just assume some % of market they "wish" to capture (that's called top-down approach). Instead use the [https://www.scalepath.io/post/top-down-bottom-up-difference-total-addressable-market-tam bottoms-up approach] as shown in this here : [https://youtu.be/Zauegs7RljM Video: Market Sizing for B2B using LinkedIn Campaigns]

[[Category:Marketing]]
[[Category:Product Management Artifacts]]

Public:Values

2026-07-06T16:04:29Z

Tushar Goswami:

This article is WIP. Please rather refer to the Values we've documented on Notion.so rather - until we clean the following article
----We adhere to the following core values while making any decision in [[About Smarter. Codes|Smarter.Codes]]:

== 1. COLLEAGUE > CUSTOMER ==
Making a customer happy is important. But making a colleague happy and competent is even more important than customers. Because a single happy and competent colleague can result in 1000s of happy customers.

== 2. ALIGN & DELIVER ==

==== A. ‘Why’ is the best question ====
When working on a task these are the questions you ask

* What is the task
* How to do the task
* When to do the task
* Why are you doing the task

Turns out ‘why’ could be one of the most important questions. Because it helps shape the ‘what, how, and when’. Hence in every task you do we would like you to ‘write down the why’. There is even a book on that now – Start with Why!

'''Align the ‘Why’ of Team'''

Whatever ‘why’ your task has, it helps to the ‘why’ of your colleagues and the ‘why’ of Smarter. Codes company.

It can be empowering if the ‘why’ of everyone at Smarter.Codes aligns before the day begins. Afterall, if the purpose remains aligned, we all progress in the right direction, at a quicker pace.

'''Tell your Why in everything you do'''

In your issue tracker (say Gitlab), task list software (say Trello). So that others reading your work can understand why it is important to work on whatever you are working on

==== B. DELIVER, EVERY WEEK ====
Read how to [[Deliver every week]]

== 3. SHOW EVERYTHING. SEE EVERYTHING ==
Whatever you do, Show it to your people.

Promptly. Every hour. Avoid the ‘''I will show once I am done''’ instinct.

Now that everyone is spending time to show ‘their everything’, do take time out of ‘YOUR daily work’ to check and acknowledge what everyone is working on, and how they are doing it.

When you show and see WIP work of yours and others, it helps everyone to give feedback faster, rather than waiting for all the signals to turn green.

'''''A. Show what you are doing'''''

'''''B. Show how you are doing'''''

'''''C. Show why you are doing'''''

Read more : [[:Category:Show Everything. See Everything]]

== 4. EFFICIENCY ==
'''Smarter.Codes is efficient if'''

* We as individuals are efficient
* We as team are efficient

=== A. Biohacking ===
To keep each individual efficient, we employ holistic methods in Biohacking. Just like in the gym you can train your body to perform better physiologically – likewise you can train your brain to perform better cognitively. We are employing holistic biohacking at Smarter.Codes to enable each one of us to contribute one notch above our mental capacities. At Smarter.Codes we should play to our ‘biological advantage’ to ship amazing stuff for our users.

Check out some advice on Biohacking at Smarter.Codes.

=== B. Upskilling ===
To keep each individual efficient, we embrace [[:Category:Upskilling]] among everyone.

== 5. SIMPLIFY ==

=== A. User Experience ===
Users should find the Products we create ‘easy’ and ‘delightful’ when they are using it

=== B. Colleague Experience ===
Users will get ‘easy and delightful’ products, if people at Smarter.Codes make it ‘easy and delightful’ for their colleagues to ‘together build’ the product.

Public:Sequence Diagram

2026-03-23T16:51:35Z

Tushar Goswami:

[[:en:Sequence_diagram|Sequence diagrams]] are often used to illustrate the Actors, and how the actors interact with each other in a sequence.

= See Also =
[https://docs.google.com/document/d/1K6xbZDji_CLyHdHzzLDpOq2zIXIlXfbVoP2rYrsds3c/edit?tab=t.jvvt15lh4dnp#heading=h.rw4jcbe52lho Sequence Diagram excerpt from Productize AI book][[File:Sequence Diagram of HC Inbox.png|thumb|Example Sequence Diagram of [[HC Inbox]]]]

= Tools =
You can use a free style diagramming tool like draw.io or even figma. Some special purpose toosl to
[[Category:Requirements Engineering]]

Public:Task Analysis

2025-09-25T08:45:56Z

Tushar Goswami:

At Smarter.Codes we build AI automation. We automate a task that a human does. [[:en:Task_analysis|Task Analysis]] involves documenting the each and every step that a human performs. Once its documented, we can use this documentation to communicate to customer, and to engineers on what automation would the AI automation cover.

= Example Task Analysis =
[https://dubble.so/library Task Analysis in operating a software]

[https://docs.google.com/document/d/1DDVG6aMnMIudTm7jyhnuqNaPXIaWK1hrHlppYrohQF4/edit?tab=t.0#heading=h.f81a6qr13qnc Task Analysis in Document Writing] - notice how under "Narrative Writing" section in this example we show task analysis done with video recordings

= Template =
Goal of the Task

Steps of the Task (with screenshots)

Who performs what task (with what context and input)
[[Category:Requirements Engineering]]