Emily Toop

Mobile monetisation shouldn’t mean heavier apps, slower load times, or endless SDK maintenance. We have introduced the full rollout of our Unified Mobile SDK, already live across 250+ enterprise apps. One integration. Real-time control. Fewer crashes. Better performance for users and engineering teams alike. This is about simplifying complexity and giving publishers back control of their mobile stacks. Read the full article to learn why the market is moving fast on unified mobile frameworks. https://lnkd.in/dCmrYwmR #AdTech #MobileAdvertising #AppMonetisation #PubTech #EngineeringEfficiency #TradeHouseMedi

6

1 Comment

Every engineering leader says they care about velocity. But velocity doesn’t die in the IDE. It dies in: Review queues Approval loops Dependencies across 3 other teams The fastest teams don’t code faster. They unblock faster.

1

You hired your QA team for their critical thinking, user empathy, and complex problem-solving skills. So why are they spending 80% of their day manually checking login forms and running the same regression scripts they've run 1,000 times? This isn't just inefficient; it's a massive waste of human potential. You're using a surgeon to apply band-aids. The true purpose of automation isn't to replace your QA team. It's to liberate them. Automate the repetitive, predictable, and mundane. Free your human experts to do what they do best: Run complex exploratory tests. Analyze user behavior and business risk. Ask the "what if...?" questions that a script never could. Stop using your best people as slow, expensive robots.

2

👻 Kiro 👻 has had a whole host of great new features recently. There are the really big ones like Skills support and the constant evolution with new models like Opus and Sonnet 4.6, but one of my favourites is ACP... The Agent Client Protocol lets you take advantage of one of the best coding assistants 💪 around and use the underlying agent in a variety of different clients. I've been exploring how you can take advantage of Kiro for use cases that aren't all about writing code 💻 and how you and your teams can all reap the benefits from its huge capability. I've got my latest post in the comments on some of my favourite new ways to use Kiro with ACP. Let me know what you think. 🚀 #kiro #genai #kirocli

27

2 Comments

If you’re a Head of Engineering who is ready to transform a team, then I've got a role for you. I’m partnering with Julia Bearzatto at Equiem on a genuinely transformational hire. Equiem is entering its next phase of growth and needs a strong engineering leader to help bring its vision to life. This isn’t a keep-the-lights-on role. It’s a reshape-the-engine-room role. The mandate 👉 You’re a T-shaped leader with strong product thinking and serious delivery discipline. 👉 Drive cultural change, not avoid it. 👉 Have opinions on architecture, data strategy, and operating models. 👉 Care deeply about people's performance and role clarity. 👉 Connect technical decisions to commercial outcomes. 👉 Get involved in design and architecture without needing to code daily. This is innovation-led, product-led engineering maturity work. Not just scale for scale’s sake. What you’ll actually do in the first 6–12 months 👉 Reshape the team (right people, right roles) 👉 Shift mindset from legacy to curious & outcome-driven 👉 Implement a modern operating model 👉 Create visibility and predictability in delivery 👉 Unlock 7 years of event data using pragmatic tooling 👉 Elevate tech leads into real leaders 👉 Strengthen SOC2 / PCI discipline without slowing innovation Success looks like: 👉 One unified engineering team pulling in the same direction 👉 Mature planning and reliable timelines 👉 Engineers contributing to product strategy 👉 Data driving real business insight Why you’ll love it: 👉 Autonomy to restructure and implement your model 👉 A CPTO who wants you to have an opinion, not ask for permission 👉 A stable team (low attrition that’s both an opportunity and a challenge) 👉 A genuine chance to leave a mark on the company’s trajectory If you thrive on lifting standards, reshaping culture, and building a product-engineering powerhouse, let's talk. I've got plenty of information to share so please hop into my inbox if you'd like to find out more.

42

4 Comments

