Marc Lequime

I was just blocked by a frontend framework advocate for daring to suggest that use of frameworks was unnecessary. Whilst it is an interesting way of enforcing an echo chamber, it brings the mess of frontend development into stark focus. For many, it's not even development, just glue between various third party dependencies - be they frameworks or libraries. There is no need for any of this. Frameworks were created to deal with a misalignment between web standards and the apps that needed to be developed. The browser-provided APIs were simply too immature. This is no longer the case, but now there is a new misalignment: between developer mindsets and the updated standards. There is a widely-held view that abstracting a problem to the moon & back - and the consequential complexity that results - is superior to simpler solutions. Unfortunately, many of the current problems in software development exist because of resistance to and fear of change. A garbage factory is the result.

10

9 Comments

📢 New blog! 📢 Our expert engineer Amara explores web app performance testing, from the impact of poor performance to the benefits and key timing tips - it's you're one stop resource! ✅ Read it now https://lnkd.in/emg39KF4 #AppInnovation #AppDevelopment #SoftwareEngineering #CustomSoftware #MicrosoftPartner

11

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

I've seen a few posts today around the subject of advice for junior developers. I have a few years experience now so I thought I'd give my own: * The most senior developers are comfortable asking the stupidest questions. Ask away. * Give feedback on your progress early. When you are halfway through the estimated duration of a ticket, think if you are halfway done with the work. If not, tell the team lead. * The moment you think you may have made a mistake on prod, pull in a senior developer then. What worries me with juniors isn't that they might make mistakes (we all do), it is that they delay in reporting it. Be more trustworthy than your peers. * Find a process for turning off work mentally after work. For me, running works but YMMV. * Practice planning all of your work. That means guessing and WRITING down steps in some form before you start, just for yourself. This gives you estimation and planning super powers over time. * Boring technology is almost always the best. You might have to fail using some new fangled stuff to learn this. * Learn the art of q contained side project. Look up Readme Driven Development for guidance. Anything I missed?

30

1 Comment

I'm prepping for a conf talk at the BrowserConf this week and will be talking about test flakiness in e2e testing (Playwright will be the example). What are your pain points when it comes to flaky e2e tests?

3

Your dev team is under resourced Spoiler - it always will be Don't get trapped thinking if you just had two more (or fifty more) devs you'd be able to work through the backlog and get ahead. The problem is that teams try and filter and prioritise *down stream* on outputs. 100's of outputs. Try filtering and prioritising *up stream* on strategic outcomes that matter to the business (and across the business).

12

9 Comments

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

8

1 Comment

We live in a world where technology is being hyped as the big fix to all of our problems 🥱 The headlines we get are often misleading and wrong for lots of reasons 🥴 … try again apple 🍏 So how can we cut through the BS and focus on the sliver of truth, the actual thing that tech, as a tool, can do for us? Well on Friday, I aim to answer those questions whilst I focus on how virtual reality can be used in business 🥸. I will use practical experience from case studies and data to do this. You might be surprised… If you want to find out how VR can be used in business, then book now 👇 Also featuring James Spiers, James Crawley and James Pallister

7

2 Comments

#thatDeveloperDad just tripped over his own curly braces and semi colons. This afternoon's stream did ^not^ go as planned. I looked up what it'd take to add some images to my pages with AstroJS between this morning and this afternoon. It looked easy enough. lmao! Misters Dunning and Krueger teamed up with CSS to KICK MY BUTT!!!! In short? I completely failed to meet my stated goal of getting a simple banner added to the website in the hour that I worked on it. And you know what? I couldn't be happier. When making software, we run into things that feel like they SHOULD be easy, and turn out to be the opposite, ALL. THE. TIME. In today's video, you get to watch me go through that very thing as I trip and stumble and stammer and ultimately, fail to get things looking right. (This is why I like to live behind the API layer as much as I can. Front end development gives me fits.) But you know what? It's OK. It gives me an excuse to step back, take a break and apply to some jobs, do a couple other things I need to do, and come back and do some research into what's going on with the site, and its styling and such, and I'll be able to share what I've learned in the morning. It also gives me practice with being kind to myself, and using some silliness to overcome what could be a stressful thing. Until later on... I'm #thatDeveloperDad #homeworkHasBeenAssigned #weAreAllAlwaysLearning

16

7 Comments

A quick but slightly boring summary of what I was up to in July 2024 (am yet to work out how you make setting up Firebase in your free time interesting). Time to build some apps #buildinpublic

11

3 Comments

