Niek van Asperen

𝗖𝗼𝗻𝘁𝗶𝗻𝘂𝗼𝘂𝘀 𝗗𝗲𝗹𝗶𝘃𝗲𝗿𝘆: 𝗬𝗼𝘂𝗿 𝗦𝗼𝗳𝘁𝘄𝗮𝗿𝗲'𝘀 𝗙𝗮𝘀𝘁 𝗧𝗿𝗮𝗰𝗸 𝘁𝗼 𝗦𝘂𝗰𝗰𝗲𝘀𝘀💥 Imagine launching new features and updates not in weeks or days but within hours of development. Sound impossible? Not with Continuous Delivery (CD). At EEnexus, we're not just automating the release process – we're engineering a competitive advantage for your software. 💪 The CD is about more than just speed; it is also about reliability and responsiveness in a market where delays can be costly. 👉 Here's the EEnexus CD difference Research tells us that most change efforts fail. Yet change methodologies are stuck in a predigital era. It’s high time to start catching up. https://lnkd.in/gzx43VP At EEnexus, we don't just help you keep up with the competition; we help you leave them in the dust. Our CD solutions empower you to: ✅ Reduce risk ✅ Boost morale ✅ Deploy more often Ready to transform your software delivery process and accelerate your business growth❓ ♻ Connect with EEnexus today, and let's engineer a brighter, faster future together. https://www.eenexus.com/ #continuousdelivery #devops #softwaredevelopment #automation #techinnovation #eenexus

4

State management is a challenging software engineering topic. State creates dependencies, and dependencies create complexity. Therefore we need to understand how to manage state. I recently heard someone say that we should aim to remove all raw for loops from our C++ codebases and replace them with std algorithms. At first I didn’t grasp his point, but I soon began to realize that he was trying to explain that raw for loops expose state. We don’t want to expose state, instead we want to encapsulate and manage state. Managing state was the topic for my talk at the Audio Developer Conference ‘23. In this talk, I share my thoughts about it in the context of JUCE (a C++ audio software framework) applications. In audio software, we have to deal with different forms of state including global settings, presets, UI state, and application state. State must be stored and restored and must be synchronised throughout the app across different threads (at least the audio and main thread). State sometimes needs to be synchronised with other software, such as a DAW (Digital Audio Workstation). There is a lot of debate about how to solve all these problems, and I’ve seen a lot of people do this in different, some good and some bad, ways. How you do it matters. It all starts by knowing the JUCE framework and understanding the fundamental JUCE objects, including the AudioProcessorValueTreeState, ApplicationProperties, Value and Vars. Knowing these objects will help you to build up a state system that suits your application. You can watch my talk now on YouTube! Go ahead, watch it, and feel free to send me a message with any question or comments afterwards. #softwaredevelopment #juce #audio #c #plugins #statemanagement

20

We’re getting close to typing some C#! We’ve described our components in plain language and listed their dependencies in the Architecture documents. At the very end of the stream, I talked a little bit about Contracts in software development, and why they’re important. We’ll talk about that some more this afternoon. The stream is archived in the usual place, I’ll link it in the comments. See y’all at 1:00 pm eastern over on Twitch! #thatDeveloperDad #liveCoding #softwareArchitecture #cSharp #dotNet 

1

1 commentaar

Resharing this as endorsement - tech compensation is *at least* bimodal, and likely trimodal (depending on your location). This article is a great read for all engineers, to help explain the market and know their worth. I saw this firsthand in my job search last year. There were local companies in the Chicago area that capped out at ~120-160k for senior roles, and then larger firms (especially in finance and tech) that reached ~180-200k. But it wasn’t until I got into interviews with large public tech companies that I saw base salaries of 200k+ advertised, and total compensations reaching from 250k to 500k and up! Gergely Orosz's articles on this topic have been a huge help to me. If I had stuck to what I saw in the local market, I would've drastically limited my options and short-changed myself. The surge in remote work has made it more possible than ever to work for some of the best companies in the world, and even with lots of return-to-office happening, there are still plenty of great and well-paying companies out there. So if you're on the market (or thinking about it), keep this in mind! 🚀

4

Talking within our team about how finding proper abstractions will often (always) make code structure just 'click' I remembered the share-pie story from DDD - and luckily found this https://lnkd.in/dzZfVngd . It is also, what I remember most from the book.

3

2 commentaren

In 2021, I tried to understand how tech compensation really works - at least in the Netherlands. I published "the trimodal nature of software engineering salaries" article. Time for an update: Back then, based on ~100 data points (and my own experience as a hiring manager,) I suspected that there are three, distinctively different compensation bands for software engineers: 1. Local companies (Tier 1) Most local businesses that benchmark to the numbers on most salary comparison sites. They usually offer close to – and sometimes slightly above – what government positions advertise for senior engineering roles. 2. Ambitious local companies (Tier 2) Startups, scaleups, and more ambitious local companies that want to hire and retain the best people, locally. 3. Companies benchmarking across a region (Tier 3). Big Tech companies, hedge funds and scaleups that hire across regions, frequently hire from abroad, and often compete with fellow Big Tech giants for talent. Curiously, the third tier (Tier 3) seemed to be missing from most public compensation data sources. Since publishing the model, I've both received lots of feedback suggesting it applies to the US, Canada, UK, Europe and many other countries. I've since then also collected far more data points, manually tagged companies by tier, and can finally confirm that yes, this model holds up when compared with actual data. Here is the longer analysis (and the stats behind this graph below) in yesterday's The Pragmatic Engineer issue. Read it here: https://lnkd.in/e7FV4gBB

