Nolan Di Mare Sullivan

This guide demonstrates using Terraform's lifecycle meta-argument to ignore changes to parameter values, enabling seamless integration with other processes that modify these values. https://lnkd.in/eK8QYnVv

1

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

Migrating off of Terraform Cloud? Check out all of the resources Scalr has available to you to make the migration easier: Automate your migration with our TFC to Scalr module: https://lnkd.in/eFNEn842 Estimate your costs by pulling run details from TFC: https://lnkd.in/eEe3NiYc See the similarities and differences between the two products: https://lnkd.in/e-JCtEx4 See the differences between the two pricing models: https://lnkd.in/epKatCtK Watch a video on how the two products compare: https://lnkd.in/eMFAhK5a Learn from previous migrations: https://lnkd.in/egnyEAXe Want to learn more? Contact us for a discussion or demo: https://lnkd.in/eBB7mGug

17

I've reviewed some cracking RFCs recently. It's one of the things I love about PayFit France's engineering culture. People genuinely seek out other perspectives and feel comfortable proposing solutions to contentious topics. And the feedback is always well-intentioned and constructive. One aspect of a great RFC is starting with a well-defined problem statement. If you can create a compelling narrative that makes people feel that this is really a problem worth solving you are off to a great start. Before you mention the solution, can you quantify the current costs or future opportunities? Can you explain how these technical issues are worth addressing on a business level? If you do this well, your problem statement will come across as an important problem that needs a solution rather than a solution looking for a problem. Sonya Natanzon covers great problem statements and gotchas in this talk: https://lnkd.in/ecz7uqvM

34

5 Comments

We were excited and intrigued by the TableFlow announcement by Confluent at the recent Kafka Summit London. It's great to see the Streaming Datalake concept getting the traction it deserves! In this latest blog post we highlight some of the considerations that come with the convergence of operational and analytical data systems and how the Streambased and TableFlow approaches differ, including: ⚙ Should you move/transform data for analytical purposes? ⏳ What (if any) latency is acceptable between operational and analytical systems? 📊 How should we surface operational data for analytical purposes? Please enjoy and, as always, join the discussion! https://lnkd.in/eMbgKn-f

12

2 Comments

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

Following our last article on containerisation, our newest more technical piece, written by re.alto’s development team, explains how to scale with Azure Container Apps and Apache Kafka. While such documentation exists for use with Microsoft products, our development team did not find similar documentation on how to scale containers using Apache Kafka and Azure Container Apps. We have therefore explored this ourselves and now want to share our knowledge with other developers who may be looking to do something similar. Learn more here: https://lnkd.in/dxPiwkJV #azurecontainerapps #scalingwithazure #azure #confluent #apachekafka #kafka #developer #dev #coding #devtips #containers #scaling #keda #kubernetes #development #containerapps #containerisation #realtoenergy #realto #scalecontainers #scalingcontainers #apachekafkatopic #microsoftazure

11

1 Comment

New blog post 🚀🔗 https://lnkd.in/dBi3fRsz ➡️ where Oliver Marshall explores all the ways to call AWS Lambda over HTTP 👉 click (... see more) for additional info ⬇️ 📌 What's Inside: - Setup instructions - Input/output formats - Unexpected behaviour - Practical experiments Whether using Function URLs, ALBs, or API Gateway, this guide will help you avoid common pitfalls and streamline your workflow. Check it out here: https://lnkd.in/dBi3fRsz #AWS #Lambda #CloudComputing #DevOps #TechBlog

3

