Fizuli Valizada

Recruiting software engineers can be easy as pie. (Guess what I made this weekend btw) But a lot of the time it’s the opposite. 🤦🏻‍♂️Unrealistic expectations 🤦🏻‍♂️Stakeholders not on the same page 🤦🏻‍♂️Long interview processes 🤦🏻‍♂️Taking too long to make decisions 🤦🏻‍♂️Not investing enough time into a search 🤦🏻‍♂️Being too reliant on direct applicants 🤦🏻‍♂️Partnering with the wrong agency We try to make things simple at 💚🖤Bounce Digital💚🖤 But if you’re not willing to change your approach Hiring engineering talent might just be pie in the sky 🥧 *Excuse the terrible puns. 

12

Here is a migration guide for anyone who wants to try Kotlin 2.0 - I tried it, my only issue was kapt plugin not being compatible with Kotlin 2.0, forcing me to use ksp in it's place. However, Kapt will be updated to work with Kotlin 2.0 in the future. Other than that, migrating to K2 worked fine for me: https://lnkd.in/dyxSatEH

3

*Bracing myself for the response I might get for asking this* Software Engineers: Would you ever consider working on an EQUITY ONLY basis (ie no salary, just owning a portion of the business, the value of which would increase as it progresses and scales)? Assuming: - The product is really interesting and so is the work - The product is in the "tech for good" space and would be a really positive contribution to parts of society - Seed funding is confirmed to be coming with several backers keen & they will able to offer a salary in the near future - The product is super early stage, you would be writing the software from the ground up, but the concept, design and business model once funding is received are all solid I know that there will be many who would never consider this under any circumstances and I totally get why, but just curious to hear if any of you would if it was for a product you believed in enough? And would you look at it on a full-time basis or a part-time basis? It's something I got asked about and so I thought I would throw it out to Linkedin to see what you all think rather than assuming that I know the answer on your behalf. #startup #founder #softwareengineer

40

309 Comments

A fascinating post by Ryan Murphy and a great read for some of those more 'technical' Product Managers on the evolution of Product and Software. As time goes by I see more roles where the lines between traditional Product and Engineering seem to blur... Systems Analyst turn Business Analysts to Product to Engineering..the variety of career paths available now are extensive depending on interest and expertise. Will we see more hybrid roles emerge with AI and ML advancements? How could these changes shift the skills that are in demand by employers?  🤔 Go check it out you haven't already 👇 #product #engineering #futurecareers

2

Check out my latest articles on TheServerSide! I've been sharing insights on newer stuff on Java. Give them a read and let me know what you think. #TheServerSide #Java https://lnkd.in/gXEN588N

26

1 Comment

🔥🔥🔥amazing software engineering posts from the past week🔥🔥🔥 Ryan Murphy rejection means only that: rejection. Keep going. https://lnkd.in/ecfy5tBV Tiger Abrodi consistently posting TypeScript knowledge bombs https://lnkd.in/ebeapvQ9 Taha Hussain are you fueling the micromanager in your life?? https://lnkd.in/eFtrhiHN Eric Roby please keep your processes simple! your success depends on it! https://lnkd.in/epk7Q_qJ Owain Lewis principles for a delegation: I needed this 2 years ago. https://lnkd.in/eNvt564u Pramoda Vyasarao master the basics https://lnkd.in/eMKTMesj Matt Watson new, "exciting" and complex tech excites only one person: the person who uses it to build. long term success needs tech that is boring, known and comes with a talent pool. https://lnkd.in/e8aK9aQt Austin Belcak above average results require above average effort. Go the extra mile - the road is never crowded. https://lnkd.in/edWQGDPH Francis Nayan take. action. today! https://lnkd.in/ej-HbcpJ Callie Buruchara 7 principles for giving feedback. it's easy to see that Callie is leading from experience! https://lnkd.in/e9XXnDyq

29

Google Announces its official support for Kotlin Multiplatform! 📱 They have stated that they are implementing it in their Google Docs app for iOS and Android and that they plan to use it in other workspace apps too. What does this mean for Flutter? 😬 Check out the article in the comments for some more details. #kotlinmultiplatform #iOS #Android #crossplatform

51

8 Comments

Think you’re unqualified for the work you do? It’s called #imposter #syndrome and we are here to help you UAE | MENA Software Engineers & QA Telegram Link: https://lnkd.in/e4twPVff To be honest, you never really will be an expert in software development. There will always be more to learn. There will always be new #languages, or #processes, or #technologies to learn. There will always be someone who knows something you don’t. There will always be someone who knows more than you do. There will always be someone who’s a better developer. That thought may be depressing right now, but I feel it’s actually liberating. You can focus on getting better and growing. Focus on what you can control: your #skills and your #knowledge. Accept that there will never be a point where you’ll feel completely knowledgeable and completely comfortable. Embrace your ignorance and use that to fuel your growth #impostersyndrome #wecanhelp #readytohelp #letstalk #askmehow #icanhelp #letsworktogether #areyouready

