Ian Field

Do you have a React Native app and want to extend your app into the land of Vision OS? Well look no further than this wonderful little package https://lnkd.in/eGrjCe2K (I have no affiliation). It definitely isn't ready for production use but it's a great step forward in bridging the gap and bringing React Native and VisionOS closer together. I will try it out and share some findings... I feel like I have to because I am doing literally nothing else with my Vision Pro. #ReactNative #VisionOS #Development

7

1 Comment

I've launched the new questions experience. A couple of questions on Frontend Hire will use this experience. Taking you to the local environment helps me cater to a wider range of questions and cover things like testing, accessibility, frameworks, etc., For example, the below question is something I ask quite a lot in interviews. Usually a bit more complex function and how they would break it down into smaller and more readable parts. I hope by teaching such refactorings more people will write better code. Thanks to Ankit Gupta and Karan Nagpal for giving their feedback on the same! Question Link: https://lnkd.in/geRm5-jh #frontendhire #interviewquestions #testing #refactoring

11

📢 📢 📢 The electorate has spoken! The next Workshop Wednesdays session (3 July) will be on Kotlin coroutines and concurrency. How much do you know about scopes, contexts and jobs? What really happens in a suspend function? I've updated the listing and you can sign up right now (https://lnkd.in/dNY6MCgG), it's free and takes place online. Thanks to all 209 of you for taking part in the vote! We'll do the other sessions soon too, the Bluetooth probably next, as that came second (and it's suuuuper fun). #androiddeveloper #kotlin

20

It's not all non-symbolic AI... I presented today to Accord Project Technology Working Group on recent enhancements to the Template Engine and how TypeScript expressions within templates are compiled and evaluated. Accord Project uses TypeScript over Concerto types (with Concerto also compiled to TypeScript) to provide type-safe logic/calculations for templates; ensuring that a wide array of programming errors are caught at template compilation time, not at runtime. #typesafety #soundness #typescript #templating #legaltech

17

2 Comments

⚙ Platform Engineering Lead Rob Hornby on implementing DX ⚙ “I think that evidences the success of DX, that everyone talks about it. At the team level, they say ‘Oh the DX results said this, this is now what we’re focusing on'...It's seen as a key measure of how we're doing.” Listen to how John Lewis Partnership is using DX to strategically improve their engineering practices #platformengineering #developerexperience

20

3 Comments

I've been exploring the ABP Boilerplate Framework recently, and I’m really impressed with how it simplifies building modular and maintainable applications. From microservices to domain-driven design and multi-tenancy, ABP covers it all. Looking forward to using ABP in my next project and seeing how it enhances my development process! #SoftwareDevelopment #ABPFramework #TechInnovation

3

2 Comments

I’m you sure many of you know that selection of software when investing in a business system is important but that just gets you to the start line. Just as important is the selection of your support team - picking the correct partner that can support you when things aren’t quite working the way you would expect is critical to ensuring that you are running smoothly every day. That’s why we are so proud of our incredible support team’s performance - for example, in June, our team provided an initial response of 10 minutes or less for 47% of the support tickets logged. Just let that sink in - 47% inside 10 minutes!!! It shows just how effective they are, especially to hit that number across a large team and shows how our support team truly understand and appreciate how your Sage solution supports what you are trying to achieve as a business. That's why we're dedicated to resolving your tickets as swiftly as possible. Here is a flavour of some of the feedback that they have received from last month: 💬 "Life savers" 💬 "Went above and beyond to understand my issue and come up with a solution - thank you" 💬 "Top notch service and support" Our support team truly is amazing, consistently going the extra mile to ensure your success. #CustomerSupport #SageSupport

7

