343 karma · joined June 6, 2022
so yes. it would still be lower.
this is why all enterprise software sucks
it seems like its basically "If you get money from lying electronically, go to jail"
by putting login, they can throttle or block it entirely.
Basically though, more carbon needs to go into the ground than the air. AA (in this specific instance) is pushing carbon in the right direction.
Software development to me is a financial investment strategy. Some risky investments, some safe bonds, some good debt to invest, some bad credit card debt that will be cleared later.
To me, these are the same as a risky overhaul of a critical system adding some automated tests, skipping some type annotations, or launching what was supposed to be a demo/MVP to be first to market.
a piece of software that took months to build could be worthless tomorrow if a competitor comes out with a better solution. There's a time value and strategy to it.
speeding up development with CD lowers the investment cost & time to market of an individual strategy. Automated tests lowers risk. Feature flag & AB testing diversifies the portfolio.
One line of code be the most valuable piece of a product, like Doom's Fast Inverse square root. and millions of lines of code could be worthless.
the value of a software engineer's work is extremely contextual. Two automation can be structurally the same, developed by the same person, written in the same language, take the same amount of time and resources; and still be COMPLETELY different in value.
until IT/software strategies are treated like an investment strategy, companies & leadership will continue to flounder when managing technical teams.
the other benefit of a statemachine is the ability to accurately determine what parts can be collapsed into subworkflows which allows for reuse, replacement, or general modification
honestly, when working with some new archaic system, the ability to insert manual tasks is invaluable for an early deployment
Basically every ERP technology every invented.
so did unity, until they removed that clause
thats the SaaS business model. first hit is free, then they take your money
I'd rather see them do 1 method very well than 2 methods haphazardly
the sudden shift is jarring, especially if the content is staggered
The economics and tactics around technology has been revolutionized a dozen times over in the last 4 decades. Now, maybe a few rare individuals have kept up, but most likely, they all rely on outdated strategies from out of touch MBA programs & buzz words.
Its the same reason the market kills public technology companies' innovation and they rely on acquisition.
Its like gunpowder has just been invented and leadership still wants large formations marching against each other. "what if we invested in medical training and add washing our hands so we can keep more people alive?" "nah, more guns and marching"
but it could just be a yml file. In essence, the requirements section says "here are the builders it needs & their versions" which identifies types of jobs. each entry is a job with a job type, a unique name, and some config info. Each builder is just a series of CRUD operations.
Like you said, it builds a directed acyclic graph, queues up the ready jobs, and executes them. updating the infrastructure's "state" with info from the completed jobs & adding new jobs when their dependencies are finished. the state files are just a dump of that structure as json.
Its not thathard. I think of myself of a junior level dev and I built something for me in my side time in a month with a full test suite and its 3/4 of the way there. CLI, builder dependency injection, type checking, relationship dependencies, it took me a few weekends
I think a senior engineer could build out an enterprise grade functional core product in a few weeks. building & maintaining the CRUD APIs is the real headache, but I think vendors would take care of that themselves if there was a popular enough OS solution.
its so many things and so complicated.
Junior engineers need help as the same rate they did before. They still need to ask for help. Remote work lets it:
- happen asynchronously & synchronously
- creates visibility of asking for help
- reduces this weird shame around it
- allows us to correct bad answers
- allows people to learn from others with the same questions
- self manages by capacity because the people with time are the ones that can answer questions
- produces an awesome collection of analytics: how many & what questions are being asked by who, Who is answering questions and about what?
Remote work is a communication and cultural change that a lot of teams have done poorly. I think most teams decided when the pandemic hit: "oh we'll use teams or slack. That's enough" and never thought more about it.One metric that I learned about was the impact of American diet on immigrants. Women who grew up outside the US, especially from asia, are smaller. When they came to the US, the high caloric diet usually lead to significantly higher rates of C-sections as a result of their larger babies.
Poor base health, doctors fleeing anti-choice states, lack of access to care, lack of parental leave, economic stress, inactive lifestyles, and now throw in country wide heatwaves.