Isaac Scarrott

What is a TypeScript Engineer? I keep seeing this pop up in recruitment posts, which means clients are asking for it...right? Has this replaced the FullStack Engineer, which, lets be honest, meant a NodeJS developer. That was back in the good old days when it was only NodeJS. Now we have Bun, Deno, Hono and more. Or perhaps its asking for a Javascript developer...whatever that means in todays world of a thousand js frameworks and evolving ES standards. Or are they actually asking for a Java developer, because someones used Gen AI along the way and it got confused between Java and Javascript (*shudders*) Are they seriously in need of a type system engineer, thats kinda niche. It's hard enough trying to explain what you do as a job to "normal" folk as it is, without this level of obfuscation. How would you even explain this when asked "What do you do?". Do kids nowadays needs to consider themselves experts in everything inside package.json to land a job? When will the industry move beyond this fixation on specific languages? I get it, it's an important consideration, but asking for Typescript Engineers...it's not going to help you find the devs you actually need.

14

7 Comments

Ever thought about how API development can transform your career? Veterans, this is for you. 🎖️ API development isn't just tech jargon; it's a gateway to endless IT opportunities. 🚀 Here's your roadmap: **Understand the Basics:** - APIs (Application Programming Interfaces) let software systems communicate. - Think of them as digital bridges. 🌉 **Leverage Your Military Skills:** - Attention to detail? Perfect for debugging. - Problem-solving under pressure? Ideal for troubleshooting. - Discipline? Great for clean, efficient code. **Get Hands-On Experience:** - Join our Skills Lab. - Work on real projects. - Learn from experts familiar with the military-to-tech transition. **Continuous Learning:** - Tech evolves fast. ⚙️ - Stay updated on new API standards and tools. - Attend webinars, read blogs, and join coding challenges. **Build a Portfolio:** - Showcase your projects. - Document your learning journey. - Highlight your unique military experience. **Network:** - Connect with fellow veterans in tech. - Join online communities. - Attend industry events and meetups. - Leverage LinkedIn. **Seek Mentorship:** - Our Veterans Career Program offers personalized coaching. - Get guidance from those who have transitioned successfully. - Enjoy ongoing support. 👐 Transitioning to tech isn't starting from scratch. Your military skills set you apart. Ready to dive into API development? Comment 'API' below to get started! #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

2

Is your coding challenge costing you the best developers? Picture this: A brilliant developer, perfect for your team, closes your coding test tab... and never looks back. Ouch. Feels like a missed opportunity, doesn't it? Here's the kicker: 58% of developers say they've abandoned an application due to an unfair coding challenge, according to a 2023 Stack Overflow survey. That's more than half of your potential dream team... gone. But why? Aren't coding challenges the gold standard for assessing tech talent? Not quite. Let's break it down: • Time constraints stress out even the best coders • Generic problems don't reflect real-world scenarios • Anxiety can cloud true abilities • One-size-fits-all approaches ignore diverse skill sets The result? You might be filtering out innovative problem-solvers who don't perform well under artificial pressure. So, what's the alternative? 🔹 Take-home projects that mimic real work 🔹 Pair programming sessions 🔹 Code review discussions 🔹 Portfolio assessments Remember: You're not just testing coding skills. You're evaluating a potential team member. How do you assess technical skills in your hiring process? Share your approach! Let's build better hiring practices together. #TechHiring #SoftwareDevelopment #RecruitmentStrategy #CodingChallenges #TalentAcquisition

39

15 Comments

Back with another #KirstysKotlinFacts ! 💡 Last week I spoke about the misconception that Google was the original creator of Kotlin. Here's another misconception. Kotlin was created for Android. Wrong. Kotlin was always designed with the intention to be used for server-side backend development, it just so happens that it's also good for mobile development. The push for mobile actually came from developers themselves. The already existing mobile language #Swift by Apple was not working quite as well as hoped/needed, so the community requested it in need of a better language for android. Android became their priority in 2014. So, despite the initial purpose of creation, nowadays if you tell someone you're a Kotlin developer, more often than not, they will assume that you're an android developer since Kotlin is now more widely known for its android use. Would you also make this assumption if someone told you they were a Kotlin developer? #Kotlin #Android #Backend #SoftwareDevelopment

11