📊 Smarter Task Management with EmberHub 📈 Meet EmberHub - the AI-powered platform designed to make managing tasks, tickets, and complex projects simpler, faster, and more effective. From automated prioritization to real-time collaboration, EmberHub helps your team stay aligned, reduce overheads, and deliver results with confidence. ✨ Key Highlights: ✔ AI-driven task management ✔ Smart ticketing & workflow automation ✔ Powerful analytics & reporting ✔ Scalable for teams and enterprises Proudly South African 🇿🇦 - delivering world-class performance 🌍. 🔗 Learn more about EmberHub: https://emberhub.co.za/ 📌 Follow us for more updates on smarter business tools! #TaskManagement #AIProjectManagement #EmberHub #BusinessGrowth

1

Adding developers doesn't speed up delivery. It slows it down. Until you fix: - Communication overhead - Context switching - Unclear ownership - Missing documentation The best teams scale by removing friction, not adding headcount.

3

I’m not normally so active on here, but am just really saddened about the SBG/Flutter redundancies. I agree with so much of the sentiment already posted by friends and former colleagues - SBG was THE place to be in Leeds and the wider North region for such a long time. Obviously change is inevitable but it doesn’t make it any less sad and I feel for everyone currently affected. I thought I would follow-up on my earlier post and offer some tips to anyone now looking for work for the first time in potentially a long time - albeit still obviously happy to chat if anyone wants to reach out directly. 1. Don’t panic. You’ll be ok. I would hope Flutter will look after you which will give you some time. 2. For now, and throughout your search, look after yourself. Take time off, stretch your legs. Lean on friends and family if you can, offload! 3. Persevere and stay positive. The right thing for you is definitely out there! 4. Use AI, but use it well. - Ask it to review and critique your CV (albeit redact personal info before pasting into ChatGPT etc). - Ask it to compare your CV to a particular job description. - Ask it to act as the hiring manager for a particular role and perform a mock interview. - DO NOT use its output verbatim. Write everything in your own voice, that’s the human part. AI-generated text is so obvious. And no - this post is not that! 5. A good CV is definitely important, so make sure it’s up-to-date. Don’t just list generic skills, rather what impact you made and what value you can bring. 6. Update your LinkedIn profile and make sure it’s consistent with your CV. 7. Upload your CV to jobsite.co.uk - recruiters definitely do use this in my experience. 8. Know what you’re good at (and what you’re not); it makes recruiter calls easier. 9. Don’t rely on making applications through LinkedIn. Complete waste of time IMO, you’re much better off going direct through company career websites, recruiters, hiring managers if you can. 10. Be proactive. Use your network if you have one. LinkedIn, former colleagues, tech meet-ups, etc. And/or reach out to recruiters directly. Get lots of calls scheduled, sell yourself, be enthusiastic. 11. Be hyper-organised. Use a spreadsheet with something like task, status, date, and notes columns. Add a new row for any recruiter contact or role applied for, and update the notes after any communication and set the date for whenever a follow-up is scheduled, or when you plan to chase. 12. When you land interviews, prepare. Do all the usual stuff - research the company, practice situational interview questions (and STAR method answers), prepare your own questions for the interviewers, etc. Again, AI tools can be quite good at helping with this. Hope any of that is helpful and I’m more than happy to chat as well. DM if you want any CV sanity checking or anything like that.

100

4 Comments

💭 “𝗜 𝗮𝗽𝗽𝗹𝗶𝗲𝗱 𝗯𝗲𝗰𝗮𝘂𝘀𝗲 𝘁𝗵𝗶𝘀 𝗷𝗼𝗯 𝗶𝗻𝘁𝗲𝗿𝗲𝘀𝘁𝘀 𝗺𝗲.” I hear this all the time - sometimes even in cover letters. But here’s the truth: 𝘪𝘯𝘵𝘦𝘳𝘦𝘴𝘵 𝘢𝘭𝘰𝘯𝘦 isn’t a reason to apply. You might find a role exciting, but if you’re not at the required level yet, you’re just shooting in the dark. So how do you know if a job is really for you? 👉 Start with the job title. It often tells you more than you think. https://lnkd.in/ezEh385G