Programming tests are: ❌ Often stressful ❌ Take-home tests are usually time-consuming ❌ Rarely representative of the approach and conditions of the job that they're testing for ❌ Many times online code testing platforms will penalise you for clicking away from the screen and sometimes they penalise you for any copying and pasting ❌ Usually theoretical "best practice" based - showing how you might do something if you were working in a vacuum, not accounting for business needs / interdependencies with legacy platforms etc ❌ Typically they favour those who have more recently come from education over more seasoned professionals ❌ In some cases the results are ignored or overlooked anyway if the candidate has done well enough in interviews rendering the test itself pointless ❌ In other cases companies take a "line in the sand", "computer says no" approach where even someone who is a known entity to the team or business will be rejected if they don't do well enough on the test   I have NEVER heard a developer say that they enjoy technical tests.   Some of the most senior, capable, accomplished developers I have worked with refuse to complete them as part of a process - particularly timed ones.   How often do you write code in a real life production environment with a timer counting down? And when would you ever want your team to not have access to Google or GitHub or Stack Overflow on a difficult task? A significant part of an Engineer's role is to research potential solutions critically, not to be a walking programming encyclopedia!   Even if your test is a less pressured, more representative take-home task rather than a recorded or monitored time-pressured task, they're not always that informative and they often take up a large chunk of time, which, particularly for someone who is currently in full-time employment and interviewing for multiple other opportunities, is a lot to ask. They also often lead to excellent candidates withdrawing from the process.   To quote a senior dev I spoke to the other day: "It doesn't matter how great the pay or the company or the work are. I'm a professional with over 10 years' experience, treat me like it. Don't set me bullsh1t homework"     👉 So why is it that so many interview processes use them? 👉 And what are the genuine legitimate alternative approaches to be able to ascertain someone's technical capability?   Keen to hear your thoughts Linkedin? Futura Talent #technicaltesting #techrecruitment #developerlife #softwaredeveloper #softwareengineer

8

2 Comments

🧑🏻‍💻🧑🏻‍💻 Dev communities are where you level up, share tips, and hang out with people who speak your language. And this is not the whole list. Being a part of the development community is much more than that. To be more specific, it's an opportunity for you to...👇🏻 ✅ Get advice and support from colleagues, and learn about the latest technologies and trends. ✅ Participate in joint projects, hackathons, and meetups where innovative ideas and sometimes startups are born. ✅ Meet other professionals who can become partners, mentors, or even employers. Here’s advice from the TRIARE team - get involved in dev circles, communicate, and share valuable experiences. Did you know that in the IT world, communities create the future? So become a part of it. #triare #triareteam #community #developers #teams #mobileapp #mobileappdevelopment #mobileapp #softwaredevelopment #websdesign

11

The Hierarchy of Power in the Tech Recruitment industry is about to change. TRIBES is that change. Talk to us about how we can help on all your tech projects. #developers #techtalent

1

Was playing around with the #Zed IDE from Zed Industries this evening. There's no Windows installer for it yet but you can compile it pretty easily. Yesterday I updated my #Rust toolchain, and with Visual Studio Community made sure the MSVC C++ build tools and Windows 11 SDK were installed. I let `cargo run` do its thing while I did other stuff, and when it eventually finished, it just launched without any build errors. Love that. Still early days though, it's not yet the most intuitive to use. I do like the docs as they are now, and also the familiar keybindings from VS Code. I wonder how easy a complete newcomer would find it though. The idea of built in #collaboration features for the IDE is great. I first saw this kind of feature many years ago in JetBrains #IntelliJ IDEA, where you could do things like viewing a colleague's session and diffing files against their local copy. I thought that was amazing! We've also seen it in recent years in Visual Studio Code and VS proper with #LiveShare. One thing these kinds of tools have issues with usually though is challenges within corporations - networking policies, proxies and firewalls, data privacy policies, etc. Having an ability to use an on-premise/local server for this would be nice too I think. As far as I understand, you can run a local collaboration version, but it's just a dev tool at the moment more than a product. The ability to follow collaborators is useful for #remotePairing or #mobProgramming. Channels with a side-by-side chat window, and note links to Markdown notes is nice. I haven't really used all the features fully, but I think it might support voice? Since COVID days I've wanted a way to combine something like Discord with Live Share or MS Teams, where you can enter a "room" with your colleagues/team, similar to being in an open office while working on-site, but now working remotely. Need a break, go over into the "coffee corner" virtual room and see what people in there are chatting or talking about - whether its collaborating on something, or just socializing. Need to have a quick team breakaway discussion, use another room/channel. Having AI as another "collaborator" in the IDE is of course nice. Interesting to see the support of multiple language model integrations too. I've recently been wanting to get back into the command line world as a primary environment, and like that it has built in vim emulation (yes... I'm finally wanting to figure out how to be a vim power user... maybe). Glad to see there's a #csharp extension, as well as an #asciidoc extension, think I might be testing those pretty soon :) Looking forward to not just playing around a bit, but trying it out on a proper project, to see how it performs. zed.dev https://lnkd.in/e5Shjx8P

