This is wildly inaccurate to the point of being dangerous advice. The goal during a bomb threat call is generally not to challenge, mock, or provoke the caller into a reaction. It is to keep the caller talking for as long as possible and gather information that could help assess the threat and assist law enforcement or security. There is no reliable rule that says a "real terrorist" will hang up if laughed at or that a hoax caller will stay on the line. People making threats behave in many different ways and simplistic tests like this are not a dependable way to determine whether a threat is real.
Soluble fiber in general helps lower LDL, beans and lentils work well too. One caution for diabetics, this meal could be pretty high in carbs for a single sitting depending on portions.
Interesting concept. Not sure if I like it more than drag and drop though, but I do love explorations like this. Reminds me of the old days when Flash devs would build some truly crazy stuff.
Potential bug: The first time I tried it on my iPad, it didn’t place the item, but it did on subsequent uses.
Yes, licensing does reduce supply compared to a free-for-all. But that’s the point, it filters out people who shouldn’t be doing the work in the first place. For engineers, the PE designation means you’re legally responsible for your work.
Licensing is a poor filter. Have you ever gotten a bad haircut? Is there a hairstylist or barber at your usual shop that you avoid? Those folks are licensed too.
This is a service. What happens if some ideologue turns off whatever is listening on the government's end? Unless this forked version will then print out a bunch of forms for someone to physically mail in, owning this software without being able to communicate to a digital host is useless.
> Unless this forked version will then print out a bunch of forms for someone to physically mail in
Well yes, this is in essence what tax return preparation software has always been; The end result is a completed set of values to fill into the boxes of form 1040 (and whatever additional forms are deemed to be required), which can then be filed electronically or written/printed on paper to be returned at an office or by mail.
The IRS accepts efilings in a prescribed format so that isnt a danger. If you look at a tax transcript produced from efiling vs a paper return, there is no material difference besides the fields related to how they were submitted.
I have no idea how I'd go about looking at an efiling. Does it essentially send a PDF export or does it hit an API and provide the data in a specified format? I could see how it would make sense for a giant government agency to want the equivalent of a PDF to hand off to humans so that it's "just like everything else".
I thought the same thing of his website when he first hit the scene. Great info, but the design was so bad it made it difficult to read. It was quick though, and today’s reader view would have fixed that issue. Being usable doesn’t mean zero design; everything needs to work together.
I think it depends on how overboard you go on the ESLint + plugins config than anything.
For a project I worked on, the main benefit was not having to manage (the 1,000 line haircut to package-lock.json was appreciated) and wire together the ESLint dependencies, and the ones to make it work with TypeScript, and the ones for plugins during our (ok, only my) regular…
npx --yes npm-check-updates --interactive --format group
…sessions. Migrating was just switch the dependencies and keep adding rules you do/don't care about to biome.json until you can live with it, but we didn't go that mad with the ESLint config prior to that.
I've had more issues with the VS Code extension than anything, not picking up config files when you think it should, needing restarted sometimes due to things like the import sorting on save (which to be fair is marked as experimental) completely breaking and producing malformed code near the imports you changed, and just being a bit… complainy if you had projects with and without a biome.json in your workspace.
I say don't believe the hype, unless you just need the basics.
For me Biome replaced Prettier but its linting capabilities are nowhere near the amount of rules available for eslint. They mention having rules from ts-eslint and unicorn; then you check and it's a handful out of hundreds of rules among the two plugins.
So it's fine if you're using a basic eslint config, but you miss out on a lot of powerful linting otherwise.
We have the editor plugin configured so we can see lints in-editor. But the rules are not yet sufficiently configurable for us to use it in CI. It seems they have their own rule-config schema, and it doesn’t expose everything you might need.
For example the banned import rule- you can list specific imports to ban, but you can’t configure a pattern. The actual lint rule supports patterns already but biome’s config doesn’t accept a `pattern` property.
We’re in the early stages of this transition. There’s no formal hiring freeze, but leadership has made it clear we should exhaust AI options before considering new hires. At the same time, raises and promotions are frozen this year, which has definitely caused a lot of frustration internally.
As part of this AI-first shift, all engineers now have access to Cursor, and we’re still figuring out how to integrate it. We just started defining .cursorrules files for projects.
What’s been most noticeable is how quickly some people rely too much on AI outputs, especially the first pass. I’ve seen PRs where it’s obvious that the generated code wasn’t even run or reviewed. I know this is part of the messy adjustment period, but right now, it feels like I’m spending more time reviewing and cleaning up code than I did before.
