Cicero22

One admittedly minor issue is that since monero is ASIC resistant, its very attractive to run on compromised computers. Other coins suffer this as well I'm sure, but I don't have any data on this. I guess this is mainly a hunch.

I've been looking for good tech conference videos and thought I'd be able to find some good ones if I built a tool for combing through hn posts and comments in an attempt to find interesting videos.

Heavily vibe coded, so correctness not guaranteed.

my take away was that the race condition was the root cause. Take away that bug, and suddenly there's no incident, regardless of any processing delays.

0.02% almost reads like satire. If you're on to something you should consider open sourcing it or give far more details to start a real discussion.

One suggestion I have is that you should run this on many binaries instead of just a single one to get an idea of effect on various binaries. If you're already doing this, my apologies. The post made it sound like you've only tested this on a single binary.

Where did you get the top ten from?

https://huggingface.co/spaces/TIGER-Lab/MMLU-Pro

Are you discounting all of the self reported scores?

This isn't actually too suprising? I'm certainly not shocked at least.

April 2024 - 209 Billion Surplus April 2023 - 176 Billion Surplus https://www.fiscal.treasury.gov/files/reports-statements/mts...

I was thinking they could use something like cloudwatch events, or something, to trigger sweeps and significantly reduce scheduled sweeps.

They could even use cost allocation tags to predict if a bucket or group of buckets should be scanned if it's growing unexpectedly. Cost isn't a perfect metric but there's definitely signal there.

This sort of work is something I wouldn't be able to do, but I can't help but point out at least one potential issue with the paper. It's a lot easier to find problems than solutions I guess.

Are the benchmarks comparing node versions valid to conclude a real world performance increase?

one possible confounder is the version of V8.

https://github.com/nodejs/node/blob/v18.x/deps/v8/include/v8... https://github.com/nodejs/node/blob/v20.x/deps/v8/include/v8...

ideally, they would've patched Node 18.15 with their changes directly and test their patch against 18.15.

Why not ask for an extremely brief summary up front?

if you're just trying to initialize a new Array, you can just hardcode it and get much better performance. https://www.measurethat.net/Benchmarks/Show/29982/0/hardcode...

This isn't necesarrily unknown, but knowing that there's a cost associated with promises and async/await will get you pretty far in terms of performance. I remember the idea first clicking when I watched this : https://www.youtube.com/watch?v=SMBvjmeOotA

This is some very good marketing, intentional or not.

I haven't heard that you're taxed when you lose money. My understanding was that If I invest $10,000 in a taxable account, lose $1,000, and withdraw the remaining $9,000, I won't pay taxes on the $9,0000 (ignoring transaction fees).

We have someone check grafana a few times a day and alert us if there's an issue. Not great, but it works

A third dev locale worth considering is one which consists of random emojis. Makes it very easy to find hardcoded strings.

I find that it's great at creating a starting point for react components, using material ui components. Generally, I find it more helpful to review the code it produces than to produce it myself on the first pass.

It's possible for it to be useless now, while being incredibly useful in the future. Prompting chat GPT manually can be very time consuming, especially with how long it takes to spit out a result. If something like AutoGPT can make it so I only need to write one or two prompts to get what I want, then it's already become useful. For reference, When I've used gpt to work on simple websites I generally end up using 10+ prompts.There is a trade off where it will definitely use more tokens than I would while prompting, though.

One interesting benefit of projects like AutoGPT is that it will be able to immediately benefit from improved models, assuming access is granted.

I think the main issue with being a data-driven company is that it's a known secret. Sure, you can snowball a small edge into a winning position over a few years, but isn't it more likely that your competitors become more data-driven, mitigating your one advantage and enhancing their advantages?

Could someone link to the research in the first chart? I couldn't find a citation, and I'm not sure I trust simulations of children who can't read.

  I wonder why people accept it. Does it appeal to the narcissism, i.e., people like to be monitored at all times because it makes them feel important?

I think it's pretty much like boiling a frog. The trend will continue, and people will have less and less privacy. At this point the marginal benefit of privacy in a car doesn't matter to most people, as saddening as that is.

Wouldn't that just end up increasing the difficulty of mining in the long term since it would all be opensource? I feel like any advantage they get by patching the software would be short lived with many people following suit, but I could 100% be wrong about that.

are there other studies on animals / mice which have a larger sample size? the one linked in the post has a sample size of 106 which to an untrained eye seems small. https://static1.squarespace.com/static/5a2069c3ccc5c5325fd05...

Chances are your information's already stored somewhere that you have no control of. Knowing that, it might be better to focus on mitigating the impact of identity theft rather than preventing it entirely. One way you could reduce the impact would be setting up many (10+) bank accounts and splitting the money between them. if someone stole your identity, how likely are they to be able to empty every one of your accounts before you notice and freeze them? another option would be to put your money in crypto, making sure you have custodianship of the wallet. Though, that adds the risk of crypto tanking in value.

My understanding is that time in the market beats timing the market.

somewhat relevant video: https://www.youtube.com/watch?v=w_aOERmUWdA

His videos generally are high quality and offer good advice, although some are tilted towards a Canadian point of view in terms of taxes.

When using animation delays, it's probably better to make the class include how long the delay is instead of just using 'animation-delay-1'. For example, Tailwind does this with transition delays, and it would definitely make the code clearer, imo.

https://tailwindcss.com/docs/transition-delay

I detest the MikroTik cli. I suppose the cli itself isn't terrible, but the fact that it's coupled with the mikrotik scripting language leaves a very bad, nearly rotten, taste in my mouth.

> I try to keep Crypto around 10%

Seems like he's actively rebalancing it to ~10%

> Avoid the debugger.

People who don't use the debugger, do you generally have more/better logging? What other advantages would there be to not using a debugger. Perhaps simpler code, so that you don't need to use a debugger to debug?

Wouldn't that end up slowing down the whole system from writing to a file though?

While you can definitely manually pipe all of the pieces together and have a functioning system, it's significantly easier, and likely more secure, to use the battle-tested auth library of a framework.

One could also use the builtin language functionality and external packages to write custom crypto, and I think we'd both agree that that's a bad idea. I'd argue that it's the same for authentication in general.

You shouldn't be rolling your own authentication. That's just asking for trouble.

I don't have experience with those frameworks, but the rails equivalent, devise, is very good. I assume it's the same for any mature framework.