steverb
According to this US News and World Reports site ( https://money.usnews.com/careers/best-jobs/waiter-and-waitre... ) the best paid 25% of waiters made $30,000.
I think you might be misremembering how much you made, or perhaps you weren't working in a run of the mill diner, because making 60K per year as a waiter 20 years ago puts you far on the right of that bell curve even without adjusting for inflation.
There might be something useful in the blockchain, specifically in how it seems to make a certain class of transaction easier/more reliable and there might be a good use case for NFTs in that space.
I really hate that the term crypto has come to mean 'crypto-currency' instead of cryptography in general.
Obviously there are some things that you should never try. Things that you find morally objectionable. Things that have too high a risk of death or permanent disability. Things that will keep you from fulfilling your responsibilities (wife and kids will slow you down). You have to do your own maths on those, but beyond that you should try as many new things as you can manage.
You will fail. You will fail a lot. That's part of the fun.
As a 50 year old man, with four grown kids, in the middle of a divorce after 25 years of marriage, sitting at home with a leg I broke skateboarding last month I can honestly say that I have very few regrets so far. I travelled through a lot of Europe and most of the US before marriage, I've had interesting work, and I've learned how to do a lot of things just by being willing to try.
Remember, failure is always an option and is the expected outcome at least 50% of the time. If you're not failing, then you're probably not trying anything new.
This assumes the company will be around in 10 years and that I am still working there.
I am an independent software developer and like most business owners I contribute because it's required by law and failure to do so carries harsh penalties.
Are you telling me that you do not pay federal and or state income taxes? That you do not contribute to FICA? Are you under the impression that because you are not a federal employee that you are not required to pay federal income taxes?
If so, the IRS has plenty to say about it: https://www.irs.gov/privacy-disclosure/the-truth-about-frivo...
I and a lot of people do have to save a write a check (I pre-pay estimated actually). You do not want to get on the wrong side of the IRS.
Here you go: https://www.science.org/doi/10.1126/scitranslmed.abi9915
It's your grandmother. You can choose how to treat her.
Also, the immunization provides more robust immunity than having had Covid.
https://www.cdc.gov/media/releases/2021/s0806-vaccination-pr...
And you're comparing a very small risk for the youth (getting a vaccine) versus a very large risk for the elderly.
They're your grandparents though, so I guess that's your decision.
We should go into business together. :-)
And yes, if everyone who was unvaccinated went out today and got the vaccine, the COVID infection rate would drop precipitously.
Edit: Apparently this is new information to people: https://www.cdc.gov/media/releases/2021/s0806-vaccination-pr...
As I have explained to several of my children's young friends "you are correct, COVID will probably not make you sick, but how will you feel when you find out you killed your grandmother by giving it to her".
The OSHA requirement will hang around, but people won't be freaking out about it because it will be normal. Within two years there will be a childhood COVID vaccine that is safe and effective and it will be required for school attendance like all the other shots.
All the people freaking out about the vaccine/mask requirements will have matured out of it or will find something else to be outraged about.
If I'm wrong, I will come back and say I was wrong. :-) I may lose an internet point or two.
I was set to be annoyed by the article, since it seems to me that a lot of PM practices put way more emphasis on planning to do things, versus actually doing them, but after reading it it just seemed like a slightly modified version of what most teams I have worked on do for sprint planning.
Which makes me feel like I missed something in the article. Perhaps it is geared towards PMs who don't have any experience or appreciation for "agile" methods?
I can give you a really really accurate estimate, but in order to do so we're going to have to spend a lot of time going through the request, building and verifying actual requirements, designing the solution and then validating it.
The process will require dev resources, business resources and probably people from the support team and will take a lot of time.
I'm happy to do it. It's actually my favorite part of the job. But the business invariably doesn't want to spend the time and money to do that.
They'd generally much rather start with a fairly vague description of what they need and let the devs keep throwing stuff against the wall and see what sticks.
Good and accurate estimation is not just a dev function. It requires buy in and input from the entire business stack.
That usually either gives the implementor enough information to wholeheartedly agree with the proposed solution, or to suggest something more appropriate.
They may tolerate (and even enjoy) your personal quirks and causes, but they are paying you to get things done that they don't have the time or skill to do themselves.
[Edit: Accidentally left ou a letter]