Muhammed Tijani’s Post

“Fake it until you make it”. What do those words mean to me? From the moment I decided I was going to be a software engineer, I thought of myself as a software engineer. And there were people who tried to convince me otherwise. And I never let them stop me. And there were people who would try to say to me “oh well when you become an engineer…” But I already knew that I was an engineer. I can’t explain it. From the moment I began to do it I just knew that it was what I was born to do. I was obsessed with it. I became obsessed with it very very fast. I was thinking about it 24/7. I watched videos about it all the time, when I wasn’t doing it, and so I sussed out the big picture of the field pretty fast. I did every single thing that was available to me in my power, did everything that I possibly could. Now, I can build things. I can build things for real. I can pick up new technologies and new languages very quickly. But for me engineering was never something that I was trying out - well okay yes it was. For two months. But after that, I knew. When you know. And so for me there was no fake it til you make it. There was only: when you know, you know. And from two months of coding: I knew. And knowing, and being sure of myself, and having that inner self-assurance, has made all the difference. It has helped me to get hired really fast. It has helped me not to lose hope and to retrain when I lost my job (and by retrain I mean up skill and learn a new tech stack relevant to roles that interest me). And it has allowed me to blog and write about the process - never pretending to be more than I was - just doing what I was really doing and writing about what I really knew. Because for me there was never really any “fake it til you make it”. There was only “when you know, you know.” When you know, you know. ❤️ and what do you know you know? ❤️💙 #softwareengineering #softwareengineer

The Three-Mountain Journey of a Software Engineer: From Novice to Expert 🏔 Embark on a journey through the three critical stages of a software engineer's career: from landing your first job to becoming a 10x engineer. Let's explore these milestones together. Mountain #1: Landing Your First Job 𝐓𝐡𝐞 𝐂𝐡𝐚𝐥𝐥𝐞𝐧𝐠𝐞: Many engineers find this initial climb daunting, as there are numerous paths to the summit. 𝗣𝗮𝘁𝗵𝘀 𝘁𝗼 𝗦𝘂𝗰𝗰𝗲𝘀𝘀: Some secure their first role armed with a degree from a reputable university. Others take a more hands-on approach, coding their way into their inaugural position. 𝗞𝗲𝘆 𝗧𝗮𝗸𝗲𝗮𝘄𝗮𝘆: Flexibility and perseverance are your allies here. Mountain #2: Ascending to Senior Engineer 𝗠𝗶𝘀𝗰𝗼𝗻𝗰𝗲𝗽𝘁𝗶𝗼𝗻𝘀: The title "Senior Software Engineer" often gets mistaken for true seniority. 𝗧𝗿𝘂𝗲 𝗦𝗲𝗻𝗶𝗼𝗿𝗶𝘁𝘆 𝗜𝗻𝘃𝗼𝗹𝘃𝗲𝘀: 1. Effective team communication. 2. Leading feature development. 3. A deep understanding of the business, recognizing coding as a means to an end. 𝗜𝗻𝘀𝗶𝗴𝗵𝘁: It's about impact, not just tenure. 𝗣𝗲𝗿𝘀𝗼𝗻𝗮𝗹 𝗡𝗼𝘁𝗲: I am currently trying to conquer this second mountain, continually striving to expand my skills and impact. Mountain #3: The 10x Engineer Summit 𝗧𝗵𝗲 𝗠𝘆𝘁𝗵: Becoming a "10x engineer" (outperforming peers tenfold) is often dismissed as unattainable. 𝗥𝗲𝗮𝗹𝗶𝘁𝘆 𝗼𝗳 𝟭𝟬𝘅: It's less about coding volume and speed, and more about leverage. Paths to 10x Impact: 1. 𝘿𝙚𝙥𝙩𝙝-𝙛𝙞𝙧𝙨𝙩: Mastering your field to solve critical organizational challenges. 2. 𝘽𝙧𝙚𝙖𝙙𝙩𝙝-𝙛𝙞𝙧𝙨𝙩: Amplifying your team's productivity and output. I'd love to hear from you: What has your journey looked like? Which mountain did you find most challenging, and why? #softwareengineering #careerdevelopment #professionalgrowth

