HN user
Let's see...
You can be part of the new reputation economy, IF you can afford Multiple Claude Max subscriptions and use all your tokens for it.
Kind of like "getting good" at a collectible card game. It's more weighted toward whether you have money (and are willing to spend it) than anything else.
I'm picturing all that coming from Max Headroom...
They're spinning this as a positive learning experience, and trying to make themselves look good. But, make no mistake, this was a failure on Anthropic's part to prevent this kind of abuse from being possible through their systems in the first place. They shouldn't be earning any dap from this.
I'm finding that Bitbucket works well enough for my needs. It's CI is kind of an acquired taste, but once you hammer it into shape, it'll do what you need.
There's going to be a demand for Artisanal/Organic/Hallucination-free programmers in the future, much like there's a demand for COBOL programmers now, but bigger.
I'm building a music file manager using Electron. I'm deferring the actual music playing to VLC, but I need a way to sort through my many audio files to quickly select and launch what I want to hear.
I wonder when we'll start marketing our zero-AI products as "artisanal", "organic", "no GMO", "hallucination-free"...
The problem with the proposed solution is that many teams can't accurately break down tasks small enough. And, even those smaller tasks have variability in how long they take to do. What I've seen is that most teams don't really know how far "stories" break down into their simplest tasks until they actually do the work.
So, that puts us back at square one, for the most part. A story point may not tell you a lot, but tasks in this form often present the same problem.
SharePoint itself was only built so that it could be marketed as a "Notes killer". It doesn't do nearly what Notes did, but most shops only found that out after they were told to try to replace their Notes apps with SharePoint.
Why not both? Not at the same time, of course.
Neither is exclusive of the other. I'd start with React, since it's 80% of the market. But, once you feel comfortable with that, move on to learning Vue.
Also, it's worth it to consider looking at Svelte. If anything is going to take a chunk out of React's market share in the future, it will be Svelte or something that looks like it.
Remember that there's no limit to what you can learn, one step at a time.
I've had a good experience with a Geekom mini pc so far.
Keep an eye on this, because this will do nothing to lower congestion in NYC. It's purely a money grab.
The drop in traffic that experts are expecting already happened during the Bloomberg administration, when they made most areas in Lower and Midtown Manhattan "no parking" zones, and jacked up the taxes on parking garages.
No one drives into Manhattan unless they have to, and congestion pricing won't change the situation for those people who don't have a choice.
Express is still the "go-to" now, because it's the rare case of a Node library that's stable, battle-tested, and doesn't change much. (Yes, the maintainers having not been able to release v5 has actually been a sort of advantage.)
But, there are other great options to go with now, and you probably won't go wrong with fastify or hapi.
Feels like there's so much massive societal damage coming out of Stanford (Theranos, FTX, so much more...), that it's kind of a dying platform. If I'm a high-achieving high-schooler, I'm going to have real second thoughts about applying here.
I ended up using Dropbox Paper, since it came along with my Dropbox subscription, anyway.
We rely heavily on Redirect components, to support a "legacy" URL structure being forwarded to the current URLs. We are able to resolve these forwards server side during SSR. That whole feature was ripped out, with the suggestion that everyone just use the history API to redirect users, or write a whole bunch of separate controller logic in the server process. This, of course, was not a suitable substitute. When we looked at the "compatibility" plugin to help v5 users migrate to v6, they didn't include this feature in it at all.
https://gist.github.com/mjackson/b5748add2795ce7448a366ae8f8...
Philosophically, he just decided that there was no value to a Redirect component.
Personally, I can't go with this advice. We're on 2.5 years rolling our own, and it's been really clear that we made the right choice in not going with next.js, which was the only such framework at the time.
Given that the remix author complete broke react-router for our use case (to the point where we can't upgrade to v6), I wouldn't trust that remix could meet our needs, either.
(There is a temptation to fork react-router v5 and maintain it independently. But, we're good just pinning the version for now.)
Wow. So much complexity here that they seem to not realize that they've added. Feels like they're just replacing one problem with another, rather than solving anything.
Moda Operandi | Senior Backend Engineer, Lead Devops Engineer | REMOTE | Full time Moda Operandi is a ten year old fashion retailer based in NYC. We're hiring a an experienced backend engineer, and a devops tech lead/team manager to work on the modernization of our tech stack.
We're building a platform using Scala, Node, Terraform, Kubernetes, AWS, code generation, and a lot more. Come join us!
Backend Engineer: https://boards.greenhouse.io/modaoperandi/jobs/5498793002
Lead Devops: https://boards.greenhouse.io/modaoperandi/jobs/5441933002
You do realize that this speech was actually part of the Russian plot itself? The tell is him calling out Walter Mondale. As we know now, the real "destabilization" started with Reagan.
My take: Start by talking to a therapist.
The question that it sounds like you want to answer is, "What am I missing?" Going minimal may help, but it also may not. The first step is to identify the problem that is causing you to feel the way you do, and that will open up avenues for solving that problem.
Speaking with a well-trained neutral/impartial intermediary is likely the best and fastest way to identify where your misery is originating from.
Advice for what to do beyond that is kind of like taking shots in the dark, without knowing what you're really solving for. The suggestions in the rest of the thread might be good, but I'd save them for when you have a clearer picture of what the problem is. Then, it'll be more obvious which techniques are worth trying.
Good luck!
Moda Operandi | Senior Backend Engineer, Lead Devops Engineer | REMOTE | Full time
Moda Operandi is a ten year old fashion retailer based in NYC. We're hiring a an experienced backend engineer, and a devops tech lead/team manager to work on the modernization of our tech stack.
We're building a platform using Scala, Node, Terraform, Kubernetes, AWS, code generation, and a lot more. Come join us!
Backend Engineer: https://boards.greenhouse.io/modaoperandi/jobs/5498793002
Lead Devops: https://boards.greenhouse.io/modaoperandi/jobs/5441933002
We do. But, depending on your project, you may need to do extra work to corral the complexity that can grow up around them. We wrote a library for using them in our web apps that allows us to use them, and remove them, easily.
Some possible failures that can happen with feature flags: 1) "Accidentally perpetual" - Since feature flags are a part of the code, it's easy to create multiple dependencies on the flag value, which makes it difficult to remove from the code without mysterious null exceptions happening where you didn't expect them. 2) Cross-scope - Using multiple feature flags carelessly can result in situations where one flag value change doesn't do what's expected unless another flag's value is present or set to a certain value. Flags should always be independent from one another, even if they're controlling the same code. Instead of two flags whose values affect each other, you would instead create more flags (4, in the case here if using Boolean flags) to reflect each combined state. 3) Fallback - What happens if the systems or SaaS that supplies your feature flags becomes unavailable? Always consider this.
Feature flags are a great tool, and enabling your team to be able to "test in production" with them can be amazing. However, do watch out for the footguns.
Perhaps the most important thing we can do is fund a scraper that creates an RSS feed for sites that don't have one.
Keep in mind that a lot of NYC's heat is provided by a steam system managed by Con Ed. I don't know if anyone is building new construction that leverages it, but it's there as an option.
Just amazed at how many people on this thread are refusing to get the point. There are counterexamples to the idea that we can collectively diet our way out of mass obesity everywhere you look. But, it seems that many people can't shed the comfort of thinking of it a character-flaw problem, rather than the biology problem that it clearly, obviously is.
Moda Operandi | Senior Backend Engineer, Lead Devops Engineer | REMOTE | Full time
Moda Operandi is a ten year old fashion retailer based in NYC. We're hiring a an experienced backend engineer, and a devops tech lead/team manager to work on the modernization of our tech stack.
We're building a platform using Scala, Node, Terraform, Kubernetes, AWS, code generation, and a lot more. Come join us!
Backend Engineer: https://boards.greenhouse.io/modaoperandi/jobs/5498793002
Lead Devops: https://boards.greenhouse.io/modaoperandi/jobs/5441933002
It was very challenging to sleep with CPAP. I took an extended break from the CPAP machine around 12 years ago, and then I tried the oral appliance - it worked wonders, and I haven't looked back.
The author probably should have read the jargon file before attempting this. Also probably should have read the room. (Referring to women as "servers"? Seriously?)
We chose to roll our own SSR, in an otherwise "normal" react + apollo app. This meant that, if we ran into bugs, that we weren't reliant on someone else to update an ecosystem to get unblocked.
It's worked out very well for us.