Izzoh☕

software Engineer.
Backend

[Izzoh☕ @izzoh254]

@dan_tiema @ForensicsKuria @BullrunIO Make an impact where jobs are sexually transmitted and not given on merit? Where even County governments make it difficult to get a business License? ati "uongee vizuri ndo we process faster "

[Izzoh☕ @izzoh254]

@nyaga_masharia @Kristianke1 @StanleyMasinde_ In fintech as a developer some companies still underpay, example some company I work for pays junior 40k, midlevel 70k, senior 120k, keep in mind our solutions are majorly for banks and saccos. (Established banks both in Ke and Tz) . In 2024 they reported a $500k revenue

[Izzoh☕ @izzoh254]

@MjengoKE @Editorial53 @georgediano Read again bois😂

[Izzoh☕ @izzoh254]

@Qiborke @onjolo_kenya You mean there is that CS position? Maajabu

[Evan Luthra @EvanLuthra]

Anthropic pays engineers $750,000+ a year to understand how LLMs work.

Stanford just put a 2 hour lecture that covers 80% of it for FREE.

Bookmark this. Give it 2 hours today.

It might be the highest ROI thing you do this month:

[Izzoh☕ @izzoh254]

@leemorio @c_ngeno5 @KipropK36205 A7??😂😂 waaah, maybe you meant A5

[Izzoh☕ @izzoh254]

@michaelbukachi Yes man, I even heard Grafana for the first time from you 😂 I was Like “fofana”I thought Fofana is football player. But thank you, it was a nice ride G @MarketForceHQ

[R𝛼m 🦅 @rambuilds_]

Go (Golang) Roadmap for Backend Engineers,
Who Want to Ship Fast:

1. Master the Basics : Syntax, variables, loops, functions, packages & modules

2. Understand Go’s Real Power : Structs, interfaces, composition & embedding

3. Master Pointers : Learn how they work, when to use them, and why they matter

4. Goroutines & Channels : The real reason people choose Go → master concurrency here

5. Error Handling : Learn proper error wrapping, custom errors & context

6. Build CLI Tools : Use → flag, cobra or urfave/cli,
make something useful

7. Work with Data : Files, JSON, YAML, HTTP clients & basic APIs

8. Build REST APIs : Use Gin or Fiber + proper routing, middleware & validation

9. Advanced Concurrency : Worker pools, pipelines, fan-in/fan-out, rate limiting

10. Database Layer : PostgreSQL + GORM or sqlx + proper connection pooling

11. Testing & Quality : Unit tests, table tests, benchmarks & integration tests

12. Production Ready : Docker, logging, graceful shutdown, config management, observability

Bonus Steps:
- Read Go source code of popular packages
- Build 3 real projects (Auth service, Background worker, Scraper)

Stop just “learning Go”

Follow this → become → production dangerous

Save it.
Follow it.
Ship it.

Who’s starting this journey in 2026?

[Izzoh☕ @izzoh254]

@marvellousbh @michaelbukachi opened my eyes back in 2022😅

[Izzoh☕ @izzoh254]

@shadrac_matata In tech the moment you sign that contract, you start actively looking for another opportunity

[Izzoh☕ @izzoh254]

@codeinecraizeey @_wawiny I know majority have their way, minority have their say, wacha nikue hapo kwa minority. Maraga for presidency ✊🏿

[Abhishek Singh @0xlelouch_]

93.5% of Senior Backend Engineer interviews are just these 7 concepts repeated again and again.

[Prajwal @0xPrajwal_]

Golang is trending.

Seeing so many new role openings lately.

Go (Golang) Roadmap for Backend Engineers,
Who Want to Ship Fast:

1. Master the Basics : Syntax, variables, loops, functions, packages & modules

2. Understand Go’s Real Power : Structs, interfaces, composition & embedding

3. Master Pointers : Learn how they work, when to use them, and why they matter

4. Goroutines & Channels : The real reason people choose Go → master concurrency here

5. Error Handling : Learn proper error wrapping, custom errors & context

6. Build CLI Tools : Use → flag, cobra or urfave/cli,
make something useful

7. Work with Data : Files, JSON, YAML, HTTP clients & basic APIs

8. Build REST APIs : Use Gin or Fiber + proper routing, middleware & validation

9. Advanced Concurrency : Worker pools, pipelines, fan-in/fan-out, rate limiting

10. Database Layer : PostgreSQL + GORM or sqlx + proper connection pooling

11. Testing & Quality : Unit tests, table tests, benchmarks & integration tests

12. Production Ready : Docker, logging, graceful shutdown, config management, observability

Bonus Steps:
- Read Go source code of popular packages
- Build 3 real projects (Auth service, Background worker, Scraper)

Stop just “learning Go”

Follow this → become → production dangerous

Save it.
Follow it.
Ship it.

[Izzoh☕ @izzoh254]

@Mugovictor001 @amerix @GeorgeYOUniq_ @JohnMbadiN You’re just stupid, talking about exchange rate and the price of kerosene. We are deeply concerned about the tax imposed on fuel. In this case we focus on petrol and Diesel.

[Izzoh☕ @izzoh254]

@Bastaprenuer @Odhiswhatis @Kama36378Kamau So upewe contract ama????

[pablo @fernandezpablo]

Quizás el único libro que vale la pena comprar dos veces 🐗 ❤️

[avrl ☘ @avrldotdev]

Step-1: Learn Go
Step-2: Learn goroutines, channel & ascheduler
Step-3: Master pointers, interfaces & malloc
Step-4: Build an HTTP server with std lib
Step-5: Read the Go runtime & standard library source. Embrace humility
Step-6: Build a production-grade backend (REST/gRPC, DB, caching, msging)
Step-7: Make it resilient under load
Step-8: Learn profiling and optimization (pprof, trace, benchmarks)
Step-9: deploy with Docker & K8s
Step-10: Ship it

[Izzoh☕ @izzoh254]

@dev_maks @michaelbukachi @mwangi_kabiru Sema Software development, ati CS as side quest, you just want to look smart lol. Do you know how wide CS is???

[Izzoh☕ @izzoh254]

@roomthinker "What further freedom would you ask from me?"So it is the presidents who gives freedom😂, Thought the constitution states that?

[Izzoh☕ @izzoh254]

@_saginii V8??😂, foreign owned , occasionally driven 😂, 2019 na hiyo front grill? Atalia. I see red flags allover