You don't need experience to be a successful Software Engineer. Period. With 15+ years of experience, 20+ successful products, 5+ rating; I can vouch that "there's more to being a successful software engineer than just years of experience." And this may break your central belief that Experience Matters. But all we have been fed with is half truth or complete lie. And here are 3 things you need to focus to be a successful engineer: 1. Obsess over new learnings ➡️ The best way to learn is to build a network, work on open-source projects, explore about new frameworks and languages 2. Master the craft, not just code ➡️ Perceive code as art. Write code that’s maintainable, clean, and readable. 3. Include empathy in your skill stack ➡️ Approach problems from user might, different angles, experiment and then iterate. I call them “Engineer Traits” and hire engineers for Jalan Technologies that fit this list. Of course, experience is on the list too but a lot down on the priority list. Which traits do you look for in a successful software engineer? #softwareengineer

🚀 Calling all aspiring software engineers! 🚀 🔍 Want to excel in the tech industry? It's not just about code anymore. Understanding business needs and connecting with clients are crucial skills every software engineer should master. 💼💻 👩💼 As someone who's been in the field for a couple of years, I can tell you firsthand: the ability to bridge the gap between tech and business is what sets exceptional engineers apart. It's not just about writing flawless code; it's about solving real-world problems and delivering value to clients. 💡 💡 So, if you're aiming to be more than just a code ninja, start honing your business acumen and communication skills. Understand the client's perspective, empathize with their needs, and tailor your solutions accordingly. Trust me, it'll take your career to new heights! 🌟 👍 Hit like if you agree, and let's empower the next generation of tech leaders together! 💪 #TechLeadership #BusinessAcumen #ClientFocused #SoftwareEngineeringSuccess

Agree. A senior - to me - is nothing more than a safe pair of hands. Somebody with the experience to know when a thing will work, when it will not work, what things to try next, how to rogrniase work and code, how to get a whole product into a user's hands. They know what to try next - when they don;t know what to do next. You can't do that after reading a few books. I read loads of books. I couldn't do it at that point. You need to apply those ideas, reflect on where they fail and why, then continuously put that into your future work. You have to move away from Inidividual Contributor thinking and "but the code works fine" thinking. It takes time, but not just time. Time alone changes nothing. Ask a cup of cold water. But time allows us to explore, expand and experiment. If we do that with mindfulness, we will improve.

Recently, I have seen some posts talking about seniority in software engineering. Some of them stated that it is possible to be a senior software engineer in months, like 20 months or something just by reading a certain number of books and writing a certain number of blog posts. I don't agree with that, reading books and writing blog posts is good but the thing I think matters is practice, applying what we learned to solve different problems we face. On the other hand, some of those posts stated that having x years of experience doesn't make you a senior software engineer, I agree with that. In my opinion, we shouldn't consider all the number of years as real experience if we are solving the same problems in the same way every year. I believe that experience comes from continuously exposing ourselves to different problems that have higher complexity. #softwareengineering #seniorsoftwareengineer #growth #experience

🚀 Career Advice for Aspiring Software Engineers🚀 Hey everyone! 👋 As a software engineer with , I've learned a few things along the way that I'd love to share with those of you who are just starting out or looking to advance in your careers. 1. Never Stop Learning: The tech industry moves at lightning speed, so it's crucial to continuously expand your skill set and stay up-to-date with the latest technologies and trends. 2. Embrace Challenges: Software engineering is all about problem-solving. Don't be afraid to tackle challenging projects or dive into unfamiliar technologies. Each challenge is an opportunity for growth. 3. Build a Strong Foundation: Focus on mastering the fundamentals of computer science and software engineering principles. A strong foundation will serve as a solid framework for your career and enable you to adapt to new technologies more easily. 4. Seek Mentorship: Don't hesitate to seek guidance from experienced professionals in the field. Mentorship can provide invaluable insights, advice, and support as you navigate your career path. 5. Collaborate and Communicate: Software engineering is rarely a solo endeavor. Learn to work effectively in teams, communicate your ideas clearly, and collaborate with colleagues from diverse backgrounds. 6. Stay Agile and Adaptive: The ability to adapt to change is essential in the ever-evolving world of software development. Embrace agile methodologies and be open to feedback and iteration. 7. Build a Strong Network: Networking is key to advancing your career in tech. Attend industry events, participate in online communities, and connect with professionals who share your interests and goals. 8. Follow Your Passions: Pursue projects and opportunities that align with your passions and interests. Whether it's open-source contributions, side projects, or specialized areas of expertise, follow your curiosity and enthusiasm. Remember, your journey as a software engineer is unique to you. Stay curious, stay hungry for knowledge, and never stop striving for excellence in everything you do. Your future in tech is bright! ✨ #SoftwareEngineering #CareerAdvice #TechTips #CodingLife #ProfessionalDevelopment