“I’ve been saying this for a whole year and no one listens, then the CEO said the same thing last week and everyone is acting like it was the most brilliant thing they ever heard” A QA engineer said that at a company I worked for in the past and it cracked me up because it’s so true of life in general. People are quick to dismiss advice that doesn’t come from a “high authority” or “reputable source”, that's just how we are wired to filter information. But if you hire really smart, proactive people and then reduce their voice to a whisper, your company is going to suck. This is why important that leaders do three things: 1. Listen to your employees and help amplify their voice → If you spot a great idea, give credit and then use your clout to push it to make it happen 2. Make them a higher authority, put them in charge of things, expand their remit → It doesn’t matter if you hire the top talent in the world if you box them in a tiny space or put them under management of someone who is not qualified to understand the output of their work. 3. Ensure you have clear values, mission and vision so it’s easy to spot what the great ideas are. → A great idea in Apple may not be a great idea in Amazon. Two companies, two very different values, that’s why it’s important that everyone in your company understands what the north star is, so they know what the metric for good idea is. 

370

38 Comments

Interesting paper about property based testing in real usage. Looks like as with any written tests it can help devs have clarity on their solution specs and helps document code. Harder to implement but more valuable when in place. https://lnkd.in/g_UEJvXW

5

Just got a chance to listen to Laura Tacho's talk from LeadDev London, "Measure for Change" covering why you need both qualitative and quantitative data when measuring #developerproductivity. When people measure developer productivity, it's often for the reason of reporting the measurements upstream to make someone above them happy, and to validate that they're doing their manager/director/VP job well. 𝗪𝗵𝗮𝘁 𝗺𝗲𝗮𝘀𝘂𝗿𝗲𝗺𝗲𝗻𝘁 𝘀𝗵𝗼𝘂𝗹𝗱 𝗯𝗲 𝘂𝘀𝗲𝗱 𝗳𝗼𝗿 𝗶𝘀 𝘁𝗼 𝗳𝗶𝗻𝗱 𝗼𝘂𝘁 𝘄𝗵𝗲𝗿𝗲 𝗶𝗺𝗽𝗿𝗼𝘃𝗲𝗺𝗲𝗻𝘁𝘀 𝗰𝗮𝗻 𝗯𝗲 𝗺𝗮𝗱𝗲, but the improvements themselves must be made by the people doing the work, not those observing them. "We want teams to use data, not just view it. We can do that when we mix quantitative and qualitative data together, because what we don't want is numbers without context..." By involving teams in the measurement process, and giving data back to them, you can drive real change, as opposed to working from a metaphorical box in the sky to report to someone even further away from the work being done. https://lnkd.in/gvK3fX7H

18

2 Comments

So I wrote a little thing to help people out with reducing your dependence influencers and instagram... https://lnkd.in/eMwjvpGc Still a bit of a work in progress, I'm updating the lists as often as I can, and I'm trying to make it more resilient and efficient. I am also writing some git flavoured logic to automate determining people taken off the lists, so they can be unchopped. Would be so much easier if instagram just gave you actual API access... Let me know if you have any problems. Please note the terms of the license before trying to use for nefarious purposes. #Python #Selenium #Blockout2024 #BadAPIs #AutomatedBrowser #AntiGenocideLicense

When was the last time you set any other timeout than the default one on a client? The longer I work in software engineering, the more I arrive at the conclusion that setting more aggressive timeouts - which are way lower than the default ones - is a hugely underestimated and underused feature in software development. Why would you use the default 30s timeout of most http clients when calling an internal service, which probably resides in the same datacenter? Having a service recommend a timeout for clients connecting against it will not only serve as an SLA, but it also allows faster failing: “If we don’t respond in x units of time, don’t expect us answering at all”. This will tighten the loop between request and response (either positive or failure), leading to a faster fulfilment towards the customer. Additionally, it forces us to think more careful about the unavailability of resources and how to deal with it. There is now a real incentive to keep our services snappy! A swift response to the customer - either good or bad - is preferable over optimising for a positive fulfilment of the request through exhaustive timeouts. In a fast paced world as it is ours, this can really make a difference on how responsive an app feels. Just be sure: I am not rooting for having such aggressive timeouts, that x% of the requests end up failing. Yet why bother waiting 25s longer when after 5s the request still remains unanswered? All our customers see is the waiting time anyway, they don’t care - nor should they - what happens behind the scenes. They care about results.