6

Hello 👋🏽 I’ve put together an article outlining alternative methods to achieve the same result when we don't use certain extension functions within Kotlin Collections. Given the importance of collections, I wanted to highlight these options. I’d love it if you could take a look and provide feedback. Your input is valuable, and thank you in advance! Enjoy the read! 😉 Let me know if there's anything unclear or if you'd like a deeper dive into any part. medium link: https://lnkd.in/dqj9tQuv github link: https://lnkd.in/dzAHCUDc #Android #Kotlin #KotlinCollections #AndroidDeveloper #Mobile

18

As an OSS maintainer I often receive long lists of feature requests My first response to these now is always to ask people to cut a branch and start working on an item from their list If you're not willing to start working on it, it's probably not that important #opensource #software #development

4

If you're used to writing tests in a traditional "unit" style where your tests are mock-heavy and test implementation details, it's no wonder you probably think TDD doesn't work well. TDD works beautifully when tests are written against behaviours and not implementation details. Your tests will actually help you make changes over time in this scenario. When your tests test internals and are very mock-heavy, TDD becomes slow and painful, as does testing in general. If every time you refactor internals you have to change loads of tests, and your tests are a pain to maintain, it might be time to reconsider how you're writing them. I don't even use the term "unit" day to day because I think tests written this way cause nothing but harm. Test against behaviour all the way through the stack and your tests will help you.

372

152 Comments

For the aspiring software engineers out there (assuming that profession still exists :), this article provides some great insights into how to think about a typical coding interview problem. https://lnkd.in/eB_Zw2D7

50

6 Comments

Are you curious about how top-notch development teams across the globe are leveraging the power of 𝗞𝗼𝘁𝗹𝗶𝗻 𝗠𝘂𝗹𝘁𝗶𝗽𝗹𝗮𝘁𝗳𝗼𝗿𝗺? JetBrains has got some incredible 𝗞𝗠𝗣 case studies. You can find out more here #google #jetbrains #android #kotlin #compose #kmp

31

1 Comment

Don’t hire a software development company until you’ve asked (and answered) these 4 questions: 1. Are we working with experts? This is obvious. It’s important to establish whether the company has the expertise you’re looking for. It’s common at bigger consultancies for one senior engineer to be managing a slew of junior engineers with little experience. This is why qualifying expertise is important. Codingscape hires senior engineers and staffs them on small teams so that their focus is entirely on the client. This ensures exceptional service delivery. 2. Will we have direct access to the team? You don’t want to work with a consultancy that will give you proxies, translators, or project managers. You want to communicate with the technical people who are working to solve your problem. Not only does it make it easy to understand what progress is being made, but it also helps the project get started quickly. If you have direct access to the technical team, you can hear straight from the experts how much things will cost and what the timeline will likely be. 3. Is the development team working on more than one project at a time? If the team is working on multiple projects, they’re not focusing their complete attention on you. You don’t want that as a client. Codingscape specifically tasks teams with just one project so they can focus entirely on understanding the client’s problem and delivering a cohesive solution. 4. Does the company want to be our partner and see us succeed? This may sound silly: why wouldn’t the company want you to succeed? Well, many consultancies care only about fulfilling the letter of the contract. They don’t: - Proactively communicate with the client - Practice transparency with progress and results - Build trust through accountability Ultimately, the right dev company is one where you come out of a meeting thinking: “Wow, this company really cares about our project and what it means for our business. I can tell they want to help and that they have the experience to make the best solution.” If you qualify a software development company using these 4 questions, you’ll be closer to finding the right match for your business.

19

3 Comments

How did it go when you switched from cloud to on prem, reduced cloud bill by 50% but increased engineering team costs by 200%? Not to mention the new range of potential incidents you're now exposed to. #onprem #cloud #aws #azure

46

14 Comments

Struggling to land a job as a Software Engineer with 0-3 years experience? Here's how to shoot to the VERY top of the pile: I won't BS you, the junior market is brutal right now. There's very few roles, and I've been hearing stories of adverts getting over 1000 applicants... So how do you stand out? The truth is, out of those 1000 applications, only 20% will be in Australia, and only 20% of those will be software engineers. That's 40 people. No hiring manager wants to interview 40 people. Especially when very few of those 40 will have the right communication skills, attitude and aptitude to get through the interview process. In fact, 99% of hiring managers would prefer to interview just 1 person. Do this, and that 1 person could be you: - Prepare some personal projects (to show willingness to develop skills) - Do some research on the company (to prove genuine interest) - Practice communicating (poor communicators fail interviews) - Apply with CV + personal project links (so you can be found easily) - Identify specifically why you are a good fit (if you don't know, nobody will) And then - CALL THE HIRING MANAGER. Or video message. Or voice note. In 30 seconds you can: - Introduce yourself and say that you've applied - Reference the personal projects on your CV - Mention why you like the company and why you'd be a great hire - Give availability to discuss the role further in an interview - All whilst proving you are a strong communicator with a great attitude Do this well and you'll be a 1/1000 candidate, I promise you.

