Tech Yada
Itβs the ultimate example of the difference between a vibe coder and a software engineer π though with that shiro story, we might not be so different after all π
Fundamentals is everything honestly.
It even affects your confidence when you approach your projects.
Because if you're someone who knows how to program without ai.
Then when you're vibing if something goes wrong you can always go and find where the problem is and fix it.
But if you don't have you're fundamentals straight, as soon as something goes wrong and your ai isn't able to figure out what's wrong(sometimes it has no idea what's wrong even when the problem is very simple) you're gonna be stuck and you'll have a high probability of abandoning your project
So please focus on your fundamentals y'all β€οΈπ never have false confidence thinking you can just vibe it.
Even tho it's possible it's just a very bad shiro πβ€οΈπ
It even affects your confidence when you approach your projects.
Because if you're someone who knows how to program without ai.
Then when you're vibing if something goes wrong you can always go and find where the problem is and fix it.
But if you don't have you're fundamentals straight, as soon as something goes wrong and your ai isn't able to figure out what's wrong(sometimes it has no idea what's wrong even when the problem is very simple) you're gonna be stuck and you'll have a high probability of abandoning your project
So please focus on your fundamentals y'all β€οΈπ never have false confidence thinking you can just vibe it.
Even tho it's possible it's just a very bad shiro πβ€οΈπ
β€3π€£2
Tech Yada
Fundamentals is everything honestly. It even affects your confidence when you approach your projects. Because if you're someone who knows how to program without ai. Then when you're vibing if something goes wrong you can always go and find where the problemβ¦
Spot on, Moh! AI is a high-speed machine, but you still need to know how to drive and hold the wheel.
Vibe coding with zero fundamentals is basically trying to cruise in a car that has no engine.
When things break and your AI hits you with 'Sorry about that!' for the tenth time while giving back the exact same error, you're just left there staring at the screen ready to cry.
Under simmered shiro and unearned vibe coding have one thing in common. they're guaranteed to wreck your stomach!
Really important point you made. ππ
Vibe coding with zero fundamentals is basically trying to cruise in a car that has no engine.
When things break and your AI hits you with 'Sorry about that!' for the tenth time while giving back the exact same error, you're just left there staring at the screen ready to cry.
Under simmered shiro and unearned vibe coding have one thing in common. they're guaranteed to wreck your stomach!
Really important point you made. ππ
π₯3π2
Forwarded from only jerk (Mohammed)
Law 10
Core Meaning
- Emotional contagion: Feelings, moods, and negativity spread just like a physical disease.
- Self-inflicted disaster: People who are chronically unfortunate often draw misery upon themselves through poor choices, then pull you down with them.
- The victim trap: Chronic complainers often play the victim, making you feel sympathy until you are completely drained or ruined.
How to Apply It
- Associate with the fortunate: Spend time with positive, productive, and cheerful people to catch their good energy instead.
- Set firm boundaries: Limit your exposure to toxic coworkers, constant complainers, or energy-draining acquaintances.
- Protect your peace: Recognize that you cannot save a drowning person if they refuse to swim; trying to rescue them often sinks you both.
Avoid the unhappy and the unlucky
Core Meaning
- Emotional contagion: Feelings, moods, and negativity spread just like a physical disease.
- Self-inflicted disaster: People who are chronically unfortunate often draw misery upon themselves through poor choices, then pull you down with them.
- The victim trap: Chronic complainers often play the victim, making you feel sympathy until you are completely drained or ruined.
How to Apply It
- Associate with the fortunate: Spend time with positive, productive, and cheerful people to catch their good energy instead.
- Set firm boundaries: Limit your exposure to toxic coworkers, constant complainers, or energy-draining acquaintances.
- Protect your peace: Recognize that you cannot save a drowning person if they refuse to swim; trying to rescue them often sinks you both.
π₯3
Moh @CoolioCodes , what is this thing? Give this kind of developer some advice, come on! Unbelievable π€£
π€£5
Tech Yada
Moh @CoolioCodes , what is this thing? Give this kind of developer some advice, come on! Unbelievable π€£
this is only acceptable if it was sent to an ai agent π
π5
Tech Yada
this is only acceptable if it was sent to an ai agent π
π€£π€£ i couldn't agree more man
π5
Forwarded from TechVibe
Another small GitHub Actions setting thatβs worth knowing
This basically tells GitHub βGive this workflow a read-only token.β
So even if something bad runs inside your CI(like a bad npm package that excute a backdoor commit), it can't use the
It's a simple example of least privilege, only give a workflow the permissions it actually needs. Small line, big security win
@devwitheyob
#TechVibe #GitHubActions #DevOps
permissions:
contents: read
This basically tells GitHub βGive this workflow a read-only token.β
So even if something bad runs inside your CI(like a bad npm package that excute a backdoor commit), it can't use the
GITHUB_TOKEN to push code, modify your repo, or mess with things.It's a simple example of least privilege, only give a workflow the permissions it actually needs. Small line, big security win
@devwitheyob
#TechVibe #GitHubActions #DevOps
π3β€2
Hey fam, Iβm working on a Backend Engineering roadmap for anyone who wants to learn it. It will include videos, notes, books, and hands-on exercises. Iβll share it with you as soon as I finish π€ Just stay tuned right here on this channel !
share this someone wants to learn backend engineering!!
@TechYada21
#Backend_Engineering
share this someone wants to learn backend engineering!!
@TechYada21
#Backend_Engineering
π8
Now we are officially part of the Omarchy familyβ€ . Greetings to all the Omarchy relatives, friends, users and stakeholders π
β€4
you are not always broken by life; sometimes you are killed by your own thoughts
@Techyada21
#from_LinkedIn
@Techyada21
#from_LinkedIn
π2π₯2
Tech Yada
Hey fam, Iβm working on a Backend Engineering roadmap for anyone who wants to learn it. It will include videos, notes, books, and hands-on exercises. Iβll share it with you as soon as I finish π€ Just stay tuned right here on this channel ! share this someoneβ¦
Backend Engineering Roadmap & Learning Hub for developers who want to bridge the gap between building toy APIs and architecting resilient, high-throughput distributed systems.
Itβs structured across 7 Architectural Mastery Phases & 31 Exhaustive Modules:
β’ Linux Kernel & Low-Level Systems Programming
β’ Production Networking Primitives (TCP/UDP, HTTP/2, gRPC)
β’ Storage Engine Internals (LSM-Trees, B-Trees, WAL, Replication)
β’ Distributed Coordination & Consensus (Raft, Paxos, Quorums)
β’ Message Brokers & Event Streams (Kafka, Event-Driven Architectures)
β’ High-Throughput Caching & Distributed Rate Limiters
β’ Cloud-Native Infrastructure, Observability & Security
check it out: link
share this someone wants to learn backend engineering!!
@Techyada21
#Backend #Backend_Engineering #Roadmap
Itβs structured across 7 Architectural Mastery Phases & 31 Exhaustive Modules:
β’ Linux Kernel & Low-Level Systems Programming
β’ Production Networking Primitives (TCP/UDP, HTTP/2, gRPC)
β’ Storage Engine Internals (LSM-Trees, B-Trees, WAL, Replication)
β’ Distributed Coordination & Consensus (Raft, Paxos, Quorums)
β’ Message Brokers & Event Streams (Kafka, Event-Driven Architectures)
β’ High-Throughput Caching & Distributed Rate Limiters
β’ Cloud-Native Infrastructure, Observability & Security
check it out: link
share this someone wants to learn backend engineering!!
@Techyada21
#Backend #Backend_Engineering #Roadmap
Backend Engineering Roadmap
Backend Engineering Master Roadmap | Open Learning Hub
Master backend engineering: 31 exhaustive deep dives, 51 video lectures, 124 multi-language code snippets, and 7 production portfolio capstones.
π2π₯°1
Forwarded from only jerk (Mohammed)
hey guys hopefully everyone had a pleasing day/evening.
If you're currently working on that "one last feature" I suggest you finish it up and get rested.
You have a great day full of challenges and mysteries ahead of you tomorrow and the best way approach it by having a good night sleep.
So if you're on social media scrolling, 120% stop that and instead listen to a podcast or watch a movie instead (best option: read a book).
DO NOT SCROLL BEZI SAET π«
I'm wishing you a pleasant rest, see you tomorrow πβ€οΈ
If you're currently working on that "one last feature" I suggest you finish it up and get rested.
You have a great day full of challenges and mysteries ahead of you tomorrow and the best way approach it by having a good night sleep.
So if you're on social media scrolling, 120% stop that and instead listen to a podcast or watch a movie instead (best option: read a book).
DO NOT SCROLL BEZI SAET π«
I'm wishing you a pleasant rest, see you tomorrow πβ€οΈ
β€3