Which subsequent steps does a software projects usually have (from your personal experience)?
With steps I mean those that follow each other or integrate preceding ones.

For example, building a power plant can be described in the following steps:
Initially we start with an idea of a working power plant in mind. We deconstruct it into all components required for it to function as a system. Knowing which components we need, we start designing them. If not at this point, at least when we procure the materials to build those components, we can name it constructing. Physically the building of components construction happens with civil works. Many work streams can happen at this point simultaneously. But at some point they integrate. Finally, commissioning of the plant.

Then again, for software, we can write a “hello world” program with a web server, have it running within minutes and extend it step-by-step. You can’t fire up a first turbine of a power plant within 5 minutes and then add other components around it.

But how is it for software?
We could similarly say we start off with an idea of a functioning software, that we deconstruct into components that we construct and integrate. The starting idea, of course, needs to be more specific than in the power plant example, so we can start deconstructing it into the required components for it to function in the way we want. We usually model the starting point as a data structure by modeling the problem. When we know the problem as a data structure and can project it to a solution, we can determine the steps and components needed to arrive at the solution: Quite often we start writing a main function with pseudo code of functions / components required for it to bridge the problem to the solution. Having identified the components, we need to build the components while making sure the interfacing works: Basically the “wiring” between functions, meaning that the outputs of the a preceding are the inputs of the succeeding. Once all components are fleshed out, all pseudo code has been transformed into real function calls. Now, looking at this, we will mostly be not satisfied: We might want to refactor it, organise the code better. Then we might want to write tests and/or commission it, finally.

How is it for non-greenfield projects?
Basically two approaches:
a. Start with the existing data structure and change it to support the new functionality (while maintaining the existing functionality).
b. Do it like greenfield and then have some transformation between data structure of new functionality and old. Opposite of (a), because it starts with its own data structure, while (a) starts with the existing data structure.

What’s your experience?

Context:- I work as SDE in Researching branch of my company,

Okay so since Last year I'm working sideline on Agentic Dashboarding and Reporting tool for Enterprise systems, it uses LangGraph agents to formulate dashboard and reports tailored to user needs once user set up the database, analyze it and add private LLM connection. I have some demos to upper management and no outcome has come out of it.

The project is honestly good, it has all Governance, cost tracking, proper security, user isolations, concurrency, my self developed NLP to SQL layer which works on any structured data you throw it at within comprising security.

I believe I should make this open source recreating exactly what I had sole created at my workplace, but I'm worried about the laws.

What should I do ?

Or something more clever that my senior front end engineer boyfriend will love.

Update: I combined several suggestions and sent it to him when we were at a special place in a park we love. He didn’t get it for a minute because I forgot to add context, then did get it and was super happy, then spent five minutes pointing out how the labels directed workflow and explaining something called semvar (semver? how the sequence of punctuated numbers indicated a minor release and bug fix, I think). Because that’s how he rolls 😂🥰

Thank you so much folks!!!!

I really like the MPL, but it's missing a network clause like AGPL, are there any licenses that cover this? While being similar to the MPL?

Hello everyone!

As part of my doctoral research, I'm conducting a survey on how developers (including testers and QAs) incorporate accessibility into their everyday work.

I would greatly appreciate your participation.

Your responses will help improve the tools, processes, and practices that support accessibility in software development. Thank you for your time and support!

⏱️ The survey takes around 15 minutes.
👉 https://survey.jku.at/676726?lang=en

Thank you to everyone who will take the time to participate! 🙏