Comment below or send me a DM and I'll pop it over! ๐ช๐พ (5/5)
@juliansequeira
I lift people up! ๐ https://pybit.es/ ๐ https://www.linkedin.com/in/juliansequeira/ ๐๏ธ www.pybitespodcast.com โถ๏ธ youtube.com/c/pybites ๐๐พ Co-Founder of Pybites ๐ฅธ Aussie Dad and Dad joke enthusiast ๐จ๏ธ 3D Printer Novice ๐งช Homelabber ๐ฅ PC Gamer
Comment below or send me a DM and I'll pop it over! ๐ช๐พ (5/5)
Once you're able to consistently spend time on your learning every day, then go dive into the next technology. You need to set yourself up for success. I created a guide with 7 other habits of Senior Devs that will help you regardless of your level. (4/5)
Pair that with learning the things that will actually get you to your goal - that's where you want to be. For those of you wondering what to do next this year, my recommendation is this: looks into and improve your habits. (3/5)
There's always going to be more technologies to learn, but the methodology you use to learn them will be the same. Today it's LLMs, tomorrow it'll be something else. Putting aside 30 or 60 minutes a day to learn and to build is timeless. (2/5)
The tech industry is moving incredibly quickly these days. I can see why people are struggling to keep up or know what to focus on next. This is why I like to differentiate the tech learning from the systems. (1/5)
We're all incredibly proud of you ๐ฅณ (6/6)
It wasn't easy, but watching you persist through hurdle after hurdle, never giving up, and finally reaching the goal has been a privilege. You put in the reps, you worked the late nights, you built the projects, and you earned every part of this! (5/6)
Breaking into the tech industry is hard, especially these days, so I was chuffed when she shared the news she'd accepted an offer as a Systems Developer in the Regional Public Sector (Sweden). You had one hell of a 2025, Sherry. (4/6)
Behind the scenes though, Sherry has been grinding, working toward her first tech role. Much of her time beyond managing the community has been spent relentlessly upskilling, building and refactoring software, and pushing her technical boundaries. (3/6)
She is always the first person to welcome new members and cheer on their wins. She has a knack for keeping the energy high when things can feel low and will make time for everyone and anyone. (2/6)
A special and overdue post today! Huge congratulations to our very own Sherry Andrews Bhutia for landing her first professional tech role! ๐ Many of you know Sherry as the heart and soul of the Pybites Community. (1/6)
You need to be able to prove you can use AI efficiently and that you know your way around your coding language. The tools change, but the need for experts in their craft remains. Keen to hear your thoughts! (7/7)
It may not be ideal for those that want the pure coding experience but with so many companies wanting you to have "AI skills", now isn't the time to be a hold-out. NOW is the time to be investing in building your skills, experience and portfolio. (6/7)
The good thing is that to be able to have these insights, you have to keep your skills sharp. You still need to know how to code! (5/7)
They're the ones positioning themselves as the Architects and Auditors/Code Reviewers. They're the ones who can look at AI output and say: "Yes, that runs, but here's why it won't scale." Or: "That looks clean, but it introduces a security vulnerability in <x>". (4/7)
Even with this risk though, AI and LLMs are seemingly here to stay (Amazon's betting on it - see that announcement last week? Phew!) So, where does that leave us devs? Well, the developers that I see succeeding right now aren't the ones trying to out-type the AI. (3/7)
But I believe we're starting to see a shift in what the market values. As AI generates more buggy, unscalable and insecure code I think the value of humans is going to go back up. (2/7)
I was thinking a lot on the weekend about the whole Vibe Coding thing (not sorry for bringing it up again!) AI and LLMs can be such tempting tools, right? The speed is addictive and makes you feel like you're doing the work of 5x developers at once. It's intoxicating! (1/7)
๐ง Listen here: https://pybit.es/articles/building-useful-ai-with-asif-pinjari/
Our chat is a nice example of moving from a Student Mindset (getting code to run) to and Engineer Mindset (solving the business constraint). Thanks again for joining me Asif! I can't wait to see how far this building takes you! (6/6)
He reminded me that the real Engineering in AI right now is about building the safe, reliable, and private infrastructure around models so businesses can actually use them. (5/6)
Asif is engineering local, LLM solutions because he realised his clients (real businesses) are terrified of sending their data to public LLMs. (4/6)
I often see developers building cool looking AI tools that call the OpenAI API which is a great start, but Asif pointed out why so many of these fail in the real world: Privacy. (3/6)
Asif is BUILDING. He's taking what he's learning both in university and out and building things that actually help businesses. (2/6)
One of the best conversations I had in January was with a university student and teaching assistant from Arizona ๐คฉ Usually, when I talk to students, we discuss coding, exams, landing their first internship, etc. My chat with Asif P was different though. (1/6)
You get your solo time to code, as well as time to interact with the other devs in your group. The feedback we're getting on these cohorts is incredible. When you're tired of going it alone, check them out here:
https://pybitescoaching.com/ (7/7)
So as enjoyable as the loud music, dark room and day-long coding sessions, are, it's the moments where you interact with other devs that'll get you to the Senior Dev level you seek. And this is EXACTLY why we created our Python + Rust cohorts. (6/7)
Don't get me started actually) When you have people challenging your logic and asking you to explain why you built something a specific way, you immediately grow as a developer. (5/7)
It creates much needed FRICTION when you have people critiquing your work. (Companies do this all the time: doc reads anyone? (4/7)
You wind up in an echo chamber of your own bad habits and biases. If there's no one to tell you your code could be improved, how else are you supposed to know you have gaps? I really believe that coding with people creates a faster path to success as a developer. (3/7)