9

Your CI/CD bill is not exploding because of “expensive runners,” it is bleeding out through flaky tests, over-parallelized jobs, and slow feedback loops that quietly tax every deploy This piece shows you how to redesign pipelines so you cut compute waste, shrink queues, and speed up developer flow without adding yet another approval gate or YAML religion Full breakdown in the comments. #DevOps #CICD #PlatformEngineering

8

1 Comment

Having seen the alternative, which usually means complex calculation rules that someone has to maintain and nobody fully trusts, burdens are a good idea. It's something I've spent a lot of time thinking about this year as we've expanded our presence in the US. Pretty clean approach: define the on-costs, deduct them before the commission calc runs, and you're paying on what the business actually keeps. In Konquest, burdens are handled through adjusters and powered by our rules engine. You define what gets deducted and on what terms. NI, holiday pay, pension, state or role-specific on-costs. It works at the placement and timesheet level, with effective dating so rate changes don't create a manual re-do job at the start of each year. Best of all, it is all transparent. Every commissionable value is broken down in full, so you can see exactly what the burden is, why it has applied, and what's left to go into the calculation. When a consultant asks why their commission landed where it did, you can show them the working.

4

What makes a great Senior Developer? 🤔 When hiring Senior Developers, it's not just about technical skills. Yes, proficiency in coding languages and frameworks is crucial, but there are other qualities that set exceptional developers apart. ✅ Problem-solving ability: Senior Developers should be adept at identifying issues and crafting effective solutions. This often requires a deep understanding of the entire development process and the ability to think critically. ✅ Communication skills: It's vital for Senior Developers to communicate clearly with both technical and non-technical team members. This ensures that everyone is on the same page and can collaborate effectively. ✅ Leadership and mentorship: Senior Developers often guide junior team members. Their ability to mentor and lead by example can significantly impact the team's overall performance and morale. We always discuss the value and how hirers prioritise these qualities to ensure we match the right talent with the right opportunities. If you're looking for your next role or need to find top-tier talent, visit bristowholland.com or drop me a message. #TechRecruitment #SeniorDevelopers #HiringTips

4

🚀 Go 1.25 is here! Just dove into the release notes and I'm genuinely excited about what the team has delivered this time around. The standout for me? - The new testing/synctest package runs a test function in an isolated “bubble”. Within the bubble, time is virtualized: time package functions operate on a fake clock and the clock moves forward instantaneously if all goroutines in the bubble are blocked. Finally, testing concurrent code without the usual timing headaches! This "isolated bubble" approach is brilliant - your tests run in their own time dimension. No more flaky tests due to race conditions. Testing time-dependent logic (like timeouts or scheduled tasks) is deterministic now. - Performance improvements are solid too. The compiler can now allocate the backing store for slices on the stack in more situations, which improves performance. Plus, GOMAXPROCS defaults to the number of logical CPUs available at startup with smarter cgroup awareness for containerized environments. Your Kubernetes deployments will thank you. The container improvements alone make this worth the upgrade. No more CPU throttling because Go finally respects your resource limits properly. Full release notes: https://go.dev/doc/go1.25 #go #golang #programming #development #backend #performance #testing

15

Code reviews aren’t about proving who’s right. They’re about building shared standards, spreading knowledge, and growing stronger as a team. The best reviews improve people, not just code.

4

If you’ve ever struggled with keeping database changes in sync across dev, staging, and prod - Flyway might be the tool you didn’t know you needed. I've written a 2-part blog series tailored for developers: Part 1 : Why use Flyway? Understand the why behind Flyway, versioned migrations, idempotency, and what it brings to the table for modern dev teams. -> https://lnkd.in/dZtPAK5N Part 2 : Hands-on with MySQL A step-by-step walkthrough: setting up multi-env DBs, running migrations, seeding data, lifecycle hooks, CI/CD, and more! -> https://lnkd.in/dbGbQNc3 Built for developers by a developer🤓

7

2 Comments