Jack Gilmore

So many software engineers in Scotland are moving to fully remote roles. Not out of choice but out of a lack of local opportunities over the last 12 months. I speak to so many people who are looking to be part of the ecosystem, to work on a hybrid basis with tech organisations in Scotland, but struggle to find opportunities. The question is, are the opportunities not here - or are they simply not competitive enough? If we arent competitive when it hiring then thats going to compound itself once all the best talent is woking outwith the country. If the opportunity just isn't here then it's a much simpler challenge that creates interesting opportunities for outward investors to capitalise on the outstanding tech talent thats up here. I think the reality lies somewhere in between. Which means that for local employers, they need to make their opportunities attractive...

31

17 Comments

We've published another great article from Wayland Goodliffe, Senior Backend Engineer at the John Lewis Partnership. This one describes how he uses GitHub Copilot for code reviews. At the end of the article he shares his detailed review.prompt.md file which he developed iteratively for when he is nearing completion of his own tickets and when he is reviewing a colleague's merge request. https://lnkd.in/eMpPizRx

24

1 Comment

Launch Group just published a blog that’s well worth a read 👇 AI is changing the game for software engineers, and not just at the senior level. Imogen Hough, our Senior Consultant for software engineering, shares what she’s hearing from clients: - They’re not asking for “typical” developers anymore. - They want engineers who bring system design, architecture, and judgment to the table. From my side, I’m seeing the same shift: ✨ AI literacy is becoming essential — even for juniors 💡 Problem-solving and initiative are standing out more than routine coding 📈 Continuous upskilling isn’t optional anymore If you’re hiring in tech or thinking about your next move as an engineer, this blog is a great pulse-check on where things are heading. Would love to hear your take, are you seeing this shift too? #LaunchRecruitment #SoftwareEngineering #AI #TechHiring #HiringTrends #Recruitment

9

3 Comments

Blazor United and the rise of full-stack .NET is something that’s been coming up more and more in conversations I’ve been having with .NET developers recently. A common theme I’m hearing is frustration around constantly needing to jump between backend C# and whichever JavaScript framework is currently in demand. Blazor United seems to be changing that conversation, with developers telling me they’re excited about being able to build across the full stack using .NET. The ability to combine server-side and WebAssembly rendering in one model is a big part of the appeal, along with improvements in performance, payload optimisation, and built-in security features. From a recruitment perspective, it feels like this could drive stronger demand for engineers who can deliver end-to-end solutions within the .NET ecosystem. Definitely one to watch as adoption grows. Do you agree? #DotNet #Blazor #FullStackDevelopment #TechHiring

33

32 Comments

I mentioned one of my “down the pub” software development opinions to James Lewis at EventCentric. He suggested that I mention it to Kent Beck and so, while I remember. But definitely, the tone here, is “crazy talk over a pint.” ———- XP optimises software development for folks with ADHD. The Extreme Tuesday Club is likely a hotbed of ADHD diagnoses. TDD, CI, Small Releases: we need those rewards to keep coming in regular doses. Pair Programming: “Stay on target, stay on target” Refactoring, Boy Scout Rule: “Ooh, while I am here, I should fix that as well. Now where was I? Oh the test list.” Sustainable Pace: We can only focus so long in one stretch, even with the above. Planning Game: one story at a time, don’t get distracted by other things. Business value, not “shiny thing.” Small stories because we get bored easily. Whole team working so that we can get to that shiny story faster. Osmotic Communication: Quick, let me blurt out my idea before I get distracted and forget I wonder if there is a correlation between XP teams achieving flow, and XP teams filled with neurodivergent people who have figured a coping mechanism for productivity.

312

67 Comments

🚫 “Junior” role that needs a senior? Call it what it is. If your job ad asks for: • 5+ years experience • 3 frameworks + cloud architecture + CI/CD wizardry • “Works independently with no guidance” …that’s not a junior role. Juniors need: • Clear scope and realistic expectations • Mentorship and code reviews • Room to learn, ship, and grow Candidates: you don’t need 100% of the boxes ticked to apply. Companies: if you want a junior, invest in one. If you want a senior, say so. We all start somewhere. Don’t gatekeep the starting line. 👇 Seen a wild “junior” ad lately? What should a true junior JD include? #JuniorDeveloper #TechHiring #EntryLevelMeansEntryLevel #DevCommunity #BuildInPublic #LearnInPublic

120

57 Comments

I've been at a lot of workshops or conferences the past couple of weeks, and I've been reflecting on what I've heard whilst also taking the time to look back across my career (and my bookshelf, which feels like a form of software archaeology). Test-Driven Development (TDD) was just becoming popular when I started my career 25 years or so ago. I got hooked and followed up with Kent Beck's work on eXtreme Programming (XP), which championed ideas like pair programming, working closely with customers, and delivering _working_ software frequently. Since then, we’ve seen movements like Continuous Delivery, DevOps, Team Topologies, and product operating models like Marty Cagan's SVPG vision. Each has helped refine how we build and deliver software. But at their core, they all reinforce the same key principles: ✅ Work directly with customers to focus on outcomes ✅ Ship high-quality products frequently ✅ Build cross-functional teams that can execute end-to-end The language evolves, but it feels like the core challenges remain.

40