David Gimelle

Bounties Available 🤠 If you are a Scala, Kotlin or Java developer and are looking to help out the community whilst adding some extra cash in your pocket, then you probably want to follow Haoyi Li's Reddit thread 🧵 This thread is growing, here are how the total bounties look from the past few months; May: $2,500 paid 💰 July: $1,000 paid 💰 September: $10,000+ available! 🤑 If you want to see if there is anything you can help with, then take a look here:

24

1 Comment

How important is domain/industry knowledge within QA? Lots of companies see it as a big bonus when they’re hiring, with some even having it as mandatory - but do they really need it? Or are they just assuming it’ll bring them more value + less time spent on mentoring and getting someone up to scratch in those specific areas. There’s certain industries that I can see the argument for, whether that’s a specific financial platform, or companies that have to adhere to specific regulations (as an example) - but does the new ideas and skills that someone can bring in from a completely different industry, potentially outweigh that? Also, are these skills that difficult that no one pick them up - everyone has to start somewhere, right? Like anything, there’s pros/cons and this is just a generic overview - but being narrow minded and not considering an ‘outsiders view’ maybe isn’t always the best option.

27

9 Comments

this is a really important point. Of course it's allowed! the only people I have met with that interpretation of tdd are people who have been forced into it by people who think it's the simple act of writing tests first that matters rather than the mindset that makes you realise doing otherwise is likley play. I think it's really important. When code works according to the spec we should be allowed to ship it. that doesn't mean we are finished - just hit the bare minimum standard. Then we should be allowed to invest more into it and ship it again, and again. This whole madness and obsession with tickets gets in the way of the feedback loop of determining value, shipping and exploration with the consumer of the code. The tests are the *most* important part of a codebase. I can rewrite code but I can only rewrite tests whilst the domain knowledge is clear in my mind. Tests are the source of truth for the behaviour of the system. After that point I depend on the tests to replay it to me. So refactoring and development of tests is a noble persuit that I think many teams and engineers undervalue.

1

📢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

TDD is expensive Like many other niche technologies Delivery of software is not only a technical problem It’s logistical and people problem as well It can be using Kotlin in Java company It can be adding a better database engine It can be applying Event sourcing to all systems You can say all of those are great But there are a couple of non-technical problems 🧠 Knowledge The whole team must know the new solution They need space to learn and practice You may get training from an expert Both cost money and time 🚦 Risk You face the bus factor What if the devs will leave? (they will) How will you maintain the niche solution? How much will it cost to hire or train a replacement? 👩 Hiring Adding new technologies narrows the pool of hires The more niche you go the harder is to find a good fit The longer hiring process will strain delivery You'll have to balance with higher salaries ☯️ Alignment What about your current team? 80% of them like tests but aren’t fans of TDD What will you do? Force them to learn or let them go? The culture will take a hit and retention will sink What can you do instead? Keep it simple Keep it boring Focus on the basics Drive incremental improvement Find alignment before picking new tech Get excited about the features and business If you don’t need to fix niche problems You get more time to deliver value

24

13 Comments

👉We have been chatting to a couple of new clients in Germany this week, about using freelance Developers/Engineers outside of Germany (Nearshore), the same questions pop up; ✔How do we know if they are good or not? ✔How much can we save? ✔How quickly can they start? 👀Like anything, there is pros and cons to everywhere, but we have built a network of Freelance Nearshore Engineers who have been rigorously vetted with technical expertise guaranteed, that could save you a 50% reduction on your current freelance rates. If you are interested to understand more about this option and how this could help your business. 🚨Feel free to book a call in my Calendly and let’s see if we can help - https://lnkd.in/eygXyhaz

8

3 Comments

I just watched Daniel Terhorst-North's talk at Kotlin conf, having sadly missed it in person (nothing to do with being hungover on day two of the conference). Daniel is the originator of Behaviour-Driven Development and gave a talk titled 'The best programmer I know'. A few interesting takeaways: - You don't need a degree to be an exceptional programmer - Everyone is a kinesthetic learner. Some people might lean towards seeing or hearing things, but everyone learns through doing, so just start and iterate as you go. Lean into uncertainty. - Invest in the product - not the code - Watch your users and find out what frustrates them - TDD pays off. Daniel's team at BP won a software quality award for their trading system. Unlike other teams, they found zero bugs during six weeks of UAT, thanks to TDD. BP paid them to stay on for the UAT period, which they spent in the pub. If that's not an incentive to learn TDD, what is?" - Explore different languages, tools and paradigms to give you more options and help you solve specific problems throughout your career - Help others - teaching is the best way to learn - Overall takeaway for me is that soft skills are clearly equally as important as hard skills in software engineering Worth a watch. https://lnkd.in/e8bau4X9

