Yesterday, in a few Reddit forums and generally from the discussions around me, I noticed that people are "tired" of office work.
Either too much routine or exaggerated demands on creativity and the like. Mostly, these are people who are paid well and can afford to "leave" their jobs to explore, relax, do something else.
I think the question is a very straightforward but a tricky one! You are given the ability learn and master ANY skill in the span of day. The logistics don't matter, it will be done. Which skill do you choose?
Yesterday, I saw this report: Meta employees consumed 73.7 trillion AI tokens in a single month. This costs roughly $221 million a month and around $2.65 billion a year. That s the salary of about 9,000 engineers.
In addition, the consumption of tokens (energy and electricity related to it) also has its limits.
Many people are starting to boycott AI. Today I read in a private message from a company profile: "Was about to sign up and noticed you use AI images, so decided not to"
I don t doubt that AI makes our lives easier and creates opportunities in many ways.
But don t you notice the fact that at a certain point it becomes unsustainable and disadvantageous?...
Next week most of the Product Hunt team is flying into San Francisco from around the world to plan our roadmap for the second half of 2019. We'd love to hear your ideas. What should we build? These could be completely new products or improvements to existing features. Feel free to get creative. There are no bad ideas.
Most people think users choose products based on features or price. In reality, support decides who stays.
A cheaper tool becomes expensive fast when every issue turns into a ticket nightmare. Meanwhile, teams keep paying more for products that solve problems and support them when it matters.
Support is not a cost. It is part of the product experience. Fast replies build trust. Clear answers reduce churn. Companies that treat support as a growth lever win.
While building an OpenAPI SDK generator, I realized that real-world API specifications are often much messier than the examples we see in documentation. I'm curious what's the biggest challenge you've encountered with OpenAPI? Circular references? Inconsistent naming? Missing schemas? I'd love to hear your experiences.
Jeanne Baret, Frida Kahlo, Virginia Wolf, Sabiha Gokcen the ones first appears in my mind. I respect women in history and I believe it was even harder to achieve any success back then.
