Sajid Gul
@itx_sajidgul
Database Engineer | Laravel & NestJs | Data Science Enthusiast | Exploring AI, ML & Prompt Engineering
You might like
I read somewhere that you never get a second chance to make a first impression. It’s so true, isn’t it?
Ever feel your motivation hit a low at work? Happens a lot in corporate jobs and startups. Its not just the long hours or hard work. When effort is not matched by others, and everyone gets the same outcomes, the energy can really dip. Thoughts? #TeamEffort #WorkVibes
Coursera 🤝 Udemy "Fine… let’s lose to ChatGPT together." investor.coursera.com/news/news-deta…
You don’t need to know everything about everything. Just knowing what you’re doing is enough most of the time.
Rule 2: Touch it, if you think you are great at what you are doing.
Recently observed something about CTOs. I see two types: one who stops coding and focuses on managing tech teams as the company grows, and one who still stays in the code while leading from the front. The question is, which products win in the long run? Curious what others think.
I think people mix two things. Vibe coding is building without strong basics, which later causes bad code, security risks, and poor maintenance. AI-assisted coding is different, you know the fundamentals and use AI to move faster. The work is real, the term just sounds wrong.
I am noticing people agree with this post but don't like the term "vibe coding." It's almost as if there needs to be a new term invented that sounds better than "AI assisted coding." Anyone got some ideas?
This debate is pointless. Frontend vs backend are different games. Love design, animation, pretty UIs? → Frontend feels easy & fun. Love puzzles, data, systems? → Backend feels natural. Both are hard work, both pay well. Just pick the one you wake up wanting to touch.
I think they are feeling the pain now, but many will embrace it again once AI tools mature and become truly production-ready.
Companies are pulling back from unrestricted vibe coding after real-world pitfalls: security risks, tech debt, and unmaintainable code
Companies are pulling back from unrestricted vibe coding after real-world pitfalls: security risks, tech debt, and unmaintainable code
after watching my son attempt to vibe code for ~15 hours, I am more convinced than ever hard skills are going to be needed
Frontend: Vue Backend: Laravel (90%), NestJS (10%) Database: MySQL & Postgres
Frontend: Livewire Backend: Laravel Database: SQLite
If you are into tech, AI or programming say hi and lets #CONNECT. #programming #AI #Coding #dev
United States Trends
- 1. Ravens 59.9K posts
- 2. Ravens 59.9K posts
- 3. Drake Maye 24.6K posts
- 4. Lamar 27.7K posts
- 5. Derrick Henry 9,596 posts
- 6. Zay Flowers 7,600 posts
- 7. Harbaugh 10.2K posts
- 8. Pats 15K posts
- 9. Steelers 83.7K posts
- 10. Mark Andrews 4,956 posts
- 11. Tyler Huntley 2,110 posts
- 12. Diggs 12K posts
- 13. Marlon Humphrey 1,953 posts
- 14. Kyle Williams 2,267 posts
- 15. 60 Minutes 52.1K posts
- 16. Lions 89.3K posts
- 17. Westbrook 4,482 posts
- 18. Bari Weiss 43.5K posts
- 19. Henderson 13.5K posts
- 20. Boutte 2,231 posts
Something went wrong.
Something went wrong.