Determining this at all takes skill. Determining it that far ahead of time requires so much skill and foresight that suggesting that people try is bad advice.
1,171 karma · joined October 9, 2013
Determining this at all takes skill. Determining it that far ahead of time requires so much skill and foresight that suggesting that people try is bad advice.
OK. https://aws.amazon.com/aws-cost-management/aws-cost-anomaly-...
I’m just so miffed that it can end up necessitating roping in so much BS. Mind you, not necessarily in this example. Things like HTMX excite me. And, on the other side, things like Next.js and Remix that IMO are a breath of fresh air, even if they might not ultimately be heading in the right direction (I genuinely have no idea).
Not that document databases don’t have their place, but…MongoDB is webscale and all that.
Nobody cares, and if you aren’t tying this to user value from the get-go, you’re fighting a losing battle.
This stuff is hard, and it’s incredibly easy to sit here on Hacker News talking about how things will be when we finally get to the fireworks factory. But for the time being, the reality is that there’s serious money and smarts behind the development and ongoing operation of this stuff.
I, a nobody, got access to GPT-4 pretty soon after it was released. Maybe your stated use case wasn’t compelling enough to get access to the beta?
I, after getting access to GPT-4 mind you, signed up for ChatGPT Plus or Pro or whatever it’s called. GPT-4 calls are still very heavily capped.
What’s the motive behind the conspiracy theory to which you’re alluding?
OpenAI can basically do whatever the hell they want here. I imagine there might be more favourable terms for the big kids. But for your average Joe, OpenAI makes basically no commitment. OpenAI aren’t trapped. Not even remotely. You’re basically buying something at the local swap meet. I imagine that the terms via Azure are effectively the same in this particular regard, though I do understand them to be different in other ways.
This is such a blindspot for ‘24/7 engineer mindset’ people. And, in a professional context, things like this serve as a great litmus test for if someone is capable and geared to look at things at a bigger-picture level instead of just ‘computer problems’.
…not to equate looking at porn with getting burglarised. This is obviously BS.
As an adult that writes software used by a lot of students in a classroom environment, I am glad to see that the spirit it still alive whenever I have a Sentry error come through indicating quite clearly that someone is trying to cheat by dicking around in dev tools. However I’m also certainly going to make the troublemakers shit their pants with a strongly worded console.log().
Calling this an “internal process” that’s none of your concern, a much more egregious wilful misrepresentation of this situation. There is a situation or phenomenon of human behaviour, this is how the healthcare system deals with it.
Who are you as presumably some software person to come in telling them to knock the gate down without understanding why it was put there in the first place? God knows you’d hate it if someone did that to you in your area of expertise. I understand that the proliferation of VC-backed money-losing companies which parachute clueless software people into other domains have given developers an undue sense of transferable expertise, but perhaps exercise some self-awareness.
It is a scheduling system for a department at a major public hospital in the area.
It’s still one of the projects I’m happiest with. Despite subsequent developers making a bit of a mess of it, it is a nice piece of software. And, compared to the rest of the stuff in health system, is it a shining beacon of hope for generations to come.
As I’ve progressed and started working for some bigger companies, I’m incredibly impressed by what we all, myself included, did with so little.
Just admit that you don’t yet understand the other perspective. Resorting to this sort of snark really isn’t in service of reaching a shared understanding.