688

43 commentaren

Selecting the ideal container cluster and orchestrator platform for your organization can be an overwhelming task. However, you don't have to worry anymore. We have conducted a quick comparison between Kubernetes and Docker Swarm, which will assist you in determining the most appropriate option that caters to your organizational requirements. Our comparison encompasses various essential aspects that will help you make an informed decision. https://lnkd.in/gBMi7Y7D Giving back to the open source community - A sloopstash initiative. #kubernetes #docker #dockerswarm #devops #container

3

Ready to see Jonas Geiregat in action again? Join us for an Apache Kafka® meetup on Tuesday the 21st of May. 📍 Jonas, one of our Senior Software Engineers, will have a talk about Kafka Streams. This talk dives deep into the practical applications of Kafka Streams from a Java developer's perspective. He'll explain how to leverage Kafka Streams to add real-time processing power to your applications, how to test it and he'll discuss the key considerations when choosing Kafka Streams over alternatives like Apache Flink. Care to join? Be sure to register in advance: https://lnkd.in/dgZuqFyg #eda #eventdrivenarchitecture #apachekafka

19

💻 Boost your software development with effective backlog refinement Backlog refinement is crucial for succesful software projects. What is backlog refinement? In our latest blog we dive deep into this process and share practical tips for a successful implementation. Read our blog and discover how you can take your team to new heights! 💡 Check the full article on our website: https://wllw.co/6G1O12TVk!

6

Developers these days are so darned lazy. And cheap. OK, sorry, that was not fair. Developers have always been lazy and cheap. I was really surprised by this when I started out as a software developer, fresh out of college 25 years ago. I noticed that whenever my more experienced colleagues were asked to add new functionality, the first thing they did was to check if there was pre-existing code that did the job. Preferably free. This blew my mind. But as I thought more about it, it made sense. Especially after I attended a Business Strategy class at Southern Methodist University SMU Cox School of Business. Build vs Buy vs Reuse is a part of Business Strategy. Why build or buy something if it is freely available? When we start with something good-enough that is freely available, we can customize it to our needs. And if it is well-maintained, we get free upgrades. This frees up more time and money for us to build things that no one else can build as well as us, which makes customers very happy. It reduced the TCO (total cost of ownership) of our solutions and it increases our EBITDA, which usually makes investors very happy, which makes the board of directors very happy. So it turns out that developers are not only lazy and cheap, but they are also strategic and there is a lot we can learn from them. Especially when it comes to building Software Product Development Lifecycles. You may be tempted to reject the pre-existing frameworks and build your own because none of them are good enough for you. Newsflash! You might think you are unique and special and nobody is solving the specific kinds of problems you are. Maybe yes, maybe no. You are just as unique as every other snowflake. And while you might be doing something nobody else has done before, you don't need to develop your own SDLC. Think like a developer. Be lazy, cheap and strategic. Start with a pre-existing framework, make use of all the free training available on the market, and customize only what you need to. Your EBITDA will go up and your customers, investors and Board of Directors will be happy. You are welcome.

14

4 commentaren

My talk at #FrontendNation is available in full length on youtube. Let me know what you think.👇🏼 https://lnkd.in/e_GBNXTv I will post a link to an automation guide of my talk as comment. In this blog post you can also find the slides. ✅ #a11y #FrontendDevelopment #wcag #WebAccessibility

32

2 commentaren

Aarrr! Check out Gijs' post where he talks about implementing continuous integration for machine configuration packages with build automation tooling. Gijs explains how to utilise build automation tooling to automate the configuration package creation process and integrate it with a continuous integration pipeline. By doing so, it can save time and reduce errors that may occur during the manual configuration process. This post is a great resource for developers who want to improve their machine configuration processes. #ContinuousIntegration #BuildAutomation #ConfigurationPackages #Azure #OpenAI #TheCloudPirate 🚀💻 Author: Gijs Reijn. Author's Social Media Links: -X: https://lnkd.in/eGd4wi_2 -LinkedIn: https://lnkd.in/eMiSQgT7 This summary was created using the Azure OpenAI Service and Azure PaaS.

1