Interesting Monday read in the latest Stack Overflow Developer Survey where 80% of developers reported job dissatisfaction. 😒 Key factors include declining salaries, increasing technical debt, workplace bureaucracy, and unrealistic deadlines leading to burnout. 😴 Although AI tools enhance productivity for many developers, they often fall short in handling complex tasks. 🖥 Despite high pay and remote work opportunities, developers face stress from layoffs and sedentary work. 💰 Surprisingly, most still code as a hobby, indicating that coding isn't the main issue. 👨‍💻 Full article: https://lnkd.in/eapBcpBy

12

2 Comments

🔥🔥🔥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

The 5-Legged DevOps Engineer Does this scenario sound familiar? You've just finished an interview process, and instead of recommending yourself for the role, you find yourself suggesting that the client hire someone else. It's a situation that can be disheartening, but it's more common than you might think. 😓 A common theme and feedback from freelancers' other processes is that the client sought a Data Engineer. While both share skills, tech, cloud platforms, and automation tools. DevOps and Data Engineers have distinct disciplines with unique requirements and areas of expertise. ❌ I want to hear from my network. Is this a cost-saving exercise, potentially an untapped market, or an oversight in the hiring process?

8

6 Comments

🚨 JavaScript Contractor Pay Rates 🚨 Over the last 2 weeks I've spoken to 80+ JavaScript Engineers, who are all contractors, and are all highly skilled and experienced with React. They have other skills of course, but their core skill is React/Typescript. Below is a scatter graph of what they are getting paid right now in a contract role. I did this a couple of years ago and I remember there was a huge variety of rates regardless of experience, what I can see from below is that rates have stabilised massively, and people are now getting paid pretty consistently dependant on their level. It's good to see the market has stabilised and that people are getting paid what they are worth. If you feel you are getting paid below market rates, reach out and we can see what other opportunities I have for you. Or if you are looking to ramp up contingent staff quickly, and need to know what you should be paying, reach out. #JavaScript #TypeScript #React #Contractors #Sydney

26

5 Comments

DevOps is not a Job Title, it's a mindset/philosophy. This is how we will know if that debate has finally been won. The 390,000 DevOps Engineers on LinkedIn will change their job titles. Until that happens, sorry but it is a valid Job Title. (Even if I prefer SRE, Platform Engineer, Cloud Engineer, or Backend Developer.) #devops #sitereliabilityengineering #platformengineering #cloud

9

2 Comments

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

9/10 times, there is only one reason that developers fail their take-home tech tests - and it has the simplest solution. "Coding projects are a polarizing topic: some candidates love them while other candidates find them unfair. On one side, coding projects allow you to showcase your skills in a more natural environment, using the tools you love." Love them or hate them, they're a non-negotiable part of numerous development interview processes. I completely agree that these tech challenges should always be general tests so that applicants are not expected to provide free contributions to the client's platform, but there is one huge point missed in this article. TEST YOUR CODE! The most common feedback I’ve had for why a candidate has been unsuccessful with their tech challenge is “code does not compile”. If you’ve taken the time to complete a tech challenge, it is imperative that you check to see if it works. You may have spent 3 hours on it, maybe even longer; don’t skimp on Unit testing. https://lnkd.in/dP4Nd5u2

21

5 Comments

Enjoyed speaking to several developers over the last couple of weeks and finding out what's new in the JavaScript world. One thing I have noticed is the emergence of Vite.js 🚀 From doing more research it seems that Vite.js emphasises improving developer experience, application performance, and build optimisation, making it a compelling choice for React developers looking to modernise their projects. How does it do this? ⚡️ Lightning-Fast Performance - ite.js leverages the browser's native module system to serve dependencies on-demand, resulting in an unparalleled development experience. 🛠 Developer-Centric Workflow: Prioritising developer experience Vite has an built-in support for CSS preprocessors and seamless integration with popular tools like ESLint and Prettier. 🚀Built with modern JavaScript and leveraging tools like Vue.js, React, and TypeScript. Its compatibility with a wide range of tools and frameworks makes it a versatile choice for developers. What do you think of Vite.js? Is it something you're now using and seeing the benefits? I'd love to hear from you!

19

4 Comments

Frontend Developers, thoughts on Svelte? How does it compare to React? Is this a trend or can you see it becoming a leading JS framework? Keen to hear your thoughts. #Svelte #React #Frontend #technologies #javascript

26

43 Comments

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

