_d.olph._

SOFTWARE ENGINEER
TECH ENTHUSIAST
I am the experience
don't miss me out

LET'S CODEEEEE‼️

[SokoAnalyst @SokoAnalyst]

DSTV laughed until Netflix arrived. Taxis slept until Uber moved. Shops ignored Shein and Temu. Newspapers mocked social media. Celebrities dismissed influencers. Every giant thinks disruption is noise, until it becomes the market. The real question is: who is sleeping now?

[_d.olph._ @___dolph]

@MrCharlesky Link

[Sergey Nazarov @sergeynazarovx]

We used to go to a special website, ask strangers for help with programming, and get humiliated in return

[_d.olph._ @___dolph]

Day 8 of infinity
Topic variables with c++
I'm easily distracted by ongoing x conversations and other platforms. So today, Marks 1 week of consistent learning and pushing to github.
For follow-up, as learning is on https://t.co/FY4nxceBQK, is your to go repository . See you on

[_d.olph._ @___dolph]

Day 7 of ∞ Variables in C

tomorrow is here; tomorrow is today
yeah, i know it's all about c++, but today, it's C. It's just for us to get an understanding of c++ from its rootsI love @saylordotorg for its structured course

[_d.olph._ @___dolph]

Day 6/∞ — Learning C++
It's mostly revision today, but everything is finally clicking.
Revisited the first C++ program, preprocessors, streams (cin / cout), and why cin.get() exists.
Less rabbit holes. More structure.
Same concepts clearer meaning.
Day 6 done.Regards, Saylor/org

[_d.olph._ @___dolph]

Day 6/∞ — Learning C++
It's mostly revision today, but everything is finally clicking.
Revisited the first C++ program, preprocessors, streams (cin / cout), and why cin.get() exists.
Less rabbit holes. More structure.
Same concepts clearer meaning.
Day 6 done.Regards, Saylor/org

[_d.olph._ @___dolph]

Day 5: Today started with active recall and code reviews. I revisited the 4 day progress to see what is still in my head regardless of the festive. Luckily, it's all of it/most of it. I had different intentions but what happened was different.
I ended up on void and endl.

[_d.olph._ @___dolph]

@JobFound5 Interested

[_d.olph._ @___dolph]

Day 4/∞
You know the drill, active recall. Leaped to datatypes. Wrote a few lines of code. In the mood for Christmas, I didn't do too much.
Reference: GeeksforGeeks.
There is no medium publication today as my laptop has some charger issues. I did today's learning via phone.

[_d.olph._ @___dolph]

Day 3/∞ — Learning C++
Compiled and ran code manually with g++.
Source code → executable finally clicked.
Curiosity led me into preprocessors, why #include isn’t normal code, and the difference between iostream and stdio.Slowed down. Asked why.Understanding feels deeper now.

[_d.olph._ @___dolph]

Day 3/∞ — Learning C++
Compiled and ran code manually with g++.
Source code → executable finally clicked.
Curiosity led me into preprocessors, why #include isn’t normal code, and the difference between iostream and stdio.Slowed down. Asked why.Understanding feels deeper now.

[Raul Junco @RaulJuncoV]

APIs interviews don’t fail because people can’t code.
They fail because people can’t explain trade-offs.

I’ve seen strong engineers stumble on questions that look basic:

PUT vs PATCH
200 vs 201
Offset vs cursor pagination
Idempotency under retries
Rate limiting choices and why they matter

Interviewers aren’t testing trivia.
They’re testing whether you can reason about real systems under pressure.

I wrote a short survival kit that covers:

- The API fundamentals interviewers actually care about
- The “why” behind common design decisions
- The failure modes most candidates ignore
- Practical examples you can reuse in interviews

No fluff.
No theory for theory’s sake.
Just the mental models that help you think clearly in API interviews.

Read it here 👇
https://t.co/EI9mo6eQJI

If you’re preparing for backend, platform, or system design interviews, this is worth bookmarking.

[_d.olph._ @___dolph]

@AvinashSingh_20 C++

[_d.olph._ @___dolph]

More in-depth details on https://t.co/1Jt3OK7Xic and https://t.co/dbmEPJ7lBE

#BuildingInPublic #C++#programming

[_d.olph._ @___dolph]

Day 3/∞ — Learning C++
Compiled and ran code manually with g++.
Source code → executable finally clicked.
Curiosity led me into preprocessors, why #include isn’t normal code, and the difference between iostream and stdio.Slowed down. Asked why.Understanding feels deeper now.

[_d.olph._ @___dolph]

Learned what `iostream`, `std`, `main()`, and `cout` actually do.
Took a W3Schools C++ intro test → 64%.
Not perfect, but honest progress.
Day 2 done

📂 GitHub: [https://t.co/4SCqetIWRS](https://t.co/4SCqetIWRS)
✍🏽 Medium: [https://t.co/izKibAMcrd](https://t.co/izKibAMcrd)

[_d.olph._ @___dolph]

Day 2/∞ Learning Cycle

Focused on understanding, not speed.
Used active recall on C++ basics → exposed gaps fast.
Asked devs how to learn C++ properly → Stroustrup’s book kept coming up
(Programming: Principles and Practice Using C++ 3rd ed.)
#BuildInPublic

[_d.olph._ @___dolph]

Medium (deeper write-up): https://t.co/PtUIflFOEv

GitHub: https://t.co/nDAYQ7TP5Z

[_d.olph._ @___dolph]

Day 001 / ∞
Self-teaching fails because of over-saturation, not scarcity. I’m cutting through the noise with a structured, module-based roadmap.
Language: C++. Method: Theory → Practice → Theory
The @ColinGalen method
Documentation:
Log: GitHub
Deep Dive: Medium
Let’s build.

[_d.olph._ @___dolph]

Day 001 / ∞
Self-teaching fails because of over-saturation, not scarcity. I’m cutting through the noise with a structured, module-based roadmap.
Language: C++. Method: Theory → Practice → Theory
The @ColinGalen method
Documentation:
Log: GitHub
Deep Dive: Medium
Let’s build.

[JNS @_devJNS]

step 1: learn to code.
step 2: realize you’ll be learning forever.