2

Top tip for "No Code" integration solutions: Only use them if it can be done internally (i.e. someone in the business is has the technical ability to build and manage them) and the monthly platform bill is < £500. If you are paying a third party to build no code integrations - you may as well get them custom built so that you avoid the high ongoing fees and scalability issues that come with a no code platform. As the business scales you'll reach a point where it is more cost effective to do this anyway.

4

Balancing ambition with feasibility in software development isn't easy. Here are 5 pieces of advice to help plan features effectively: 🌟 Prioritise User Needs Over Cool Features. It's tempting to add the latest tech. But does it solve a user problem? Focus on features that provide real value. 🌟Start with a Minimum Viable Product (MVP). Launch with core functionalities. Gather feedback. Iterate based on real user input. This reduces risk and aligns the product with actual needs. 🌟 Set Clear, Achievable Milestones. Break down the project into smaller tasks. Assign deadlines. Celebrate small wins to keep the team motivated. 🌟 Balance Innovation with Stability. Innovate, but don't sacrifice reliability. A stable product fosters user trust. Test thoroughly before releasing new features. 🌟 Communicate Transparently with Stakeholders. Keep everyone in the loop. Share progress, challenges, and changes. This builds trust and ensures everyone is on the same page. Remember: Ambition drives progress, but feasibility ensures success. How do you balance ambition and feasibility in your projects? Share your thoughts!

294

41 Comments

The 2024 StackOverflow survey is out, and for the 8th year in a row, Clojure has ranked near the podium in the Top Paying Technologies category—often occupying rank 1. I don't talk much about why I choose to use a weird Lisp—mostly because nobody cares—but the results speak for themselves. If you can hold your nose long enough to learn something very different, you'll find yourself in a high-productivity environment that features: 🔥 Hot code reloading 🦆 Dynamic typing ♻️ Best-in-class garbage collection 📂 Highly performant immutable data structures 📚 Access to the entire JVM's ecosystem of libraries 🧩 Cross-platform compilation to JavaScript 🧠 An unbelievably smart and humble community Sure, you'll pay a high mental price to learn the language, but as a reward, employers will pay a high price for *you*.

72

47 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

🚀 Code quality matters! Whether it's fixing bugs, optimizing performance, or aiming for perfection, ensuring high-quality code in mobile apps is crucial for delivering the best user experience. I loved this article from Stack Overflow about the challenges and strategies for pushing code quality in mobile development. A must-read for developers looking to refine their craft! Check it out here: https://lnkd.in/dNGeJ2EW What are your go-to strategies for maintaining top-notch code quality? I'd love to hear your thoughts! 💬 #Tech #TechRecruitment #ProfessionalDevelopment #CareerGrowth #CareerInsights #Networking

19

1 Comment

I just wanted to mention the release of clj-uuid 0.2.0 with support for RFC-9562 https://lnkd.in/eKgiTtvP which updates the older RFC-4122 with new features and recommendations. What does this mean to you? Primarily, this means support for two new UUID types: v6 — a fast, time-encoding, lexically sortable, unique identifier. This is a field-compatible version of v1, reordered for improved DB locality. v7 — unix time-encoding, lexically sortable, index-friendly UUID with randomized monotonic counter, and cryptographically secure random portion. As such, creation of v7 UUIDs may be slower, but have improved entropy characteristics compared to v1 or v6 UUIDs. This release is fully backward compatible with also some improvements and bug fixes, so I’d recommend all users upgrade to [danlentz/clj-uuid “0.2.0”] If interested, please read on at https://lnkd.in/ejDar5zn #clojure #uuid #rfc-9562

7

1 Comment

Thought id share this great little code snippet by CodeWithVed on local Kafka ops management, their approach using client properties for IAM auth is spot-on (saved me from many auth headaches). Simple but yet straightforward CLI commands for topic management and message handling - especially useful when you need to quickly validate consumer group behaviours. #observability #kafka #aws

1