It would be cool to do some evening shifts at a restaurant, for the novelty and the social aspect (compared with staring at a screen all day)... plus the work is cognitively very simplistic... quite relaxing compared to corporate life. The problem is, if I have a day job as an engineer, my regular income puts me in a high tax bracket. So, not only would I be earning close to minimum wage, I would be taxed at the highest tax rate on the minimum wage... so it really would be a waste of time. Progressive tax rates are what makes it unviable for high income earners to pick up a weekend or evening job.
I worked both front and back of house in restaurants in high school and college. It is true that the work is cognitively simple, but there is nothing relaxing about the work. Even if you could do the work tax-free, I assure you, you don't want to do it if you do not have to.
Would some cook/work for discounts scheme be possible from a tax perspective? Something like, you work for x hours and bring y friends or coworkers then get a z discount?
Because there is a fiscal deficit which requires borrowing, which means that new money is created. If the new money were spent only in the USA it would cause prices to go up a lot, so the money goes overseas so that the price increases are more moderate (arbitrage). Why is there a fiscal deficit? Because politicians want to win elections. If the fiscal deficit were ended then mathematically there could not be a trade deficit.
The faster you can deploy, the faster you can deploy fixes. Also note, you can always roll back bad deployment.
But, using a trunk branch (eg master, main, whatever you want to call it), doesn't mean you can't support a variety of release schedules. You primarily just feature flag the elements that aren't scheduled for release.
Why not tell it, "I only want the regex, don't give me the entire solution. I'm doing this to learn, please don't spoil the assignment for me." Anyway, if you want to learn regex there are many interactive regex tools online that you can use to iterate on.
Wide events are good, but watch out they don't become "god events". The event that every service needs to ingest, and, therefore, if there's new data that a service needs then we just add it onto the god event, because, conveniently, it's already being ingested. Before too long, the query that generates the wide event is getting so complex it's setting the db on fire. Like anything, there are trade offs; practical limits to how wide an event should reasonably become.
Maybe I’m missing something, but this doesn’t seem like what the article is talking about at all. These events are just telemetry — they’re downstream from everything, and no service is ingesting them or relying on them for actual operational data.
It had too many Indians. Not that that's absolutely a bad thing, but it was bad for me because the answers tended to reflect Indian cultural perspectives and they weren't very relevant to me.
