The author spends the first paragraph of the article talking about how n number of users bet x on a specific outcome and they won. They fail to account for the many others who bet on a different outcome and lost.
I watched polymarket like a hawk for weeks before the attack and am incredibly familiar with the numbers. Fact is, there were no indications on Polymarket that an attack was happening that morning. The chances of an attack was like 10 percent if I remember correctly.
UniFi website and marketing is just really really bad. They have amazing products but for some reason they don't really care about consumers and don't really know how to market to consumers. Just look at their website, it's impossible to find anything other than some super super specific networking stuff that you probably need a CCNP to even begin to understand
Absolutely agree. Mistakes should be corrected immediately, protocol revised, and those responsible punished, if malicious acts are found. Otherwise, enforcement should be full stream ahead. Illegal immigration has hurt the US enormously and it's time that we enforce our laws.
For me, personally, any new language needs to have a "why." If a new language can't convince me in 1-2 sentences why I need to learn it and how it's going to improve software development, as a whole, it's 99% bs and not worth my time.
DHH does a great job of clarifying this during his podcast with Lex Friedman. The "why" is immediately clear and one can decide for themselves if it's what they're looking for. I have not yet seen a "why" for Zig.
Techrot is real and it's there in almost every major big tech product. Google does definitely take the gold medal in this category though as I have never seen so many bugs in production software by a trillion dollar company as I have seen in Google's.
1. Maps crashes almost every ride on Car Play (this used to happen a lot back in 2023 and was fixed for majority of 2024. Seems like it regressed again)
2. Trying to expand reviews on Google Maps expands the wrong review (100% reproducible, not an edge case)
3. Firebase Auth has terrible reliability when it comes to SMS delivery and fail rate of like 5-10%.
4. Gmail keeps opening links with the wrong account (Click on Google meet link from an email in account number 2, as in .../u/2/... . Link opens with account 0 and now you gotta switch accounts again).
5. Gemini is famously unreliable and produces wrong results for seemingly simple queries.
And many more I can't recall on top of my head but surely exist.
Dreamweaver was how I learned MySQL back when I was 12-13 and got into web development. I don't remember how I came across it but somehow things, the way they were laid out at the time, made sense to me. This would ripple into a career that's making my living 16 years later.
I remember downloading XAMPP and installing it to get a local MySQL and PhpMyAdmin server. A few clicks in Dreamweaver later, I somehow had a connection file that would connect to my local MySQL server. I started playing around with it and creating different forms. The MySQL query generators on Dreamweaver were so simple that you could, with a few clicks, have a full on CRM.
I ended up coding a test score reporting system for my middle school class and the school somehow trusted me and started using it. This made me possibly the most hated person in the school because parents could now see their kids scores every day and there was no more "Oh the teacher hasn't given out the scores yet." But it was good times, and I was so excited about it.
Many years later, I now run a startup and have transitioned into using Node.js but MySQL is still my bread and butter. I still remember that day when I discovered the SELECT query.
1. Upgrade protocol to include protections for well known cold wallets held by exchanges (ex: API call has to be made to the exchange's security endpoint to validate each transaction out of the wallet. Exchange staff would need to manually allowlist large transactions before they are transmitted).
2. Decentralized voting on reversal of transactions (90-95%+ vote needed to reverse to avoid 51% attacks)
I'm a huge crypto believer but I can admit that we don't have a serious system if a person can just transfer over $1.5B from a well known crypto cold wallet to different accounts with nothing flagging it and no way to reverse it.
Lol this was the most blown out of proportion "gate" ever and a nothing burger really. The issue wasn't what Apple did, as it is a very common practice in the industry and I bet almost every other manufacturer did it too. The issue was that they didn't notify the user.
1. Your 5 year old kid with her pink bike should not be on the street alone. This is just a matter of judgement, independent from other motorists. You should be behind her watching for cars.
2. If you want to ignore point 1, my argument still stands. The chances of a Dodge Ram 3500 ramming into her is far higher if she is on the sidewalk as opposed to on the street. A 5 year old doesn't understand traffic rules good enough to be riding on the side walk and watching for cars. Her best chances are to make herself as visible as possible (ie. by being on the road in a bright bike and protective gear).
I run a $3m/yr startup on a free tier Cloudflare account. To this day I have no idea why Cloudflare is not charging us for anything. I would have happily paid them for their service
1. NEVER RIDE ON THE SIDEWALK. Cars on the street cannot see you due to other parked cars and WILL make right or left turn on you. Additionaly, cars coming out of parking lots won't see you on the sidewalk.
2. NEVER RIDE ON OPPOSITE SIDE. Ride on the same direction as cars, make yourself visible.
3. INDICATE ALL TURNS WITH HAND SIGNALS. Be predictable. Don't just turn or otherwise behave unpredictably. Indicate turns, make eye contact and then turn.
Agree with all your points on the real world consumer experience.
* I would never assume the AI answer to a consequential problem to be authoritative, unless it shows me the source and I can click on the link to verify the source and the data presented (search engine use case).
* Rewrites with AI are bug-prone and often produce hard to trace bugs to the seemingly correct nature of these bugs. Generating the scaffolding works super well.
* Images are often too smooth, videos too robotic and rhythmic, water too shiny, etc. Trained eyes can easily distinguish between AI and real.
Agreed. There is just too many limitations for it to be ever useful, unless you build out a large dictionary with a huge CPU cost... A true waste of effort, albeit a fun one if you wanna learn QMK programming
You learn to learn with time and imo it's different slightly from field to field. In tech field you just learn by doing, asking questions, making mistakes and gaining experience. Take a sample code in a new language, make it do something slightly different. Then add one more thing on top. Then something slightly more complex, then finally try to make it do what you want. Once ready, deploy, test, and iterate.
I watched polymarket like a hawk for weeks before the attack and am incredibly familiar with the numbers. Fact is, there were no indications on Polymarket that an attack was happening that morning. The chances of an attack was like 10 percent if I remember correctly.