For example, I've been booking a group trip lately, and I found that the sticker prices for some things didn't include many fees, so it was more of a hassle to actually get accurate quotes. At the same time, the companies which were providing these prices have an incentive to hide fees, because that's what all their competitors are doing – they have pressure to be competitive both at first glance and at checkout.

With a level playing field, these fees should be incorporated into the total price across competitors, allowing for easier cross-shopping. I'm excited to be more confident I can quote what I see initially vs. going through a checkout flow.

What a thoughtfully designed space for your family and friends! I feel like going this custom is pretty rare, and you’re clearly getting the value out of it. I also love that you did the math on the cable runs making essentially no difference.

Thanks for sharing :)

>It’s very important as a company we maintain proper communication lines. ... If you skip and just go below you prizemust then call and let the people in charge know. Let’s say you’re a production coordinator and you call a writer and tell him you need some bits about a sandwich being cooked with lava, seems harmless... and then tyler askes her why she is making lava and she has no idea and everyone is confused. This is what happens when you don’t follow proper communication lines.

Skipping over all the typos, it's just such a great visual of the communication breakdowns that can happen when a lot of things are going on.

Also this section on tracking contractors:

> [Y]ou can’t just dump and forget your projects... Ask him to send videos everyday to spot problems early, hell maybe talk to him twice a day. I don’t care just don’t leave room for error. No excuses, stop leaving room for error. Check in daily, receive videos, and know weeks in advance if you’re fucked. Not days.

This is more extreme than I encounter in my day to day, very on brand to MrBeast, but it's interesting to see this constant accountability and ownership are so critical in their production. I see similar behavior in some of the more effective people I've worked with.

How often are you deploying your apps? Every commit? A few times a day?

How do you measure these deployments to make sure they are stable / non-breaking? How are you alerted when things go wrong?

Do you do ramp your deployments, or deploy to 100% of users at once?

How do you solve the problem of measuring low-volume flows, where it’s harder to tell if there’s been a drop off in conversion?

I’d love to know your experiences have been like, and any recommendations you might have.

Comments URL: https://news.ycombinator.com/item?id=41422259

Points: 1

# Comments: 0

We saw that production and consumption of opiates was far too high, eventually leading to the bankruptcy of Purdue Pharma. In that case it seems like the DEA was not taking a strong enough regulatory role, leading to much harm to Americans.

Are we facing an upcoming epidemic of amphetamine addiction and the DEA is holding it back, or is the DEA causing more harm through regulation of production? It’s impossible to tell from this article alone, but it seems clear we need at least some regulation of production, since the pharmaceutical industry cannot completely self regulate.

In conclusion, the rise of generative AI is a transformative trend that will have a significant impact on the information economy and the job market. While certain types of jobs might be at greater risk than others, there is still room for adaptation and growth for individuals who proactively prepare for this shift. By focusing on tasks that are novel, unpredictable, and fragile, fostering high-trust relationships and interdisciplinary collaboration, and embracing AI tools to enhance productivity, it is possible to navigate these changes and secure a meaningful career in the evolving landscape. The key is to take action now and invest in the skills and strategies that will make you indispensable in a world where AI continues to advance.

Before I could register I could see most classes I wanted to take had plenty of availability except for one which was almost full. That class would make my schedule perfect (no classes before 10am, everything ending before 4PM, good teachers), so I was ready the moment my group got access. I logged into the janky Java applet and saw that my desired class was full. Dismayed, but not giving up, I refreshed the class list to see if someone might drop during the drop-add week. Nope, still full, but there was still time for someone to change their mind and for me to slip in. I was going to need an edge.

Another peculiarity of this system was that it was definitely a weird Java app based on some type of main frame. It must have been around for a decade at least. One of the signs of its age was that you had a limited amount of time per day during which you could be logged into the system, something like 90 minutes a day.

So I did what any good hacker would: I made _really_ good use of that limited time. I wrote an AutoHotkey script which would automatically log in, traverse all the menus and attempt to sign me up for that class. It was much faster than a human, so each run barely put a dent in my logged-in time allotment. As a cherry on top, I wired it up to a python script to push notify me if it succeeded.

After letting it run for two days, some false alarms, and tweaking, I got a delightful "You're registered!" notification on my phone and found that it had successfully gotten me the class I wanted. I'm still chasing that high to this day.