I agree. For my use case, I chose to prioritize latency over accuracy, but it's always difficult to find the right balance between the two. There is no easy answer.
424 karma · joined April 16, 2015
At the moment, Soniox STT v5 is definitely the best, and I'm impressed by its performance. It's good that Google released Gemini-3.5-Transcribe, and it beats every other model on accuracy, but it definitely needs a bit more work on latency, which is the most important factor for STT apps.
Consumers will always gravitate toward the more affordable option.
All performances are relative. Ruby or Python is very performant for 99% of websites, generally the bottleneck is the database.
Rails has enabled Twitter to develop and iterate faster. But now that the social network has to manage several tens of millions of users, the 200 req/s of Rails are no longer sufficient.
And Ruby in 2013 didn't have the same performance as in 2023. Hardware no longer had the same performance, too.
(https://blog.twitter.com/engineering/en_us/a/2013/new-tweets...)
John's humility, despite his monumental success, taught me to always keep my feet on the ground. His vision inspired me to push boundaries in software development. But above all, it was his passion that kindled a fervor within me to harness technology for change.
John Warnock's passing is a massive loss for the tech world. My heart goes out to his loved ones during this time. His legacy, however, will continue to shape the industry, inspiring countless others just as he had inspired me. Goodbye, Mr. Warnock. You will be missed.
It exists for a decade and the cashier job still there.
Don’t be afraid of the evolution of technology, humans take time to adapt to these evolutions.
Could apply to self-driving cars too, taxi drivers are still and will be still a thing in a decade.
I've created Claper [0], an open-source tool for real-time interaction with a public. You have multiple ways to monetize an OSS, starting from donation, sponsorship to consulting or SaaS.
Personally, I chose the last one with a cloud version. I like this model, people paying for the SaaS support the project and have, in return, a hosted version of the OSS, and so contribute to improve it.
> We do not have monthly fees, set-up fees, integration fees or closure fees. We do have a minimum invoice depending on industry or business model. Please speak to a member of our sales team for more details.
If you want a simple app served on a single host you can try LiteStack [0] so you don't need a Redis/Postgres/Sidekiq instance, just SQLite.
Laravel is also good if you like PHP language.
It's easier to build muscle mass before the age of 30 and the muscle you gain during that time will never go away (with a minimum of training).
The earlier you start exercising, the less difficult it will be to maintain your body as you get older. Someone who has never exercised but wants to lose weight by their 40s will have a much harder time than someone who started exercising early.
More than that, working out has a significant impact on my productivity, mood and psychological health. It changed my life.
I regularly build MVPs or administration dashboards and TailwindUI saved me several hours of work.
With perspective, it's one of the best investments I've made. Moreover the Tailwind team regularly adds new templates.
Simplicity comes at a price.
[1] https://www.netlify.com/products/functions/
[2] https://zeit.co/docs/v2/serverless-functions/introduction
I hope to share it soon on Show HN.
For 2020, I will:
- Read 1.5 books a month.
- Launch my startup while being employed (I am currently working on the product).
- Enjoy life and the people around me.
- Less time on social network.
- Travel to at least 3 new countries.
- Develop my photography (and videography) skill.
- Try to write more than I read on HN.
- Propose to the most wonderful woman.
- Save money, as always.
May 2020 be even good !
I love the design, it's one of the most important thing I look at for a bag.
[0] - https://www.notion.so/
Can you go deeper ?
From years of watching master programmers, I have observed certain common patterns in their workflows. From years of coaching skilled journeyman programmers, I have observed the absence of those patterns. I have seen what a difference introducing the patterns can make.
Here are ways effective programmers get the most out of their precious 3e9 seconds on the planet.
The theme here is scaling your brain. The journeyman learns to solve bigger problems by solving more problems at once. The master learns to solve even bigger problems than that by solving fewer problems at once. Part of the wisdom is subdividing so that integrating the separate solutions will be a smaller problem than just solving them together.
Time
- Slicing. Take a big project, cut it into thin slices, and rearrange the slices to suit your context. I can always slice projects finer and I can always find new permutations of the slices that meet different needs.
- One thing at a time. We’re so focused on efficiency that we reduce the number of feedback cycles in an attempt to reduce overhead. This leads to difficult debugging situations whose expected cost is greater than the cycle overhead we avoided.
- Make it run, make it right, make it fast. (Example of One Thing at a Time, Slicing, and Easy Changes)
- Easy changes. When faced with a hard change, first make it easy (warning, this may be hard), then make the easy change. (e.g. slicing, one thing at a time, concentration, isolation). Example of slicing.
- Concentration. If you need to change several elements, first rearrange the code so the change only needs to happen in one element.
- Isolation. If you only need to change a part of an element, extract that part so the whole subelement changes.
- Baseline Measurement. Start projects by measuring the current state of the world. This goes against our engineering instincts to start fixing things, but when you measure the baseline you will actually know whether you are fixing things.
- Call your shot. Before you run code, predict out loud exactly what will happen.
Concrete hypotheses. When the program is misbehaving, articulate exactly what you think is wrong before making a change. If you have two or more hypotheses, find a differential diagnosis.
- Remove extraneous detail. When reporting a bug, find the shortest repro steps. When isolating a bug, find the shortest test case. When using a new API, start from the most basic example. “All that stuff can’t possibly matter,” is an expensive assumption when it’s wrong.
> E.g. see a bug on mobile, reproduce it with curl
- Multiple scales. Move between scales freely. Maybe this is a design problem, not a testing problem. Maybe it is a people problem, not a technology problem [cheating, this is always true].
- Symmetry. Things that are almost the same can be divided into parts that are identical and parts that are clearly different.
- Aesthetics. Beauty is a powerful gradient to climb. It is also a liberating gradient to flout (e.g. inlining a bunch of functions into one giant mess).
- Rhythm. Waiting until the right moment preserves energy and avoids clutter. Act with intensity when the time comes to act.
- Tradeoffs. All decisions are subject to tradeoffs. It’s more important to know what the decision depends on than it is to know which answer to pick today (or which answer you picked yesterday).
- Fun list. When tangential ideas come, note them and get back to work quickly. Revisit this list when you’ve reached a stopping spot.
- Feed Ideas. Ideas are like frightened little birds. If you scare them away they will stop coming around. When you have an idea, feed it a little. Invalidate it as quickly as you can, but from data not from a lack of self-esteem.
- 80/15/5. Spend 80% of your time on low-risk/reasonable-payoff work. Spend 15% of your time on related high-risk/high-payoff work. Spend 5% of your time on things that tickle you, regardless of payoff. Teach the next generation to do your 80% job. By the time someone is ready to take over, one of your 15% experiments (or, less frequently, one of your 5% experiments) will have paid off and will become your new 80%. Repeat.
The flow in this outline seems to be from reducing risks by managing time and increasing learning to mindfully taking risks by using your whole brain and quickly triaging ideas.
You are more likely to spread your ideas about open internet in a public place like Medium than the faraway countryside like your website.