15

1 Comment

Catch Continuous Delivery Author, Dave Farley & TDD/DD expert, Denis Čahuk talking live about DORA, Continuous Delivery, TDD & much more. The event link is in the comments below 👇

36

4 Comments

Reposting to extend reach. I 💯 agree that your CI/CD should be something that can be executed manually in a local environment. I also agree we need to assume cross-platform and architecture when possible.

3

1 Comment

*Bracing myself for the response I might get for asking this* Software Engineers: Would you ever consider working on an EQUITY ONLY basis (ie no salary, just owning a portion of the business, the value of which would increase as it progresses and scales)? Assuming: - The product is really interesting and so is the work - The product is in the "tech for good" space and would be a really positive contribution to parts of society - Seed funding is confirmed to be coming with several backers keen & they will able to offer a salary in the near future - The product is super early stage, you would be writing the software from the ground up, but the concept, design and business model once funding is received are all solid I know that there will be many who would never consider this under any circumstances and I totally get why, but just curious to hear if any of you would if it was for a product you believed in enough? And would you look at it on a full-time basis or a part-time basis? It's something I got asked about and so I thought I would throw it out to Linkedin to see what you all think rather than assuming that I know the answer on your behalf. #startup #founder #softwareengineer

39

309 Comments

Good morning everyone 👋 I’ve posted before about my love for the Tech Radar concept from Thoughtworks to track emerging technologies across its engineering teams. You can see the latest edition here : https://lnkd.in/eaGbSNie 🚀🚀 Key themes this time are:   — Coding assistance antipatterns — Rust is anything but rusty (Tim Lewis 👀) — The gradual rise of WASM — The Cambrian explosion of generative AI tools If you are not familiar with it yet the Thoughtworks Technology Radar is a twice-yearly snapshot of tools, techniques, platforms, languages and frameworks. This knowledge-sharing tool is based on our global teams’ experience and highlights things you may want to explore on your projects. The Radar is a brilliant way to keep track of some of the latest tech and understand how these are being considered by some of the best technologists in the world 🌍 Some of the latest tech is broken down into the following categories: - Adopt. Blips that Thoughtworks think you should seriously consider using. - Trial. Things they think are ready for use, but not as completely proven as those in the Adopt ring.  - Assess. Things to look at closely, but not necessarily trial yet — unless you think they would be a particularly good fit for you. - Hold. Proceed with caution. Well worth a look! The team also releases some brilliant supporting webinars for each release, which can be found on their YouTube channel. Kudos to Thoughtworks for such commitment and enormous effort. Another brilliant edition 👏 How does your organisation decide which technologies to work with? #TWTechRadar #softwareengineering #softwareengineeringleadership #cio #technologychoices

16

8 Comments

I think I may be a little late to the party here but, blimey Charlie testcontainers.com is super useful for your integration tests. 1) I can see why Docker snapped up the developers, AtomicJar 2) testcontainers.com may make building integration tests just a little too easy

6

Developers.... Can someone explain why SRE acronym has been hijacked as the moniker of the Software Engineer? According to https://lnkd.in/e2Wj2kCy - SRE stands for Site Reliability Engineer. Whilst this and a Software Engineer role may overlap, the first is not the second and the second may not be dealing with Sites at all. If you have that role or are a software engineer that uses SRE, can you explain what it means and why you have it.

5

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

56 Comments