15

2 Comments

📢TOP TIP for AWS focused DevOps/Platform/Site Reliability Engineers looking for a new position📢 I have spoken to 3 Engineering Directors this week, and they all told me they are getting so many applications for their mid-senior level roles. They openly admit that they have less time than ever to read profiles thoroughly and need the resume to stand out to them EASILY & QUICKLY. Here is what was on their watchlist when reviewing a profile👀 🎯AWS, Terraform, Kubernetes & CI/CD experience 🎯Software Development skills 🎯Evidence of the key technologies used per role (spell it out for them) 🎯Where you have made an impact on the business/the project ("I" not "us") 🎯How you have saved time and/or money 🎯Evidence of strong communication skills If you'd like to know what the industry leaders in Cloud & Platform Engineering are looking for feel free to reach out to me📩 #tethr #devops #sre #platform #resume

11

Trying to hire a junior to mid-level engineer in Scotland with great benefits and remote working is hard... https://lnkd.in/eQNHVqGR Not because the role isn't attractive (you'd be working on exciting large-scale system infrastructure challenges writing code with Golang - 1,000's of Kubernetes clusters, 10,000s of cloud VMs) or because the team are all crazy (they're thought leaders in their field including multiple upstream Kubernetes contributors from 3 continents!)... you got me... maybe there's a little crazy - but only the good kind! No... my challenge is whether this AI-generated image to go with my LinkedIn post makes any sense! I never have much luck with images containing generated text. Even using prompts like "spell check any text" or as is the case with this one "do not include any text" doesn't seem to work. Not to mention, I know what a Scottish Terrier is... but that "thing" in the bottom right looks more like an angry, tartan-wearing Capybara. Comment below for your biggest concerns with this image... or if you're a junior/mid-level, talented software engineer based in Scotland - maybe just skip over the image and apply online - https://lnkd.in/eQNHVqGR

61

12 Comments

MVPs shouldn't go to the bin, unless the business pivots to something else. Way too often I've seen agencies & devs building MVPs in a 'poor' way (and that's a nice way of putting it), because 'who cares, it will go to the bin anyway when you get PMF and fundraise'. I disagree. There's absolutely NO reason that your MVP should go to the bin, unless your business model or product change dramatically. And even then, a lot of boilerplate (like signup, subscriptions management, emails, etc) - can and should stay the same. If done right, that should be a given, with 0 extra effort on the dev side. If someone's quoting you to do a poor job, don't work with them. You can stay agile & lean (as a startup should) without compromising on quality, and forcing yourself to rewrite the next version of your app. When you're investing in something, especially at an early stage when money is tight, it's important to NOT buy garbage.

10

2 Comments

I'm observing a team writing code as an ensemble without TDD. I am selfishly delighted in the confirmation of how valuable TDD is to me as I use it. The team is implementing a new function that's doing list of list manipulation and returning something. They are all over the place with naming things, creating objects, streaming, mapping, flattening maps, return object, variables, naming...so many squirrels. Too many squirrels to even really focus on "what's the simplest first thing we could do?" TDD is so much more than writing a test first. It's a framework that helps me focus, prioritize, structure, and order my thoughts. Test Driven Development is an immensely helpful design and focus tool. I should also note, that I am beginning of working with this team and meeting them where they are. #codelife #devlife #TDD #testdrivendevelopment #unittesting #designthinking #problemsolving #structuredthinking #focus #mindset #toomanysquirrels #codingchaos

282

62 Comments

If you’re an engineering leader, this report about the current state of tech has some great insights. It’s super fascinating to see what the current common themes are.

3

Code readability: prefixes. If you've got a method which checks if a status is true or false, instead of calling it 'status', why not try 'isStatus' or 'isPending'? If you've got a method which checks if someone has replied, don't call it 'replied', call it 'hasReplied'. In my opinion, it's better to hint at whats being returned. Lots of micro-improvements like this make your code easier to read.

9

4 Comments