HN user
The Birthday Paradox is about a group of people sharing at least one birthday between them. If it was at least 1 person out of 23 people sharing YOUR birthday then the odds would be 1 - (364/365)^23 which is around 0.06 (or 6% chance). So, yes, this scenario is a lot less likely.
Context for the article: https://cdn.openai.com/spec/model-spec-2024-05-08.html#dont-...
"We believe developers and users should have the flexibility to use our services as they see fit, so long as they comply with our usage policies. We're exploring whether we can responsibly provide the ability to generate NSFW content in age-appropriate contexts through the API and ChatGPT. We look forward to better understanding user and societal expectations of model behavior in this area."
Does this mean that 2FA was not in place? For a company handling such personal information, this seems like a minimum requirement.
When educating the general public about the risks and limitation of LLMs, I think "hallucinating" is a useful term - it is something people can understand and it conveys the idea of LLMs being somewhat random and unreliable in their responses. I'm not sure "confabulating" is so easily understood or accessible.
Analysis finds isometric exercises that involve engaging muscles without movement the most effective for reducing blood pressure
Price will go up from $50 to $100 per seat. Now can only have 8 seats instead of 40 seats and only 1 project instead of unlimited projects.
Maybe this? This isn't THE biggest cruise ship ever built though. https://www.walesonline.co.uk/news/world-news/one-worlds-lar...
... can I do these trails on my full suspension mountain bike...?
Yes. It will be a bit more work on the pedalling front vs a dedicated gravel bike, but I doubt you will encounter any bike snobbery. I have gravel trails near where I live, and you see all kinds of bikes tackling them.
Yeah. Sorry about that. HN seems to auto remove the ellipses when you paste in the title.
I did that for a few of my posts and in the comments I was criticised for “editorialising”.
This is probably true for many other industries. Organisation experience / knowledge is very important in being effective in a role. When looking at productivity, organisations tend to overpay new starters (a new starter is often a net loss, particular in a skill based role) and underpay those who've been with the organisation for several years. Of course, people have to live, so you can't pay a new starter next to nothing with the promise of huge increases after 6 months.
Of course, the flip side is that sometimes that initial step of:
"We are doing a prototype on our new mapping product, we need to write a one-off script to pull in some map data."
... is just that - a one off script. And it can prove to be a lot quicker to write a one-off script than getting involved with an ETL framework. I am not arguing against ETL Frameworks (Airbyte etc). Just that over-engineering carries its own costs, just like under-engineering does.
We are a .NET shop and have been using DbUp (https://dbup.readthedocs.io) for years now. It is fantastic. We had so many false starts managing production databases and keeping them consistent. DbUp has taken all that away, and now every upgrade or patch is repeatable and predictable. It is worth spending time identifying what in your database is idempotent (e.g. stored procs, functions) and what isn't. This way the idempotent objects can be upgraded every time and everything else just receives a single incremental update as required.
If you have a young family, working a 4 day week would make all the difference. At the moment I work 5 days and then go into a weekend which can be just as tiring as a work day with kids to tend to. With an extra day, this would mostly be when the kids are at school, so it would be genuine time to myself.
Yes. Considering the Hacker News audience, I didn't want people to click on the link thinking it was an in-depth, scientific discussion.
What is the alcohol content once fermentation is complete? Is it similar to wine?
Exactly this. I moved to New York in my early 20s, which would seem a bad choice for an introvert, but I loved just sitting and watching it all go by. It was like being in a human circus but you are in the audience rather than in the circus ring.
One thing I have missed as an introvert is the "people watching" aspect. I don't need to be at the centre of things and don't enjoy big social occasions, but do enjoy walking around a bustling city, taking in the atmosphere. It feels like the world has stood still (or at least slowed) and that has made just my normal day-to-day less interesting. Introverts aren't disinterested in society - they just like to experience it differently to extraverts.
I’m not a big fan of OLAP cubes / data warehouses but it should be noted that these aren’t always just about scale and speed. They also serve to provide a single view of the data when the data is held across multiple databases / systems. You’re orders may be in PostgreSQL, your inventory tracked in MySQL etc. So bringing all that data into a single database for analytics can be valuable.
I'm confused. The article talks about "tenants". Does this mean the Chelsea Hotel is not actually a hotel, as it has long term tenants?
Yes. And "learning" shouldn't just be measured in PhDs or being an expert at one thing. I think the "work hard" advice can be interpreted as "focussed, tunnel vision, excelling in one area to the exclusion of everything else" when there is great benefit of aiming for a wider range of experiences in your 20s.
Regarding the "work hard in your 20s" advice.
I took the approach that in your 20s you are still forming, still growing, still malleable. The experiences you have in your 20s will have a disproportionate effect on the kind of person you end up being. Therefore, you have to think about what environment, what experiences you want to foster that growth in. I would suggest optimizing for variety and new experiences is a better idea that working 80 hours weeks throughout your 20s. In your 20s, don't just work hard, work hard at becoming the person you want to be.
I've always wondered who does those browsers / email clients / phone UIs you see in films and on TV that are kind of familiar but also not "real" software. I'm talking about everyday films - not futuristic fantasy. Often when someone writes an email in a film the UI is some kind of Frankenstein interface that isn't recognisable as say Gmail or Outlook. Am I just imagining this? Is there a company that specializes in writing fake UIs for films and TV?
Plus there is a great deal to learn out there that is not instructional and can't be captured by a single book. Reading good fiction, biographies etc opens your horizons, builds human understanding and empathy. It is more subtle than the "10 habits of successful people" style books but more valuable in my opinion.
Performance basically. As SQL is a set based language you can often replace cursors (which are basically loops) with joins and that is orders of magnitude quicker for larger workloads.
My rough estimate is: 1/2 * 10/49 * 4/48 * 3/47 * 2/46 * 1/20 = 1 in 3,390,016
What are the chances? 6 consecutive numbers when 6 balls are picked from a set of 50 balls? Ref: https://www.nationallottery.co.za/about/how-to-powerball
(Actually, the 6th ball - the "powerball" is picked from a set of 20 just to complicate things)
One obvious drawback is the amount of boilerplate code and multiple files. Although the essence may be no more complex, the amount of "noise" and fragmentation across files can increase the mental load.
I personally have found that how to approach data access has been a real bone of contention on projects and quite damaging. It seems half the team want to use an ORM and have a long list of reasons not to use SQL/Stored Procs (slower to develop, out dated, not testable, business logic in the wrong place). The other half of the team wants to avoid ORMs and would rather use SQL/Stored Procs (performance, ORMs start off okay but soon aren't up to the job, more control and power with direct SQL). In fact, you can see these two standpoints in this very discussion.
I find both have valid points and there isn't really a compromise. Whichever approach is taken you end up with half the team feeling not listened to and disenfranchised.
I have found few things to be more divisive than the ORM vs No ORM debate and I am not sure what the answer is.
What does the slash mean in the article? Where it says “... in 2018 GE sells 3.0.0.0/8” what does the “/8” mean? I guess it indicates the range of addresses?