I think that should look like this: HMO style access for all - automatically. Rebate if you decide to up it with PPO style insurance (or beyond). So you get 200 per month off taxes to pay towards your own insurance.
Also, get it out of the employers hands - as in make it illegal to offer any benefits and let the employee get paid 100% of their salary instead. Also make it so that employers can't legally collect taxes without consent.
Definitely agree. If I ever did get brilliant one day and make something useful or simply exist, I don't think I would post it here. Inevitably the comments would scar me.
I get that founders quickly learn to get past that stuff, but I'm probably too much of a softy.
We moved EVERYTHING to Teams and ADO (for git, backlog, pipelines) except our actual product is still on AWS. If we didn't have a couple things like encryption, S3 and some fargate usage, we'd probably start fresh on Azure.
I got through the second paragraph. I probably made 10 mistakes. Very nice interface.
My only thought was - if I suck at typing, learning it, it's going to be very discouraging getting through just one page. I wonder if it would be better to display just a paragraph at a time. Also as the user finishes a sentence without mistakes to give them a visual reward (kinda like one of those cheap mobile games that shows stars or something). And another reward for finishing a paragraph.
Other than that, I am guessing this will likely help a lot of people learn to type or type faster.
Is software just too easy to write that everything becomes incompatible. Everyone has the next best idea. It's XKCD 927 all the time.
Now if you instead look at Trucks and Campers, Rear Hitches, Fifth Wheels Hitches, Goose Neck Hitches. Every truck you can buy on the market today (with some strange exceptions Cybertruck cough) has very simple compatibility with all of these various trailer types. Yes in some cases you have to buy a mod kit, but when you look at the mod kit it literally bolts into pre-drilled holes in your truck frame. It's all plug and play.
I feel like the reason it's like this is because no one person can go off and design a truck in the dark. It's designed by many people and is beholden to customers.
Software, on the other hand, just gets built by whoever wants to build something. It doesn't have to fit some kind of standard. And it's not like there are a lot of standards that already exist in whatever it is that the software is doing.
In the real world however, you have Kubota tractors that need to fit a CAT bucket.
I'm trying to parse this - are you saying it was the killer feature that convinced you to be a customer, or the lack of more detailed information of the user that "killed" your interest in the product?
> You set goals, you decide what happens when those goals are met. Furthermore, there is no concrete assertion here that what happens if this deadline is passed. "at risk of losing funding" can literally mean anything from changing FTE allocation to capital expenses to a million other things that get discussed at an executive level.
No customer is going to sink risk into a statement like that. Everyone wants to know that the investment increases and only increases.
Definitely agree here. I have a 2014 MBP. I can't let go of it. Last year I bought a brand new laptop with Windows 10 on it. I definitely think it is a major improvement over all Windows since XP (better than XP of course too).
I told myself I have to eventually migrate... still hasn't happened. There's just no reason to dive into horrible Pythoning, Dockering, NodeJSing (do I have to bring up Node-Gyp?)
For development Windows has a long way to go, even with WSL.
Maybe the fix is to require the submission to include the timestamp start and end. And if there is also copyrighted imagery, that the submission include black boxes around the restricted imagery (for video imagery the would include the timstamp start and end).
Then, the resolution would be to wipe out the original audio and black out any imagery similarly. Thus if a car drives by playing something copyrighted, it would simply cut the audio for a few seconds. No loss of revenue to the original poster. And beyond that, provide the video poster a chance to edit the video without the original sound/images. If they re-upload it with the sound/images still included, then they can have negative consequences for their account. If they re-upload with everything "fixed" then they shall have no negative marks on their permanent record.
We're doing this exact thing. Our micro front ends are React components (most of them are actually now using hooks!). Our 2 deployed UIs are angular (1!!!) apps. We use react2angular to slowly replace the angular app. The angular components are all Java backed using a poorly maintained swagger set up (and the swagger definitions don't match the actual services :( ). The new backend is all Graphql on top of typegraphql. The nice thing about typegraphq is how easily it converts our models into usable rest services, and allows us to create field resolvers, that basically extend other types and let us pull down additional concepts. Basically we let the front end then choose what it wants to pull down. It's very flexible, self documenting, and reduces the amount of boiler plate we had in in the Java layer a ton. One set of model objects (typeorm) that also have typegraphql decorators. Compared to Java that has models, swagger objects, converters (both ways)... Life before was literally a nitemare.