Matthew Clarke

I gave a talk at the most recent London Ruby User Group (#LRUG) on how experienced programmers solve problems, and what that means about how we think and communicate as human beings: https://lnkd.in/eBzTM53t I am really proud of this talk and care deeply about this subject; I'd love if you could give it a watch! (slides available here: https://lnkd.in/eXX89qXe)

38

Mastering Shadow DOM interactions? Discover how Playwright simplifies automating nested elements and unblocks the secrets of Shadow DOM testing, ensuring precise targeting and reducing test flakiness effortlessly with advanced superpowers.  Explore our blog on leveraging Playwright for effective web testing with Shadow DOM at Nagarro! Stay tuned for more in this series from Bharat Garg and myself, on using Playwright to solve intricate challenges. Sincere thanks to Khimanand Upreti, Vineet Bhatt, Alok Sharma, Debaghna Mukherjee, for giving invaluable feedback in refining the content. #WebTesting #Playwright #ShadowDOM. https://lnkd.in/gSwar-bV

38

11 Comments

really interesting points if you considering adopting an iPaaS.

2

8 times out of 10 a time boxed architectural spike will drive better decisions than workshops, RFCs and C4 diagrams. Whilst I value (very much) the things on the right, there is much higher proof from working software.

15

Totally agree to use Separate Routine for IO mapping rather than using IO address directly in the program. The only trouble one will face is that The Mapped memory bits cannot be forced. Forcing is to be done separately through IO mapping routine or From the controller tags. Periodic Tasks for Totaliser and PID like operations. Less use of AOI, the reason being it's not editable online. So whenever using AOI make sure, the code is tested and verified. Whenever writing a code/logic, make sure you don't restrict the use of Online Editing, very useful specially in Hot cutover projects. Another most important aspect is that the program shall be written in such a way that the cross reference feature can be utilised at its full capacity.

5

I’ll be there, learning from the sessions and sharing ways to progress and enable your engineers, from beginning beginners, through fluency, to mastery. Joining me?

2

My latest blog post went live this morning https://lnkd.in/emUHBQD8, focused on how we can make our events in tech more inclusive to neurodivergent folk

2

Want to come and work with me? We're hiring for a mid-level, a senior and a tech lead software engineer here in Manchester. We are a Scala shop so experience there would be great, but we're also honestly open to smart people with experience in other languages. * Mid-level https://lnkd.in/etE2_err * Senior https://lnkd.in/ehdGirbx * Lead https://lnkd.in/emh_R3Gx Update 2024-04-29: sorry, no visa sponsorship available for these roles. No agencies. Look, I mean it. I know there are arguments both ways but it's not my decision and if you think telling me how good your agency is will change anything, you misunderstand how enterprise companies work.

198

34 Comments

Over the course of each month, I spend a few moments each day or so collecting relevant links, and then, at the end of the month, I bundle them (with the help of some nifty automation scripts) into an easily digestible reading list. Here's everything that I found interesting in June 2024 about the Elixir programming ecosystem: #qfm #quantumfaxmachine #blog #elixir #programming https://lnkd.in/eM2Gwews

1

https://lnkd.in/eH9gpzeW Microsoft is relentless when it comes to pursuing its goals. This is a 4 hour documentary, use an LLM to get a synopsis of it and then decide which part you want to watch. For full effect of the story telling, watch it in its entirety. It captures the tussle between run-the-business vs change-the-business.

1

Since the introduction of the Delivery API in Umbraco 12, the amazing Umbraco community has been asking a bunch of questions on how to do this and that with the API. A lot of those questions have led to a better API feature set and/or improved documentation 🚀 A few have not (yet) made it into the official docs. I have put together a blog post describing some of the most interesting/useful, undocumented extension points in the Delivery API. 👉 https://lnkd.in/dNRVh3hn #umbraco #headless

29

2 Comments

Interesting article. I firmly agree with the task breakdown and implementation detail. Has anyone tried using number of tasks and average rate to project timing?  https://lnkd.in/e_HysuiJ

10

1 Comment

Look mah, I'm still an engineer 🙃 Nice to get lost in a little cost saving exercise and problem solving from time to time. I've collected quite a few "solutions" to small and large engineering problems over the last 20+ years and will be planning to post a few of my thoughts over on dev.to as and when I get the chance as a way to give back. https://lnkd.in/eGa2cY2V #dev #software #development #coding

16

Second post about the Overwrite trait: https://lnkd.in/ea2RFJVe, focused on how pinning gets better

24

To say that I’ve had a bad week would be an under statement. I try to lose myself in reading and whilst it’s not the best coping strategy it does yield some interesting results … like this piece which really resonates with me: "Bad leaders execute, good leaders improve, and great leaders compound. Compounding is not about improvisation but a coherent set of actions in response to strategic challenges ahead. [...] A strategy is a designed response to the challenges ahead." We often fall into the trap of viewing strategy as a cure-all, neglecting to validate if the problems we identify are truly the most impactful for the business. We can create meticulously crafted documents brimming with well-intentioned policies and actions, but these efforts often yield minimal organisational recognition or lasting impact due to a lack of prioritisation. https://lnkd.in/ek8Xjfkx

15

I've spent the past 12 years helping orgs move from a dev-ops team to a dev-ops mentality. One thing I've refined and learned with others along the way is the concept of a "Dev Ops Contract". It's a concept so simple, it's often overlooked, but some powerful benefits are: - Clear understanding of what software requires to be operational - Reduced complexity in runner configs (github actions, AWS codebuild, etc...) - Developer autonomy - Parity with local and remote task execution And more if you're interested: https://lnkd.in/gyRmQPq9 Is anyone else out there decoupling their CICD from their services in a similar way?

7

I don’t post a lot on LinkedIn. I find a lot of the posts are obvious statements of well known ideas or successes. I’ve decided to start posting on LinkedIn, to share, to vent, to find a little group therapy so to speak. I’ve been managing software engineers for over 10 years now. Coming from an IC background, making the transition from IC to a first line manager hasn’t been easy, but it has been rewarding. I don’t read a lot of books, in fact, just a few, and not really related to software engineering or management or the like. Most of my experience has been self learned, through failures, through mistakes; hard knox so to speak. I like leading a team, but don’t feel like a leader. I position myself as a team member on a team that has joint responsibility for success and failure. Leading by example when I can, and being led by others at times. Of course I get to make some of the decisions, but I rather see the team lead itself. It is more rewarding that way. What I find most intriguing is that one size does not fit all. The hardest part of managing is the people. Each person is unique with different experiences, different motivations, different ethnicity, different backgrounds, different home lives. You aren’t given a prebuilt team that is optimal for success. You are given the raw materials, some that are a good match for the job and others that need to be coached, developed, and nurtured. None of my team members ever took a compatibility test to determine how well they’d work with me or each other. Some are meticulous in the way they operate, some are “cowboys” (sorry for the gender team). Some can deal with ambiguity, the technical complexity, the problem solving, the scale, the quality, etc. Some need to be shown how to unblock themselves, how to find a way forward with little experience or the lack of confidence. Some flourish in an environment full of chaos, others struggle. What makes a puzzle interesting is that it takes different shapes and sizes and time to solve. Apparently there is a character limit on posts. This is my first post, it is raw and unfiltered (no help from ChatGPT). It probably lacks context and clarity, but might resonate with some. I’ll post a continuation in the coming days to help tie these thoughts together with other thoughts still yet to come.

110

9 Comments