You may want to check if you have one of the app listed here[1] on your system.
Electron based apps cause a huge system wide lag on macOS 26 due to the use of a private macOS API[2]. This bug has been fixed in Electron but not all Electron-based apps have been updated yet.
I used to work for the Australian parimutuel(aka tote or pool)[0] betting operator.
All the proceeds for a race are placed in a pool, the operator deducts a percentage of pool as a takeout, and the rest is divided among the winners, or. is carried over into a jackpot.
We had special bulk betting integrations for quantitative bettors, and even offered rebates on the takeout revenue, it's not secret, although it's not widely publicised.[1]
There are stories of traders that have made lots of money betting in parimutuel markets[1]
Alright, so I have a project that is mostly abandoned right now due to various other obligations.
The main goal was to contact car owners without having to have their phone numbers and such. But i quickly saw the advantage of tagging all sort of things. So I have it on my keychain, wallet, or several other things I own. If I lose these items, any stranger can contact me without having any of my personal contacts.
What is it? It's a QR code. You scan it, and you can send some prewritten notifications to the owner. Once they reply, you can have a conversation. Scanning captures the gps location both for security measures and to help recover it.
As a graphics designer of almost 20 years i have to heavily agree. Firefly is nice for drafting and dabbling with stuff that once would've been served by stock sites, but aside picking a few demo images or making some abstract pattern backgrounds here and there, this has close to zero overlap with the UI/UX into development & design system management process Figma serves. It's almost like saying the Bing bot eats away at Laravels user base.
As a personal aside:
I'd like to commend the initial push you guys did with XD. While Figma was still out of my scope back then, and XD played a major role for me in transitioning away from oldschool Photoshop or Indesign mockup processes into a modern workflow that integrates with my dev team and focuses on component & design token centric thinking.
Figma may have left XD thoroughly in the dust by now, and i honestly couldn't be happier that the merger won't happen, seeing how Adobe has been committed to absolutely dismantling the UX of Photoshop to the point of it only remaining installed on my workstation because Affinity Designer still lacks some core feature parity - but in its earlier days XD has been absolutely crucial to the development and modernization of my whole thinking and workflows!
> The underlying connection method is open source, for anyone to review.
SSPL sure isn't open source and I'm certainly not reviewing this. At best it's source available. I'm all for separating the meaning of the term from OSI's opinions but this usage misses the mark.
"Hands on Rust" teaches Rust by building a rogue like game step by step. Before that there's a chapter where you rebuild Flappy Bird from scratch that teaches the "basics" before diving into more advanced concepts in the rogue like. I liked the approach and recommend the book but it's fast paced and expects quite a bit from the reader (it's excellent if you have some programming experience already but probably daunting as a true first book imo).
And now that they've already cheated and were caught, what happens? Double down? Come clean? Nope, post publicly online for ideas.
This person does not seem to think things through. Glad to see cheaters put in their place, although I wonder what they would have done if ChatGPT didn't exist.
It's kinda funny how people think that firing people that are building fault tolerant distributed systems make the said systems immediately go down, including Elmo pulling the plug on a "critical rack" or whatever his tweet was. The effects will be seen in weeks, months or even years, as with any roles that were just removed but not replaced or covered.
Our dogs are frequently out in the yard, so other than spring pre-emergent I try to avoid herbicides. I bought it after a hand weeder broke pulling up crabgrass.
This thing has oddly been one of the most satisfying purchases I've made in years. You put it in the ground, step on it and the thing easily pulls out weeds and only in the spot you put it. Then you get to shoot them off the claw. I have a bucket I try and shoot them into. It's oddly therapeutic.
I'm a software engineer, but these have been instrumental in my success in a way no coding book can compare to(though John Ousterhout's "A Philosophy of Software Design" would have, if it came out earlier in my life).
Personal time/task management- The classic, Getting Things Done(https://www.amazon.com/Getting-Things-Done-Stress-Free-Produ...). The power this has on people cannot be understated. Turns out that most of how life is conducted is rife with forgetfulness, decision paralysis, prioritization mistakes, and massive motivation issues. This book gives you specific workflows to cut through these in a magical way.
Personal Knowledge Management- The equally classic, How to Take Smart Notes(https://www.amazon.com/How-Take-Smart-Notes-Technique/dp/398...). Where GTD(above) does this for well-defined tasks/work, this book does it for open-ended work, giving you an amazing workflow for introducing "Thinking by Writing", which is frankly a superpower. This lets you see things your friends/colleagues simply won't, lets you deconstruct your feelings better, learn new/deeper subjects faster, and connect thoughts in a way to produce real insight.
For Product/Business Management, Gojko Adzic's "Impact Mapping"(https://www.amazon.com/Impact-Mapping-software-products-proj...) feels like it could make nearly every software team/business 10x better by just reading this book. I've personally watched as enormous portions of my life were spent on things that barely moved the needle for companies, or merely didn't keep the metric from rising. So many projects taken on faith that if you work on X, X will improve, without ever measuring, or asking if you could have accomplished that with less. The world looks insane afterward.
I've been struggling with wrapping my head around asynchronous programming with callbacks, promises and async/await in JS, however I think it's finally clicking after watching these YouTube videos and creating a document where I explain these concepts as if I'm teaching them to someone else:
Edit... I've been rewatching these videos, reading the MDN docs, the Eloquent JavaScript book, javascript.info, blogs about the subject, etc. This further proves you shouldn't limit yourself to a single resource, and instead fill up the laguna with water from different sources if you will.
I’m a founder, not a sales person, but we don’t have any sales staff. So I, along with my CEO, do all of our demos. We split the responsibility. Our product does many things, and I could just speed talk through a demo. But I don’t. I directly ask the person what they want to see, and how they feel we can help them. If they don’t know, that’s fine, I have material prepared. But I’d much rather you tell me how I can help you, and then we drive the call from there.
A few months ago, I quit my job and started to work on it full-time (best decision I've made).
It is not VC funded (said no to 30+ investors - time will let me know if it was a good decision or not ), but funded by the awesome community! <3
Why I'm mentioning this? Because I would like to focus on the functionalities, the community & the users and not the revenue and other boring metrics. I just would like to make a good software, enjoy the process and make people's life easier. I do not want to make millions of dollars from it. If me and my family could live happily, that is totally fine.
Let me know if you have an questions. I'm happy to answer them.
I've never understood how we got to this place where _some_ content on youtube is advertiser friendly and _some_ is not, and that is viewed as actionable information. I guess my whole mental model is you run ads on the whole network, and advertisers have nothing to do with the content being shown, and only an idiot would look at an ad and think, oh this brand is knowingly sponsoring this content. Advertisers used to be content with that, and wouldn't dream of being choosey about what content their ads run alongside of. However we got to this place, it's done a lot of damage -- would much rather live in the world where there is no concept of demonetizing a particular video or channel, and ads just run on the entire network. Caving to advertiser demands is the #1 best way to make a platform worse for the actual users and content creaters and slowly drain your value. Note that for example google AdSense could run alongside _any_ content that appears on youtube probably without issue. They've just created this different, pickier world when it comes to video ads.
What's worse is youtube entirely controls the market, and they opened the floodgates of caving to advertiser demands. Now advertisers expect it wherever they go. They should be 4th class citizens if anything, not a meaningful constituency. As long as youtube keeps driving users to the platform, that should be the only concern.
I had good results with my students with the illustrated video explanation I made [1]. It thinks of running functions as boxes that produce output, and of function definitions as box blueprints.
S16 here. I think the greatest value add was actually being able to work heads-down for 3 months knowing that you would almost certainly get investment on Demo Day. Almost all companies got investment, since YC was extremely selective back then (batch sizes were much smaller) and investors generally trusted YC's judgement. Prior to S16, this was probably even more true.
If it weren't for YC one would have to spend 50% of their working hours having coffee chats and preparing demos, since investors generally had their own contorted idea of what a good demo is before they would invest, and it was usually not what the customer wanted. Being able to get twice as much work done in return for 7% was a good deal.
I don't think that applies anymore, sadly, with the large batch sizes they accept now. Nowadays you'll have to waste half your summer having coffee, not have guaranteed investment, and still give away 7%. Not a good deal.
Also, if you live in the bay area, it's fairly easy to come across most YC advice and get investor intros just by going to enough house parties with seasoned founder attendees.
Related. I listed something for sale on Craigslist recently and got a bunch of messages right away that asked obvious questions that were in the listing. One suggested that his wife pick it up, and can I take Zelle? Went silent when I said cash only.
But the most interesting scammer said: "for my safety, can I send you a 6-digit number, and you confirm it, so I know the listing is not fake?" I say yes, unsure what the scam was going to be, but sure it was a scam. Moments later I got an SMS from Google Voice asking me to verify my phone number. Mofo tried to steal my number, presumably to use it to scam other people. I was pissed and impressed.
Good advice. There are a few nice tools out there to support technical writing. I think one of them was featured on HN a few days ago: vale.
This is a tool that allows for applying simple regular expression based rules to enforce style rules. The idea is that you can tune this to your needs and cover all sorts of stylistic rules. For example, gender neutrality might be a desirable thing in the documentation for some tech companies and you can get it to flag things that are clearly not gender neutral.
Another thing worth mentioning is Jetbrains Grazie Professional (warning it's different from the normal grazie plugin, which is confusing), which actually integrates vale and can be used as a plugin for editing both code comments and markdown files in Intellij and other Jetbrains IDEs.
In general, treating text like you would treat programming code as a thing that has rules that can be figured out and enforced is a good mindset. I learned to write coherent text while doing my Ph. D. a long time ago. At some point I figured out that anything I'm doing consistently wrong, I can just learn to do consistently right. I just need to be open for criticism and figure out why something is wrong/not ideal. You kind of learn to look for things that you've done wrong before in your own text and then you fix it. A lot of these rules aren't rocket science. You just need to know about them. There's a whole grey area between grammatically correct and stylistically pleasing/acceptable. Having tools point out things that are likely problematic helps.
One thing that makes Racket somewhat special is that it can be used to build your own languages (e.g. domain specific languages) with it as it comes with the tools and a community that has experience in it.
> We have lists implemented like divs, navs like divs, lack of appropriate attributes, aria labels and few other things.
Since I don't use accessibility tools: how big of a deal is this for people who do? I try to keep my personal website lightweight, but I think I also use `div` for almost everything.
> he is being arrested because it is illegal in Russia to be against the war
do you have any source to support this?
I went thru most "Criminal Code of Russia" searching for anything related to war, and could not find anything in terms of even temporary jail time for speaking out against war. Many people do, in Russia, including politicians of Putin opposition and they are nor being jailed. Looks like you can get jailed for participating in a protest against war or basically against anything in Russia... but nobody is going to bother going after you because you have posted a mean tweet. And if you search Twitter there are thousands of anti-war anti-Putin tweets from Russian accounts posted for years and these accounts keep being acting and keep posting (from jail I assume???).
I believe those studies but correlation does not equal causation. I think the real reason that more diverse boards do better (if they do) is that the company hires people more based on talent and other metric which don’t discriminate, vs ones like patrimony. Forced diversity just sidesteps the problem because the company can still use bad metrics.
> there's no substance just a lot of charged language.
Yeah, this was my issue with all I could find so far. It seems like 'working as designed'. Perhaps those who publish on audible would like to be able to opt in or out of various sales/credits etc but as a customer I prefer that I can get anything with a credit.
> Basically Audible splits the money spent on credits among the books that the credits were spent on, except weighted by the retail price
Is that all credits in the system (similar to how Spotify was weighting streaming subscriptions (to my understanding)), or per user. I would prefer the money from my credits to go to the books I purchase, not be weighted with purchases by all other users.
I never had the "hands off" hosting experience that cloud providers advertise in the first place. Before (with AWS and Heroku) if things went down, I was the person that had to investigate and escalate to the appropriate vendor's support. Now, I'm the person responsible for investigating and fixing things. For many small issues, it's easier to fix them than to get someone at AWS with the necessary clearance on the phone.
One big trade-off is that I only have one datacenter so in cloud lingo, I only offer one availability zone with offsite backups. But then again, when AWS us-east went offline, so went most companies, because the proudly advertised multi-AZ failover didn't work that well in practice.
As for the APIs, I just limit the subset of APIs that I offer. Since this is used only for my consulting clients, my cloud only needs to support those APIs that they require. In effect, that means CEPH+PostgreSQL do most of the heavy lifting.
I've seen Cloud APIs explode in funny ways when customers actually arrive with Petabyte-scale datasets. In that sense, my customers are pre-qualified because all of them have had horrible experiences with Cloud providers over-promising and under-delivering. So once they are on my platform, dissuading them from wanting more APIs is very easy. "Would you like to continue to use my cloud at the current price? Or would you like to pay 3x the monthly spend just to use the Amazon cloud and gain API call XY? And please remember the last time they crashed badly and you could not reach any Amazon support by phone. Didn't they even bill you for EC2 while it was unreachable?"
And if they insist, I can always point them towards the Open Source project that Amazon/Heroku use under the hood. But in my opinion, most Cloud APIs don't add business value anyway. "Keep it simple" always wins out in the long run.
To paraphrase my brilliant cofounder, mentor and tough sparring partner:
"The biggest lie you techies tell to yourselves is 'Build it and they will come'. Nope. Nobody ever comes by. I've beaten competitors with the better product again and again. Know why? Because marketing builds growth, growth builds revenue and revenue enables hiring brilliant people to fix your product, all the while the brilliant product people are still waiting for customers."
Let's say I've have been having kicked my ass more than I can count on some beliefs I've had, but I yet have to regret working with him.
I'm not a pilot either, but I worked for 3 years on the 757 stabilizer trim system and detail design, so know a lot about it. My lead engineer was a pilot and would take me flying and let me fly for a few seconds. A good chunk of the engineers at Boeing are also pilots.
My dad and brother are pilots. Many of my friends are pilots.
FWIW.
But you don't have to take my internet credentials seriously, and you shouldn't. So here's some documents which you should, if you want to be informed about this:
Boeing Emergency Airworthiness Directive
"Initially, higher control forces may be needed to overcome any
stabilizer nose down trim already applied. Electric stabilizer trim can be
used to neutralize control column pitch forces before moving the STAB
TRIM CUTOUT switches to CUTOUT. Manual stabilizer trim can be
used before and after the STAB TRIM CUTOUT switches are moved
to CUTOUT."
"The [LA] pilots countered with main electric trim nose-up inputs. At least 25 automatic stabilizer nose-down, pilot-directed stabilizer nose-up exchanges took place and then several nose-down inputs were not countered."
"The MCAS activated twice, and the [EA] crew countered with electric trim."
Electron based apps cause a huge system wide lag on macOS 26 due to the use of a private macOS API[2]. This bug has been fixed in Electron but not all Electron-based apps have been updated yet.
[1] - https://avarayr.github.io/shamelectron/
[2] - https://github.com/electron/electron/issues/48311