brixon
brixon on Hacker News
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.
Stand ups are not for top down management or managers.
Daily Scrum Meeting aims to support the self-organization of the Scrum Team and identify impediments systematically.
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.
Agreed, views against stand ups are either team members hiding issues or the team is not doing stand ups like best practices suggest.
Most of my teams problems with Agile/SCRUM come down to skipping steps or not following best practices. Once we fix those, it gets better.
"Show up for 15 minutes, and then it’s safe to hide for the rest of the day."
Lack of stand ups makes it safe to hide for multiple days.
Short of reading the Shape Up book (which I will probably do), the article is weak in action and reason.
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.
The purpose of entertainment is to keep the masses from revolting during idle times.
They will sunset it without something new to replace it.
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.
They are a consultant, so they just move on to the next client and let the perms deal with the politics.
InfoPath is end of life and PowerApps is their replacement.
Yes since it is describing more what you want and less how to do it, but SQL is not an end-to-end solution.
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.
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.
I try to use the rule of after three levels of inheritance or abstraction then it needs to be a black box and then you can reset your count.
That is only a concern for medical grade masks. Most masks that people wear are to slow down the air, not filter the air.
One of the big issues for these kinds of things is that the United States has 51+ governments. The Federal Government has limited power and for a lot of stuff the 50 states can do their own thing. The Civil War did move more power to the Federal Gov, but the States are still very independent.
For non-tech people they think the exact opposite. Facebook is a name they know and understand.
The Accounting department is usually backwards facing. The Finance department is usually forwards facing.
It is worth a study since the trees needed for ships (hard woods) is very different than trees needed for construction/paper (soft woods). Pine trees grow fast and can be harvested while relatively young and weak. Trees for ships tend to be older and stronger hard woods that take much longer to grow.
installing apps is another thing that will be watched and limited. a one line powershell script will do this and would be less noticeable since the system and admins run powershell stuff on the computer everyday anyway.
For the "rudderless" and "self discipline is hard" parts, that is one reason I am glad our team is doing Agile/Scrum. Just the daily stand ups give you enough accountability to have a goal to shoot for.
evolution and rapidly don't go together.
Did you count all incidents or only the ones that happened in real life and not the simulations?