with LLMs in a few years software would be a low level thingy that people used to spend hours writing and debugging. like assembly back in the day. software is becoming more and more cheaper to put in place. craftsmanship is in the product and value not in the software itself. we are in an era: adapt or get out ...
Switched to an AI team 8 months ago. Ended up doing infra and api integration for llm tuning which is a nice way to start ramping up to the field. With every integration learned new things: Lora/pets, spin up servers to host the models for inference/tuning. It's a lot of learn on the spot compared to concepts from SWE life.
I had a very good experience using safe 4.x
The whole department participated.
Edge Software
Cloud platform
Application team
It allowed the 3 teams to have better communication, things were written, we knew what we are building and how/who is using it.
Met with stakeholders regularly for feedback and better understanding of the business in general, the strategy and why we need to land this feature either to differentiate or because it is priority 0 asked by many customers.
As a team member safe allowed me to understand why what I am working on is important for the business and how it brings value.
I wonder if it is a people problem that we are blaming safe for or an actual process problem?
Disagree.
In one of the companies I worked for. Management decided to adopt safe agile.
We had a dedicated agile coach for the whole department. Each team went to learn the safe agile principles and framework. The main focus was how do three teams get more aligned when building a solution: edge software, cloud software, application layer.
I can say after 3 months of sprints. The productivity improved, people were happier and now we know which feature is used by whom. The requirements were forced to become clear so it be translated into designs and then dev work with the definition of done.
When properly applied with the right intentions it is transformative.