👨‍💻This one’s for the software engineers, you’ve probably been there: staring at a tangled web of code that somehow manages to function despite it’s apparent chaos. It's not pretty, it's not perfect, but it gets the job done. 💡 Here's the thing: messy code isn't always a sign of incompetence. Sometimes it's a testament to the creativity and resourcefulness required to solve complex problems under tight deadlines. 😂 🔧 Sure, we all strive for clean, elegant solutions. But in the real world, deadlines loom, requirements shift, and sometimes you just have to roll up your sleeves and make it work, no matter how messy it gets. #code #softwareengineer #itworks

11

The average software developer stays at a company for around 𝐲𝐞𝐚𝐫𝐬 𝟐.𝟗, so let's talk about why that could be... There is an argument to be made about whether job hopping is good for your career in the long term or not. But the numbers are clear that job hopping can bring great financial benefits. While the average annual salary increase sits at 3%, you barely compensate for increased costs due to inflation. When changing jobs, a good salary increase ranges between 10 and 20%. If you care about increasing your salary quickly, then job hopping can make a big difference. Let's compare 3 different people starting annual salary of 40K The first never leaves their job, the second someone changes jobs every 3 years, and the third changes jobs every 18 months. To stay on the conservative side I have calculated every job change with only an 8% increase in salary. Over a period of 10.5 years, the financial situation of 3 employees has changed drastically. The loyal employee has increased their overall salary by 35%. But the employee that has been changing jobs every 3 years has an increase of 55% making 8K more. The job hopper has increased by a whopping 105%. So should you start job hopping? It depends! Ask yourself what you are looking for. If maximizing your income is the answer, then the answer is probably yes. But you may also be missing out on opportunities within the company you leave plus constantly trying to find a new team is can stressful!! You may also simply want to stay with the job, role, boss, team & company that you have found. I would suggest focusing on job opportunities that enable you to develop and grow professionally while increasing the level of responsibility you have. What do you think? #team #job #career #opportunities #jobopportunities #people #jobs #jobchange

19

3 Comments

I thought it might be fun to start a bit of a LinkedIn Challenge - to meet 100 Developers in 100 Days I've been a C#/.NET software developer for over 2 decades. I've actually been coding with the .NET Framework since one of its beta releases Post a comment of what your primary coding language is and how long you've been mastering your craft #softwaredevelopers #coders #100devsin100days #linkedinchallenge

2

All junior developer roles should come with a built-in apprenticeship. There solved the junior developer conundrum, you don’t want to hire them because they don’t have the experience you need so assign them as apprentices of a particular senior dev and watch them thrive or sink. Some will rise to the occasion and will produce great work for you and others won’t be able to keep up and you will get rid of them within 6 months under the guise of not meeting the requirements of the apprenticeship. This is not like an internship which is finite, an apprenticeship is an agreement between the company and the junior with requirements that need to be hit. It is a program, the cost is very low because their salaries are very low but they will quickly be productive as the apprenticeship progresses. I’ve been beating that drum for a while now, it’s tough for a business to hire a junior dev because money is tight and they need more things done. My debate is that if you only need senior developers, something is very wrong in your org (if it’s not a startup)

23

19 Comments

I'm sorry to break it to you 😞 A GitHub link may have been enough to secure an interview a few years ago but times have changed. CVs are being closely reviewed, and companies are demanding quality over quantity. It's time to delete Office 2003, and trim down the exhaustive list of every technology you've ever come across. Having recently connected with 100+ exceptional software engineers during a search for a leading European startup, I've noticed a clear pattern in what makes CVs stand out: 1) Impact matters more than ever! - Don't just list what you used - show how you shaped products - Highlight the "before and after" of your contributions - Quantify your achievements wherever possible 2) Showcase your achievements! - Led the migration that cut infrastructure costs by 40%? - Built and launched that critical feature used by millions? - Mentored junior developers into senior roles? - These are the stories that matter. 3) Personal achievements matter! - That side project you launched? Include it - Teaching yourself Mandarin? That shows dedication - Your top 1% ranking in competitive programming? Absolutely relevant The tech market is currently more competitive than we've seen in recent years. Don't let a poorly structured CV be the reason you miss out on your dream role. 💡 Need a template designed specifically to highlight these elements? Drop a comment or DM me - I can share a free CV template that's helping engineers showcase their true value. #SoftwareEngineering #Careers #Hiring #CVTips #Recruitment Kioni Talent

77

46 Comments