𝐉𝐚𝐯𝐚 𝐍𝐞𝐰𝐬 𝐑𝐨𝐮𝐧𝐝𝐮𝐩: 𝐏𝐫𝐨𝐣𝐞𝐜𝐭 𝐋𝐞𝐲𝐝𝐞𝐧 𝐄𝐚𝐫𝐥𝐲-𝐀𝐜𝐜𝐞𝐬𝐬 𝐁𝐮𝐢𝐥𝐝𝐬, 𝐋𝐚𝐧𝐠𝐂𝐡𝐚𝐢𝐧4𝐣, 𝐉𝐑𝐞𝐥𝐞𝐚𝐬𝐞𝐫, 𝐆𝐫𝐨𝐨𝐯𝐲 𝐏𝐫𝐨𝐣𝐞𝐜𝐭 𝐋𝐞𝐲𝐝𝐞𝐧: 𝐄𝐚𝐫𝐥𝐲-𝐀𝐜𝐜𝐞𝐬𝐬 𝐁𝐮𝐢𝐥𝐝𝐬 Project Leyden has recently released its early-access builds, sparking excitement within the Java community. The project aims to improve startup time, time to peak performance, and footprint. These enhancements are crucial for applications requiring fast launch times and efficient resource usage. The early-access builds offer developers a glimpse into the potential improvements and provide a platform for feedback and testing. 𝐋𝐚𝐧𝐠𝐂𝐡𝐚𝐢𝐧4𝐣: 𝐑𝐞𝐯𝐨𝐥𝐮𝐭𝐢𝐨𝐧𝐢𝐳𝐢𝐧𝐠 𝐉𝐚𝐯𝐚 𝐃𝐞𝐯𝐞𝐥𝐨𝐩𝐦𝐞𝐧𝐭 LangChain4j is making waves as a revolutionary tool for Java development. It simplifies the creation and management of language chains, making it easier for developers to implement complex language processing tasks. With its intuitive API and robust features, LangChain4j is set to become an indispensable tool for Java developers working on natural language processing projects. #SoftwareDevelopment #TechIndustry #SoftwareSolutions #DigitalTransformation #SoftwareEngineering #Innovation #Technology #SoftwareDesign #SoftwareArchitecture #Coding #SoftwareTesting #SoftwareUpdates #SoftwareTools #SoftwareDevelopmentLifeCycle #SoftwareAsAService https://lnkd.in/dpHBCumX

1

Testing Platform Update: We have a test results explorer! Goal Tracker: ▪▪▫▫▫▫▫▫▫▫ 20% of the way to 120 tests in 24hrs We're calling this "Testing Taxi Results". Like you would expect, it's got a list of tests, individual step details, test history and easy to view screenshots. Is there metrics/info I missed? #testing #testautomation

3

At Evoluted | Certified B Corp™, we've been using GitLab as our DevOps platform for years, and it's been fantastic. But as our Shopify client base has grown, we faced a challenge: no built-in GitLab-Shopify integration. Many developers solve this by building custom solutions. That's what I did! Over the past 6 months, I've developed an integration leveraging GitLab CI/CD and the Shopify CLI to automate theme deployments. Here's the benefit: Streamlined development workflows for Shopify stores on GitLab. It's not a silver bullet: This solution might not be as feature-rich as the official GitHub integration, but it's robust and ready to share. Calling all Shopify devs! Have you struggled with manual deployments? I'm sharing these scripts to help you improve your workflow, just like they've helped ours at Evoluted. Links to the full breakdown of the implementation: In the first comment. #shopify #gitlab #devops #ecommerce #cicd

20

2 commentaren

At PropelAuth, we think about our users in 2 phases: before the integration and after the integration. Before the integration, our main users are developers. Occasionally a product manager or designer will be involved to help make some decisions, but generally - it's developers. After the integration, the developers can often step away for long periods of time, and our main users become... everyone else. Customer support, customer success, sales, marketing executives - all are in the PropelAuth dashboard daily. They're doing everything from impersonating users to track down bugs to checking out our user insights to make sure they're hitting their goals. They can get their jobs done without needing ask a developer for help. It's not enough to have an easy to use auth product - we need to make sure that everyone at the company can work with user data they need to drive growth.

21

What-if questions can be powerful or wasteful. How do you know if you’re using the question right? I was working with a developer recently. We were on the hunt for a bug. After some initial analysis, we found several questionable things and one obvious flaw. But it wasn’t clear if the one obvious flaw was the only issue. We began to spiral into a series of what-ifs. We even started writing code to prove out the what-ifs. That’s when we realized we left *analysis* some time ago. Were well into the realm of *speculation*. We did a 180. We reverted the what-if code. We spent 2 mins fixing the obvious flaw. Doing that simple pivot cleared up most of the questionable things we were seeing at the start. The problem got a lot smaller. Avoid *speculation* what-ifs. Embrace *analysis* what-ifs.

1

🗣 The Importance of Effective Communication Long-term projects, particularly in software development, are complex processes where precise and timely communication is indispensable. Misunderstandings or gaps in information can easily lead to mistakes, delays, or even cost overruns. Now I will briefly introduce the communication guide we use: 📩 Email: It is ideal for sharing important decisions, formal confirmations, and official documents. 📲 Call: Personal encounters or online meetings are also essential when discussing more complex topics or urgent problems. 📳 Other Platforms (like Slack): Instant messaging platforms are excellent for everyday communication, quick questions, and information exchange. We discuss the topic in more detail in our latest blog, which can be found in the comments! 🔽 🔽