That is very likely an option, but probably not used a lot. I have worked with several people that had a similar schedule, but they did not start at the company with that schedule and of course took a pay cut due to the lower hours.
It is very difficult to argue for hiring someone that is not 40 hours. HR and management thinks in terms of full time (40) or part time (<30). The 30-39 hour schedules seem to be used to keep someone they really don't want to lose and not offered to new people. I have seen it with people getting close to retirement and people caring for someone sick or small.
Roman concrete is not like modern concrete. The process in modern concrete does not stop and eventually makes it too brittle and falls apart, Roman concrete does not do this and can last a very long time.
Well, the manager is not supposed to be there. A scrum master is supposed to keep it organized and time boxed, but the team is supposed to self police/organize themselves.
It's supposed to be like a restaurant where all the waiters share tips. It is in everyone's interest that one, all customers are being served well and two, that all waiters are pulling their weight.
Since this is not a public service, then no rationing is not bad. In the US, a lot of the homeless shelter are faith based and each only have so many beds to go around each night.
There are not more since someone has to put up the money for the investments. And entrance fees would not likely work for anything new and not novel. Only the government can spend more than it makes.
You have to pass a driving test at age 16 (in US), after that you never need to test again (sometimes eye checks when you are old), cause um... nothing changes about driving or cars or rules in the next 64+ years it would seem.
Telsa is only a level 2 self driving car, but it has been sold as something way more advanced (Telsa has since pulled back some of the hype). A lot of people don't understand that there are even levels at all.
You have to first fight the battle that you do not own the software, but that you only have a license to use the software. If you win that, then you can fight for repair.
No difference than Excel Macro apps today. When Excel Macro wiz kid leaves the department or the company and it either breaks or needs new features then it goes to IT and they don't work on Excel so they will push to rewrite it into a web app.
The plus is that the use case and value for the program is already proven, so IT is not wasting time creating things people will not use.
It was also an issue of the speed of capture. Paintings and old Cameras had long exposure times so you needed a pose that you could hold for a long time.
Dependency weight is more a factor for maintenance than initial development.
The apps I write I have to support for many years, so this dependency weight does concern me. By dependency weight I am more referring to the breadth of authors/maintainers and not the actual amount of code. When working in the Java/.NET worlds you still deal with a ginormous amount of dependency code, but they are one maintainer that is funded. The downside of monolithic dependencies is lack of flexibility and vendor lock in.
"Whatever limitations you plan for, plan for how to bypass them too. This will happen."
The world is not straightforward, allow an admin to fix/change anything and when they get tired of making some change then code that new path in the system. Working with or writing systems that do not allow admin overriding is painful.
It is very difficult to argue for hiring someone that is not 40 hours. HR and management thinks in terms of full time (40) or part time (<30). The 30-39 hour schedules seem to be used to keep someone they really don't want to lose and not offered to new people. I have seen it with people getting close to retirement and people caring for someone sick or small.