Oiza B.’s Post

📌Pro tip for devs: Whenever you feel like you don't wanna code... Take a deep breath  Open your setup💻  and start working ⚒ After a few minutes, you'll hit your stride and make progress! Trust me, this is the best way to kill procrastination and get some real sh*t done!

Journey starts from 2019 to become a successful devloper

Read and Watch my Journey to becoming a Game and Software Dev! Chapter 9

Just finished my first week as a Full Stack Software Developer at Parq! Here's what I've learned so far: • 🧠 The ability to pick things up on the fly is perhaps more valuable than prior experience. You can't know everything, but if you can learn anything, you bring value immediately. • ⏩ Start-ups are fast-paced. Goals have to be identified, organized, prioritized, and met on time. Making that process a well-oiled machine is critical to success. • ⚙️ Create a hypothesis and test it. Keep that hypothesis in mind during the whole task in order to stay on target. • 💯 Presentation is everything. Doesn't matter if you're an engineer or a sales person -- a great product that looks terrible (or has a terrible demo) might as well be a bad product. • 🥪 Take a lunch break. Maybe a walk break too. Stepping away from a problem for a few minutes and coming back can give you a fresh perspective, getting you to a solution faster than banging your head against it when you're hungry. • 🦆 Talk through problems. Rubber duck debugging is real and it helps. (Better with a human, though) This first week at Parq has been full of great projects and great learning opportunities! Shoutout to Walker Ryan, our CEO, for his vision, drive, and passion for delivering epic products to customers. Shoutout to James White, our head engineer, for his amazing teaching ability, technical expertise, and level head when things get sticky.

If you want to see what the future of AI and DevSecOps holds, check out our recent LinkedIn Live. Fatima Sarah Khalid ✨ leads this great roundtable discussion.

Whether you are qualified to called as a Senior Dev from my point of view were: 1. You have full understanding of why we have this feature, who is using this feature, why it was built this way 2. You can point out a problem and propose a solution 3. You know what's the right time for a problem to fix and when it need to became priority 4. You won't hesitant to guide your junior to became like you, since you know one day you need someone to replace you in order for you to climb higher .... so on, anyone want to add more comment?

A question to all senior devs here📢 Share some of the greatest advice on what you think are important for Junior Devs to transition to a senior role.👇

Just finished a write-up about some common patterns I've used recently when joining new software development teams. If you check it out and have thoughts, let me know! Hit the Ground Running! Impress Your New Team by Tidying Builds

If I were to kickstart a new project today, TypeScript would unquestionably be my go-to choice! Its robust static typing, along with its ability to catch errors during development, significantly enhances code quality and developer productivity. I'd love to hear your thoughts on using TypeScript in modern software development! Let's connect and discuss our experiences with this amazing technology. 🔍🚀 #typescript

Goal of junior dev: minimize the chances of breaking something in the code. Goal of senior dev: minimize the chances of juniors breaking something in the code.