We will do that now. We will start the competitive bidding process, and we expect the RFP paperwork to be returned by October, 2021. After that, if there are no injunctions filed because of the bidding process, preliminary design documents will start being created. Preliminary design review will occur August 2022. ...
Seriously I worked on projects subject to government scrutiny and it was ok, but you had to be the right kind of person.
Account for your time in 6-minute increments. Milestones I recall off the top of my head were preliminary design, detailed design, 3-5% of your time coding, software integration, hardware software integration, acceptance.
It was stable, predictable, and (to me) very soul-crushing.
Technical question for you, how does this time tracking work in practice? Do you pause every 6 minutes and note what you’re doing? Or just roughly remember at the end of the hour/day?
You had to charge each project you worked on and record your time to .1 hour precision.
So recording 1.1 against project 3456 would charge that project for 1 hour and 6 minutes of your time.
You had to do the same thing for a dentist appointment. 1.0 hours for an "overhead project".
(I should mention this was years ago)
Also, lots of the people who worked there were ex-government employees and were fine with it, because software folks got to go home to their family every day at a predictable time, you would get training at regular intervals and although the pay wasn't super competitive it was a good job, indoors and in an air-conditioned office.
It becomes a reflex. Commercial lawyers all do it, tracking time this way is a fact of life, not least because if you end up in court arguing about costs the judge is going to throw out hand-wavy "I spent about a week on this" claims from professional lawyers who should know better.
I vaguely recall part of it was that you had to sign your timesheets. It's been a long time, and I'm pretty certain things have gotten better. It was harder for me as a young software guy out of college to accept 3-5% only of your time was coding.
> Why isn't there a whitehouse.gov ActivityPub instance that no single admin can censor or subvert?
Legislation is sorely needed for public institutions to make public announcement messages (microblog posts, or "tweets") using publicly managed and controlled infrastructure, contributing back to the commons[1].
Stop building into broken commercial services, the standards exist today to rebuild a commons-oriented Internet.
This. Just as surely as email, texts and tweets are now admissible in contract law and as we can sign documents online that are binding, we need a national realtime information-streaming infrastructure --text and URLs today, multimedia in the future...all over the (hopefully) secure domestic 5G network. Set the standard, setup a court system for inevitable violators, regulate the gateways allow everyone to connect.
Because the general public has no clue what ActivityPub is or the desire to learn how to consume feeds from dozen of instances when they could just download a single app onto their smartphone where all the celebrities already are.
How do you propose people consume 100s of different ActivityPub feeds without learning the details of how to configure an app to do so, while also staying away from a centralized platform to make it easy to consume the feeds?