🚀 To the Aspiring Software Engineers: Embrace the Leap of Faith 🚀 Remember the first time you had to reach out to a colleague you hadn't met? If your heart raced at the thought of being a bother, you're not alone. My journey from those early days of hesitation to becoming a Software Engineer has taught me a valuable lesson: our community is overwhelmingly welcoming. A recent chat with a newcomer, anxious about her initial one-on-one interactions, took me down memory lane. It's a common feeling, that mix of excitement and nervousness, when you're about to step into the collaborative world of tech. Here's the heartening reality I've discovered: nearly everyone is approachable and willing to lend a hand. It's a testament to the supportive backbone of our industry. When you're on the receiving end, think about it – wouldn't you step forward with a smile to help? So, to every junior engineer standing at the crossroads of uncertainty and ambition: let your spirit be fearless! The tech community thrives on collaboration and mentorship. Your questions and contributions fuel our collective growth. Dive in, unblock your path, and remember – we've all been in your shoes. The first step might be daunting, but it leads to a journey of endless learning and connections. Let's move fast and break barriers together. Your voice adds value, and your courage to ask is the first step toward mastering the art of software engineering. #softwareengineering #techCommunity #professionalGrowth #beBrave #collaboration #JuniorEngineers #TechMentorship #SoftwareEngineering #CareerGrowth #OpenDoors

"How to evolve as a Software Engineer" Excited to share some key tips on how to advance your career as a Software Engineer: * Stay Curious: Embrace lifelong learning and continuously update your skills. * Network Effectively: Build relationships and learn from others in the industry. * Develop Problem-Solving Skills: Strengthen your ability to think critically and strategically. * Seek Feedback: Be open to constructive criticism to improve your work. Ready to take your software engineering career to the next level? Let's connect and learn from each other. 🔗 #SoftwareEngineering #CareerGrowth #ProfessionalDevelopment 💡🚀 Remember, the growth of a software engineer is fueled by constant learning and collaboration. Let's journey towards excellence together! Like, comment, and share your thoughts below.

I haven’t screamed it enough from the rooftops today so here it is! I love software engineering. I love the way it feels when I have written a piece of code and it is in production. Wow! Nothing feels better than that. I love the camaraderie and friendship that there is in software engineering. I love how caring and kind software engineers are. I love how far out of their way they go to accommodate me with my neurodiversity - never seen a group do better at that for me at work than software engineers do. I love how it feels to build a feature. Can you imagine that? To take something and then be told to built it and then you write some code and then your feature exists. I mean - wow. At the moment one of the biggest things I’m thinking about is how do I translate a feature into working code. 👩💻 I am thinking about - how do I do the investigation for a feature that needs to be done 👩💻 I am thinking about - how do I own the product technically and push back on this when this is required. Because it is about so much more than just coding courses. Because software engineering is not just about who can write the best code. It is about owning a product from start to finish. It is thinking about technical implementation and what tools can I use to make this product feature a reality and how can I translate this into steps. Lots and lots of small steps. Always smaller and smaller steps. Right down to the smallest steps of the code. And I have an amazing post coming on this soon. It’s all about breaking things down. And above all being a software engineer is all about self reflection. And I will maintain this to the very end. I maintain this is a great way to get hired. Is to be able to self reflect really well. Because your self reflection journey never ends as a software engineer. You could always do everything better. Your code could always be better. And everyone will always have opinions on you and your code. And you have to be open to those opnions. And you have to be open to everybody. Because everybody is only ever just trying to help. Btw - I first started to love editing photos of myself and others into unusual and high contrast settings when I was 15. So great to have found this again. This passion. - Thanks! x #softwareengineer