45

3 Comments

Ever wondered how your favorite apps communicate? 💡 Let's talk about APIs. API = Application Programming Interface. Here's a simple analogy: You're at a restaurant. → You = Customer 🍽️ → Kitchen = System → Waiter = API 🧑‍🍳 You order through the waiter. The waiter tells the kitchen your order. The kitchen prepares it, and the waiter brings it back. APIs work the same way: 1. Request → You make a request via app/website. 2. Processing → API receives and interacts with the system. 3. Response → System processes and sends back results. 4. Delivery → API delivers results to you. Why care? APIs simplify complex processes. 🔄 → Booking a flight? ↳ APIs connect to airline systems. ✈️ → Checking the weather? ↳ APIs fetch data from weather services. APIs are tech's secret heroes. For Veterans in IT, mastering APIs is key. → Boosts your technical skills. → Essential for software, data roles. → Valuable in business consultancy. Remember the API magic next time you use an app. ✨ Questions about APIs or IT transition? Drop them in the comments! 💬 #USArmy #SignalCorps #MilitaryTransition #SoftwareEngineering #ITOperations #DataAnalytics #InformationTechnology #VeteranJobs #MilitaryCommunity #CareerDevelopment #Networking #ArmyStrong #DigitalTransformation #VeteranHiring #TechJobs #Opportunity #ServiceMembers #ProfessionalGrowth #LinkedInNetworking #VeteranSupport #ArmyVeterans #YouGotThis #YouGotThis #fdmcareers #fdmvets #fdm #usmilitary #usarmy #usaf #airforce #airforceveteran #navyveteran #navylife #navy #marines #usmc #usmarines #nationalguard #reserves #fdm #fdmcareers #fdm 

20

1 Comment

Programming tests are: ❌ Often stressful ❌ Take-home tests are usually time-consuming ❌ Rarely representative of the approach and conditions of the job that they're testing for ❌ Many times online code testing platforms will penalise you for clicking away from the screen and sometimes they penalise you for any copying and pasting ❌ Usually theoretical "best practice" based - showing how you might do something if you were working in a vacuum, not accounting for business needs / interdependencies with legacy platforms etc ❌ Typically they favour those who have more recently come from education over more seasoned professionals ❌ In some cases the results are ignored or overlooked anyway if the candidate has done well enough in interviews rendering the test itself pointless ❌ In other cases companies take a "line in the sand", "computer says no" approach where even someone who is a known entity to the team or business will be rejected if they don't do well enough on the test   I have NEVER heard a developer say that they enjoy technical tests.   Some of the most senior, capable, accomplished developers I have worked with refuse to complete them as part of a process - particularly timed ones.   How often do you write code in a real life production environment with a timer counting down? And when would you ever want your team to not have access to Google or GitHub or Stack Overflow on a difficult task? A significant part of an Engineer's role is to research potential solutions critically, not to be a walking programming encyclopedia!   Even if your test is a less pressured, more representative take-home task rather than a recorded or monitored time-pressured task, they're not always that informative and they often take up a large chunk of time, which, particularly for someone who is currently in full-time employment and interviewing for multiple other opportunities, is a lot to ask. They also often lead to excellent candidates withdrawing from the process.   To quote a senior dev I spoke to the other day: "It doesn't matter how great the pay or the company or the work are. I'm a professional with over 10 years' experience, treat me like it. Don't set me bullsh1t homework"     👉 So why is it that so many interview processes use them? 👉 And what are the genuine legitimate alternative approaches to be able to ascertain someone's technical capability?   Keen to hear your thoughts Linkedin? Futura Talent #technicaltesting #techrecruitment #developerlife #softwaredeveloper #softwareengineer

8

2 Comments

We’ve spent the last couple of weeks filtering down over 90 applications for our software engineering roles so here’s some of the good practice I’ve seen: 👉take the time to create a good quality application. When there are so many candidates looking, it is much better use your time doing fewer applications well than spamming lots of roles in the hope that something sticks. 👉 if they are asking for x-years experience in something (or another key criteria) make sure it’s easy to see that you have it (or clearly explain why you think you have the equivalent in your cover letter). When there are so many candidates there isn’t time to deconstruct all the experience in someone’s cv in case they fit. 👉 write a cover letter explaining why you want the role and how you fit (or could grow to fit). Every cover letter I read gave me more depth into the candidate and helped me understand what they would bring to the role. 👉 use the layout to highlight the key skills you bring - it really doesn’t matter if it’s 1 page or 2 pages and whether you have columns or any other fancy bits - just make it easy for me to scan read. 👉the more you can quantify (with numbers) what you’ve done or the value you’ve delivered, the better. The numbers don’t have to be big - they just give me an idea of the size and scale of what you’ve been involved in. And finally, I know it’s tough getting a rejection but please don’t take it personally. I’ve seen some amazing applications come through, but they’ve just not been right for what we need. #jobapplications #careers #cvtips

23

1 Comment