🚀 Why Use React Native for Mobile App Development? At coding.co.uk, we specialise in building cutting-edge mobile apps that not only deliver top-tier performance but also save time and resources. One of our go-to frameworks for app development is React Native. Here’s why coding.co.uk chooses React Native for our clients: 💡 Cross-Platform Efficiency: Develop once, deploy on both iOS and Android – doubling your reach without doubling the work. ⚡ Speed to Market: Our experienced team accelerates your app’s development timeline, bringing your ideas to life faster than traditional methods. 🔥 Native-Like Performance: With React Native, we deliver apps that feel and perform just like native ones, ensuring an outstanding user experience. 💰 Cost-Effective Solutions: By utilising React Native, we help our clients reduce development costs while maintaining exceptional quality. 👨‍💻 Expertise You Can Trust: Backed by a team of seasoned developers and a vibrant global community, we’re ready to bring your vision to life. Want to learn more about how React Native can transform your mobile app? Check out our latest blog post! 📲 👉 https://lnkd.in/eciRHDfR #ReactNative #MobileAppDevelopment #CodingCoUK #CrossPlatform #AppDevelopment #React #TechInnovation #BusinessGrowth

3

Just like Nessie on the Loch, our incredible service might seem too good to be true🦕 But unlike the Loch Ness legend, AWCape’s implementation of software like Sage Intacct is the real deal! Don't settle for myths! Get in touch for a consultation and see how we can transform your finances. ➡️ https://lnkd.in/dGXW8PS9 #AWCape #BusinessEfficiency #Sage #SagePartner #YourDreamTeam #FinanceGuru

1

At Computer Futures we host monthly Rust meet-up in our Leeds office. For those of you who have not attended the meet-up before, you may be thinking “what is Rust?” Our recent article will dive into this question and explore the benefits of using the system : https://lnkd.in/efd47uCB We hope to see you all at the next Rust event!

1

Day 6: Code Review 101 Challenge Today's post highlights the importance of no-noise code reviews. As seen in the image, there are no extensive code review comments, just a quick acknowledgment. Why? Because relevance is key. At Panto, we believe acceptance is more important than nitpicking for accuracy. A great code review is one that adds value, is highly relevant, and doesn't overwhelm developers with unnecessary comments. That's why our bot is designed with a maker-checker logic that filters out the noise, ensuring only the most useful feedback gets through. We aim to keep code reviews clean and efficient, providing feedback that matters. Less noise, more relevance! #CodeReview #DeveloperTools #CleanCode #NoNoise #EfficientCoding #DevCommunity #BestPractices #Panto #AIinDev #CodeQuality #AutomationTools #DevFirst #OpenSource

6

I've been lucky enough to have a few opportunities come my way recently, but they have all had 1 thing in common...a #CSharp backend. So there's only one thing for it! For the last couple of weeks I've been learning C#. It's been a really interesting journey so far, and one I feel quite positive about. I had already encountered C on the #CS50 course, so thankfully some of the early confusing concepts (ints vs doubles vs floats vs decimals etc) did not come as a surprise to me, and my many wranglings with the #TypeScript compiler set me in good stead for tackling a strongly-typed language. The C-Like syntax shared by #JavaScript and C# has been a double-edged sword - on the one hand it made learning the very basics a breeze: a for-loop, for example, is almost identical across both languages. However, it has given me a real headache when it comes to arrays which look similar but are handled enormously differently. Essentially, in JS arrays are mutable and it is very easy to add/remove elements and alter the length accordingly. In C#, arrays are fixed-length, and are not as easily manipulated. Lists in C# are another data structure, which shares more similarities with JS arrays. It has also been really helpful in forcing me to think harder about the underlying data structures in memory, rather than relying on JS's laissez-faire approach 😂 I began my journey by following the Microsoft Foundational C# programme, which was really useful for learning basic concepts, but did not really cover the #objectoriented structures that most C# programmes are built on. For the next step, I have looked into some tutorials and trying to rewrite some of my older projects in C#, but I realised I lacked the fluency to get the best out of these. To build up fluency, I'm going hard on Codewars. This has been really useful in forcing me to dig into the #dotNET docs, finding and trying out methods and comparing my solutions with others'. I'm excited to get to the point of fluency, so I can build programs which properly dig into the object-oriented structure of C#. So far on my journey, I've tried to restrict myself to building competency with JS/TS to avoid spreading myself too thinly. However, I am confident that I am becoming a better developer by throwing myself into slightly less comfortable waters, whether these opportunities come through or not. And if that involves building a tic-tac-toe game, well, so be it! #codingjourney

38

7 Comments

In-house vs agency – which is the best choice for an apprentice? 🤔 There's no right or wrong answer, as it's less about the "best" choice and more about which one will be the best fit for YOU. In her latest blog, our Software Engineer in Training, Lil Corris, explains why a digital agency was the best choice for her, compared to an in-house apprenticeship role. Lil found that with a wide range of client projects across several industries, being in a digital agency offers her a richer learning experience by exposing her to various styles, techniques, and tasks. Check out Lil's blog to find out why she finds being an apprentice in a digital agency so rewarding, and how it could benefit anyone looking to kickstart their career in tech. Continue reading: https://lnkd.in/eg86qqzf

2

🚨 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