SRE vs DevOps... I once got into a bit of a debate with a manager over the differences between SRE and a DevOps Engineers. His view was very much "they're one in the same" which I couldn't wrap my head around... It very much felt like a spotlight moment... Like I had Chris Tarrant sat opposite me (Sorry Jeremy). My stance and understanding from my time is kind of, what it says on the tin... Ensures uptimes, availability and robustness (i.e. reliability) of the Product and it's Infrastructure. His was very much no they need to be able to work across multiple domains and be able to code. As a consultant, Shock... I'll consult to partners what the market dictates, trends and help improve their processes but I've known a few DevOps and SRE interviews ask for coding tests and I often have to ask what the actual requirement is and if it dictates that? I get it if that's required and that skillset is necessary but then I would question calling that an SRE... I know it's always up for debate but keen to hear other peoples two cents or if I've got the wrong angle here... Alec Bruce-GardyneKim O'CallaghanBecca CoombesConnor AndrewsMaryann McGeeSteve BowenGeorge AldridgeAdam HolmesRichard Morrish

31

19 Comments

We have TDD and BDD and DDD … I’d like to respectfully suggest another acronym CDD - CI Driven Development. Unfortunately this isn’t IMHO a good thing. I’ve worked in several places now where CICD has taken over and there are extremely complex pipelines and corruptions of code to ensure that there is comprehensive a complete coverage of every possible scanning, testing, analysis, and checking … but in the pipeline ONLY. What those that push CDD forget is that developers need to run/reproduce these checks locally! I recall a video of a talk given by Daniel Terhorst-North some time ago where he suggests running builds manually to check that you still understand what is going on. I think this excellent advice has been completely ignored and swamped by vastly complex GitHub actions or GitlabCI script, mountains of Groovy code, huge docker compose files. I would submit that your CI should simply call Make targets (or similar commands for the relevant build tool). CI scripts should be simple. Aim for build scripts that help a developer run things locally really quickly - make test should whizz through unit tests for example. Also can we PLEASE stop assuming everything is x86: we live in a world with at least two major architectures and a third on the rise: multiarch builds should be the norm!

80

56 Comments

Something I have seen lots of times on the business environment in LATAM, some big old companies are just catching up to modern tech and tendencies. You don’t have to implement it right away, but at least try to keep up and incrementally start integrating into your projects or just start experimenting so that when the times comes, you are prepared

5

1 Comment

Yesterday we: Deployed a couple UI/UX polish features at 11 am Deployed upgrades to Frigade and PostHog at 2 pm Deployed onboarding revamp at 5 pm Deployed document import at 7 pm Deployed a hotfix (for onboarding) at 1 am yesterday (well... this morning) We ❤️ moving fast but the Joggr team is ready for the weekend so we can relax... and switch to working on open-source projects 😂 #movefastdontbreakthings #deployments #weekend #nodejs #javascript #opensource #codingonabeach

44

2 Comments

The Art of Self-Review: A Solo Developer’s Guide You should always have someone to review your work – a manager, a lead, a mentor, a psychotherapist. An external perspective is crucial for validating your thoughts and intentions. But what happens when you don’t have anyone around? That's my current reality. Five months ago, my backend engineer partner moved to another team, leaving me solely responsible for all server-side decisions. Initially, I felt sadness and loneliness, which quickly led to a drop in both speed and accuracy. This challenge prompted me to elevate my self-review practice, and here's how I do it: 1. Complete the Code — Ensure it's fully functional and meets all acceptance criteria. 2. Post for Review — Submit your code as you would for any peer review. 3. Switch Tasks — Move on to another task until the end of the day. 4. Start Fresh — Begin each new day with a Code-Review session. 5. Review Your Code — Use a Code-Review Tool like GitLab to gain a reviewer’s perspective. 6. Blur Ownership — Review your code alongside others’ work to minimize bias. 7. Leave Honest Comments — Critique your code as if it were someone else’s – no hesitations or leniency. 8. Address Feedback — Review comments, respond, and proceed to QA. > Be a leader for yourself. Poll - Do you practice self-review? - Do you leave comments for yourself? - Do you agree that your code isn't ready for cross-organizational review until it passes your self-review? - Do you apply self-review to other activities, like planning a vacation? Inspired by [Christian Hammond's blog](https://lnkd.in/d5Y3KZHB) #LifeIsASoftwareDevelopment #CodeReview #SoftwareEngineering #TechLeadership #BackendDevelopment #DeveloperLife #SelfImprovement #AgileDevelopment

15

7 Comments