The role of the Architect in an agile delivery group is a crucial one that is often misunderstood, with its importance understated. But architecture is critical to the success of any software project, and even more so in an Agile software team, as the Architect has additional key roles there.
The current crop of generative AI (ChatGPT, Dall-e 2, etc) may be a blessing for individuals, but they could prove a pestilence for our civilization in the short term. For every door they open, it seems to me they also threaten to wipe away whole towns of visual artists and copywriters. And as consumers of information, we are doomed to be overwhelmed, our attention span drowned in torrents of content. Our eyes and minds will be overfull. Our time will be drained away by too much being said too well, and sharing platforms that monopolize our attention too well.
There are many software systems that can help your business grow and succeed; many of these have undergone capitalization and become well-known Software as a Service (SaaS) offerings, while some are open source software systems you can freely download, modify and host yourself. It is increasingly rare to commission and run software systems built to your specifications by software artisans. You might be asking yourself whether to pay the subscription costs for a SaaS product, or if you’re better off putting in some development and deployment work to host and support your own in-house systems. Well, there is a secret benefit to using SaaS solutions that makes it more appealing for nearly any use case, with one glaring exception where it makes more sense to run your own servers.
Every discipline and every niche has a “Swiss Army knife of X”. Why are they so prevalent, and what makes them so valuable to engineers and software developers?
In my last post, I described the initial phase of determining the trajectory for a greenfield softtware project. Once you have established your vision and created a roadmap, the next step is to decide how the software system is to be built. This involves finding a suitable architecture for the system and devising a macroscopic design of the different components and interactions involved.
If you’re a technical leader overseeing the development of a greenfield software project, then you know how crucial it is to get the design right.
In this article and the next, we’ll explore how to approach the initial technical modeling of the system. We’ll look at some of the best practices for making critical decisions to establish an efficient development plan that will lead to maximum system quality and reliability. We’ll cover concepts such as the high-level characteristics of a system, user story maps, and what product roadmaps should look like.
Business startups face many different and complex challenges, and all of them threaten to slow down or break momentum during the challenging initial stages of business development. Luckily there are a variety of approaches, techniques, and tools available in 2023 to help you get started, bust through barriers, and break stalemates. From using services provided by others to adopting process changes that build good habits from within, here are the four biggest blockage-breakers we have used at Opreto in 2022 to keep our business moving forward.
As a technical leader, you must make software development decisions that minimize risk for your company, and doing nothing may seem like the safest path. However, sometimes the risk of doing nothing can be the most significant. So, how do you know when to take a leap and go for it and when to hold steady?
You’ll often hear about the importance of getting started, breaking ground, getting moving on a thing. Whether you have a specific goal you want to achieve, or you just want to get your feet in the door of a particular industry or technological stack, the outlook from a thousand feet can be daunting. So how do you choose where to begin?
How do you help someone solve a problem if you don’t speak the same language? You learn their language and teach them a bit of yours. Without a shared language, you won’t understand the problem, and your solution may not end up being a fit. You are endangering the entire project. Read on to find out how I establish a shared language with new clients.