To people reading this: please never ever do that, unless it was agreed upon with your client/employer beforehand (and compensated accordingly).
If you know the code may break in 5 years, why don't you fix it now? Because your employer doesn't want to pay you to do that (probably for good reason, surely there's higher priorities).
Sometimes it's because they don't know it will break in 5 years. They weren't anticipating exponential growth and when they started, the i32 range was a thousand times more than they needed. Ten more doublings later ...
You can say, anticipate breaking changes that is calendared to happen as an eventually rollover or deprecation
Essentially things have to work one way now and there's solid reason to think it will no longer work that way later and there's no valid path to fix because exogenous conditions change.
This alternatively, can be done in bad faith to guarantee a future paycheck by intentionally placing timebombs in and then charging high rates to come back. There's incentives for abuse.
I'm making it clear and acting in good faith. I can give them 2 hours for free in 5 years, whatever. I'm a competent and responsible person and I get paid well by not being so cheap.
We're not talking about working in bad faith, that's bad obviously. But there's no reason for most people to give away even 2 hours of their time for free. If you're working as a freelancer and it's your way of building a portfolio of clients, that's a good reason to give away those two hours. But I'd rather not have someone with little work experience read that, think it's reasonable, and apply it themselves.
In my first year of university I was working for a very small web company. I got paid per website an amount that was enough for my student needs, nothing much. I wasn't a very good developer in my 1st year, so I often received emails about bugs in past projects. The bugs were my fault, so naturally I fixed them in my own free time.
It took me 2 years to see how badly I was getting owned by the company. If they wanted less bugs, they should have asked someone with experience and a much higher salary.
The employer also shouldn't take you up on the offer because now you are engaging in work without a contract, which opens up contract issues, probably breaks things like SOC compliance, etc.
I like your accountability, but it's sufficient to document the issue in code, open a jira (or equivalent) and move on.
I'm predisposed to dislike Steve Jobs (I'm predisposed to dislike anyone who exploits other people tbh, so virtually all high-profile CEO).
But there's already 5 pretty big successes in your list. At which point it stops being statically improbable he isn't exceptionally talented by some kind of metric?
The Newton, Pippin and Copland were done before and without Jobs. And Lisa wasn't his thing (the Mac was, he was remove from being involved with Lisa).
As for the G4 cube, it is just a failed model, not some huge company bet - every company has some models that don't sell well. Apple's laptops and iMacs still sold greatly from Jobs new iMac to this day - if a particular model didn't do well that's not exactly a big deal. In fact it's an expected part of doing business. Apple had several other such products on its way to becoming the #1 valued company on earth.
Also, what Nokia-iTunes fiasco? Nokia folded, and iTunes became the biggest music store, and then an app store and a streaming service.
The point being that this is irrelevant. Do you think Bezos invented Cloud services or coded AWS himself? Did Musk invent the electric car? Did Ford invent the regular car?
It's about leading and putting things to market and succeding there, not about inventing stuff. They're not in the inventing or research business, they are in the selling commercial products business.
He didn't have the ideas, but he was a core part building the organizations. So you shouldn't listen to him when it comes to computer engineering, but you probably should listen to his thoughts on leadership and organizations.
I think it's pretty different from using high-level languages. I'm not interested in a competition that would be decided before even starting by who has the best AI program.
I'm not interested in a competition that is decided by who has the best Python interpreter, but since we all have the same Python interpreter that isn't a problem.
Even if it is free, I have no interest in playing chess against a superhuman chess bot. You don’t even have to know how to play chess to use the moves the bots recommend and win against a grandmaster.
The line is blurry today, but we are moving into territory where humans will not be able to solve programming challenges that require under 200 lines of code faster than AI - we are slower to read and type. The AIs will likely get better at understanding the problems, requiring less help from humans and fewer attempts to find a solution.
At some point using a language model to compete in these kinds of programming contests will absolutely be like using a poker or chess bot to compete in those games.
> Note: There is a delay of up to a few days between incurring costs and receiving budget notifications. Due to usage latency from the time that a resource is used to the time that the activity is billed, you might incur additional costs for usage that hasn't arrived at the time that all services are stopped.
So still pretty useless. Apparently they do have real-time billing updates via PubSub, but then it's up to you to code what to do when you spend too much.
If you're in an exploring phase for [GCP PRODUCT X] you're not going to preemptively write a safeguard to turn off [GCP PRODUCT X] in case of too high billing updates.
It's better than nothing, but kind of a slap in the face that they do have all the tools to really allow people to have a hard spending limit, but they don't.
I've heard the argument "but it's too dangerous, people might lose non-backed up data", but that also happens if you set a Billing Limit, just that the billing limit will kill all your projects AND still let you rack days of over-the-budget billing.
The capping costs sample code in my updated link warns you that it will go and forcibly stop assets, possibly deleting data, due to suspended billing. It still has the same notification delay so it's not a total panacea, but it does help alleviate some of the fear that I'll accidentally end up with a huge bill at the end of the month due to a small misconfiguration or for forgetting to shut down a GPU instance or something.
I can't vouch too much for it as I've used it for maybe 1 hour tops, but the remote capabilities of vscode were pretty seamless for that one hour.
Emacs+Tramp definitely does not feel like you're editing locally. A surprising amount of things work, but many others will fail in annoying ways or are just clearly not supported.
What's your hourly rate as a designer, and how many minutes would it take to put together all the triangles in Illustrator?
If you make more than $16/hr and it would take you 30 minutes to put this together triangle-by-triangle, color-swatch-by-color-swatch, then $8 is not too much, correct?
Not just that... If he has to do any kind of customer support it rapidly becomes a money losing business at $1. Looks like it wasn't worth it at $4 either.
