@stoney.codes: Here are some software engineering concepts that can cause a mental paradigm shift in your work, helping you level up from junior engineer to senior. 💡 This includes technical engineering concepts like writing maintainable code instead of speed optimised code (Big O Time Complexity) and whether monolithic codebases are good or bad. 🏃🏻♂️ This also includes more career oriented misconceptions like whether meetings matter, and the fact senior engineers are valued on their system design skills over their ability to write code - especially now with AI code assistance lower the bar for code writing ability. 👔
“coding skills dont matter” alright buddy tell that to tsoding or primeagen or even linus himself
2026-09-13 23:53:10
5
Anon :
As a CTO - agree on most, disagree on rational ignorance and forget speed. Your brain can fit more than you think. You should always be learning new ideas, frameworks (not in depth, but at least their killer feature), and patterns. If you’re not learning, you’re not growing. Forget speed is ok at a startup, but it’s the antithesis of what your mindset needs to be at scale. A 2% improvement on an app that has 50k users decreases your cost of revenue and allows you to add 1,000 more users without increasing infra cost (assuming cloud here)
2026-09-10 19:49:36
9
Dylan :
Gpt written post
2026-09-10 01:05:49
64
Lu Ca :
i was with u until u threw in everyone can code. if u push that crap into the codebase that codex creates when u dont supervise it properly ur out. that creates the opposite of readable and maintainable code
2026-09-10 06:55:44
41
Scribby :
By coding skills don’t matter do you mean the actual act of typing or the fundamental knowledge needed to write that code?
2026-09-09 23:12:56
6
Eli 🪽 :
Ignoring big O is wasting money and compute for your personal comfort (too lazy to lock in)
2026-09-10 02:56:52
16
g.sch68 :
Why forget speed ? You can write a fast and readable code lol
2026-09-10 07:40:11
6
Frank Casanova :
I agreed with all this stuff point by point. greetings from a software engineer at Toyota! :)
2026-09-10 11:16:23
11
Shadow Blade :
5th slide is kind of stupid, you can't properly design a system and pick tradeoffs without programming skills
2026-09-11 15:01:26
4
Kyrr :
I feel lost trying to find the best concepts to study on for my career in cs, I don’t know what to focus on and what I need to do to be prepared for work. Can anyone help me with this, I’m just very uncertain. I do want to aim high and I ideally want to get an opportunity to work on a big tech company someday if my abilities can manage. I just want to be certain with what I’m focusing on because I feel like our university’s curriculum isn’t helping me much.
2026-09-10 09:39:19
3
. :
in the age of AI 100% coverage is fine since AI is writing them
2026-09-12 15:56:27
7
Spenc55 :
Yeah but I need to be an expert in 15 languages just to get an interview
2026-09-10 03:53:40
2
herglowdiaries :
These are just good life tips unironically if applied more broadly haha, and rehashed proverbs which are the OG life pro-tips
2026-09-10 14:17:15
1
My name is unique :
Good advices but good luck bro cuz u have to reply every single comment to let them know what exactly your purpose is 😂
2026-09-10 13:09:11
1
JC :
“Forget speed”??? Omg ofc code has to be readable but there’s documentation for SOME REASON, so you can optimize resources
2026-09-10 12:08:49
1
CaptainLift :
Regarding meetings, having a clear goal of what is to be solved during the session is the most important prerequisite. Then writing what is to be done and when is as important. Otherwise meeting is just hot air
2026-09-10 08:04:51
1
debugandoavida :
I never used big O. Of course you do need to learn it, but using it is more of a lucky coincidence than a project necessity.
2026-09-10 08:39:08
1
TCE-Veille Pour Solopreneurs🤖 :
ARCHITECT CODE !!!! ARCHITECT CODE !!!!!!!’nnn
2026-09-09 22:24:44
6
potatohead :
tehee baka
2026-09-09 22:41:18
1
desumafia :
isn't it like common sense? im just an indie dev and suck at coding, but i thought all IT people would know that and much more even, never thought that you could get a job in this field without knowing that you should write readable code and say something useful during meetings
2026-09-12 21:34:14
0
algernonalleng :
The amount of times this was saved shows that it is worth it 🤌🏾🫶🏾💪🏾
2026-09-10 13:05:02
2
Christopher^ 🌼 :
I’m taking tip 3 a little too seriously. My code doesn’t even compile.
2026-09-10 02:26:51
1
ягорячиймексиканец :
"monoliths arent always bad" brotha, microservices in 90% of times are the one thats bad. 90% cases monolith > microservices. The only real reason to use microservices is large team, period. Other bonuses like independent scalability / fault isolation are nice but usually come as a bonus, and not as a "reason" to pick microservices. And u can have very big highload with monoliths
2026-09-10 13:47:07
3
𖿤 :
as a site reliability engineer: learn kubernetes, it is my favorite larp
2026-09-10 01:05:38
4
thebookjourney44 :
Great advice
2026-09-10 08:56:25
1
To see more videos from user @stoney.codes, please go to the Tikwm
homepage.