- You can just focus on the content and speak naturally. It is extremely smart in applying punctuation and formatting.
- You don't need expensive Microphones to get good accuracy. The crappy microphone that comes with your laptop should be good enough.
For me Dragon was pretty much unusable without expensive microphone setup. And even then, it needed constant intervention for punctuation and formatting.
Here's an example of what I mean. In these tests, I just spoke the words, I did not dictate any punctuation. Mistakes annotated by ~
VoiceBuddy (with microphone built into my cheap Logitech Webcam):
The color of animals is by no means a matter of choice. It depends on many considerations, but in the majority of the cases tends to protect the animal from danger by rendering it less conspicuous. Perhaps it may be said that if coloring is mainly protective, there are to be but few brightly colored animals. There are, however, not a few cases in which vivid colors are themselves protective. The kingfisher itself, though so brightly colored, is by no means easy to see. The blue harmonizes with the water and the bird, as it darts along the stream, and looks almost like a flash of sunlight.
Dragon 15.6(with the same microphone), unusable due to recognition errors:
~the color of ~monuments~ is by no means a matter of choice~ ~it depends on many considerations~ but in the majority of the cases tends to protect the animals from danger by rendering it less conspicuous~ ~perhaps it may be ~saidthat~ if coloring is mainly protective~ ~and~ ~not~ to be but few brightly colored animals~ ~there are~ however~ not a few cases in which ~we~ ~would~ colors ~of~ themselves protective~ ~the kingfisher itself~ though so brightly colored~ is by no means easy to see~ ~the blue harmonizes with the water ~the~ bird~ as it darts along the stream~ and looks almost like a flash of sunlight~
Dragon 15.6 (with $220 high-end microphone setup - Sennheiser):
The color of animals is by no means a matter of choice. It depends on many considerations~ but in the majority of the cases tends to protect the animals from danger by rendering it less conspicuous~ ~perhaps it may be ~saidthat~ if coloring is mainly protective~ there are to be but few brightly colored animals~ ~there are, however~ not a few cases in which we would colors are themselves protective~ ~the kingfisher itself, though~, so brightly colored~ is by no means easy to see~ ~the blue harmonizes with the water and the ~board~~ as it darts along the stream~ and looks almost like a flash of sunlight~
LAMP with dynamic webpages (I assume your approach) works just like it ever did (besides SSL)
But are you really keen to make a PHP dynamic webpage application where each page imports some database function/credentials and uses them to render html?
Can you keep the behavior of fluent userflow (e.g. menu not rerendering) that way? Only with minimal design.
When in 2006 most webpages had an iframe from the main content, an iframe for the menu, and maybe an iframe for some other element (e.g. a chat window), it was fine to refresh one of those or have a link in one load another dynamic page. Today that is not seen to be very attractive and to common people (consumers and businesses), unattractive means low-trust which means less income. Just my experience, unfortunately. I also loved that era in hindsight, even though the bugs were frustrating, let alone the JS binding and undefined errors if you added that...
I was doing web development in 2006 and that's not how it was. Websites were not all in i-frames and they were not all insecure. Setting up a PHP dynamic website with Apache does not have to be insecure and didn't have to be back then, either.
You can make modern single-page web apps with a LAMP back-end if you want. PHP is perfectly capable of serving database query results as JSON, and Apache will happily serve your (now static) HTML and JS framework-based page.
If you start peaking success, you realize that while your happy path may work for 70% of real cases, it's not really optimal to convert for most of them. Sentry helps a lot, you see session replay, you get excited.
You realize you can A/B test... but you need a tool for that...
Problem: Things like Openreplay will just crash and not restart themselves, with multiple container setups, some random part going down will just stop your session collection, without you noticing.. try to debug that? Goodluck, it'll take at least half a day. And often, you restore functionality, only to have another random error take it down a couple of months later, or you realize, the default configuration is only to keep 500mb of logs/recordings (what), etc, etc...
You realize you are saving $40/month for a very big hassle and worse, it may not work when you need it. You go back to sentry etc..
Canine just makes deploying sentry / grafana / airbyte + 15k other OS packages a one click install, which then just gives you a URL you can use. Because its running on top of kubernetes, a well built package should have healthchecks which will detect an error and auto-restart the instance.
Obviously if [name your tool] is built so that it can be bricked [1], even after a restart, then you'll have to figure it out. Hopefully most services are more robust than that. But otherwise, Kubernetes takes care of the uptime for you.
[1] This happened with a travis CI instance we were running back in the day that set a Redis lock, then crashed, and refused to restart so long as the lock was set. No amount of restarts fixed that, it required manual intervention
I totally agree with your suggestion for ordering, self-reporting the success and the "if x then imagine y!" you discuss and I get you didn't ask for criticism, but in your last example - the value of coffee to you might not be what it costs to make. The value can be a lot more for some people than others:
- Utility-wise:
If you need to perform at work.. even if having it every day means the coffee nolonger changes from your original no-coffee baseline..
- Social:
My girlfriend doesn't really go to the expensive coffee shop because it's worth the 2x marker. It's because she can chat about relationships, have security in her relationships with her friends and they can designate this as an unscheduled-long time to talk through issues
- Regulating your emotions
For me at least buying something small and pleasant can avoid troughs/peaks. In fact overstressing the financial ratio of cost:price of a product causes these troughs for me. That's also why poorer people often buy small but tasty things, even when it's pricy for them, it regulates their mood up enough to slog through the rest of the 1am shifts with difficulty seeing the future (I have been there...)
That's why I'd be wary of having an app pressure you not to buy something. You don't always know the real reasons your body gets you to do things.
Utility-wise: I specifically mentioned same amount of coffee so this one is moot.
Social: most coffee is consumed for takeaway and on Auto-Pilot. In the usa most starbuckses make 80%! From takeaway and 20% from sit ins (they tried to close some Starbucks locations because of this but the funny part is that sales drop more than the 20%... Probably because people take the "cost of the store" into their reasoning why they are spending 7-12$ on a cup of Joe.)
-regulating your emotions: if you are in a luxury position that's fine... Being / perceiving / stressing about being poor causes a drop of 8 IQ points. I know/understand what you mean and changing a default always causes stress but the question is always about short term pain vs long term gain...
Nobody likes to change... Being told what to do... The app is not pressuring you - it's making you aware of options / costs that you might not have considered. (Did you know)
The thing is that if the app is well made and you trust the maker you know you have a "friend" who is looking out for you... Even though you might still ignore him/her (think friends who smoke cigarettes etc...)
The brain's main goal is not too think because it tries to preserve energy... Unfortunately the environment is simultaneously safer (we killed all animals that literally can kill us) and more dangerous (our fellow humans who used to stand next to us having our back against the animals are often against our interests now.)
The question is always what is a low effort high reward substitute...
I'd say takeaway coffee is probably one of the best options for a lot of people.
The art is just to visualize the profit you're gonna make in the future in the now --- because your brain focuses on the now...
If I said to you that if you drink a coffee less every other day you'd "make" 4140$ in 5 years would you --- pretty sure for most people in dire financial straits they would... On the other hand not meeting with your friend for brunch once a month might save you more even but a friend is harder to substitute than some sugary beverage...
The question is always "why" - the "suffering" now is always certain (change is painful if it is not perceived as improvement) but by making the future gains big, visual and realistic people (can be) more self motivated.
I would say I wouldn't agree, but maybe our language in common is why we don't agree - for example, the idea that coffee is 80% takeaway... this global report puts it at 65% in cafe. My experience in most of europe is about 75% in cafe: https://www.grandviewresearch.com/industry-analysis/cafe-mar...
So maybe your use of coffee is just different to you know, the old world ways that developed it.
I said most coffee is consumed take away...
With the report you mentioned (65%) that is still correct.
I pointed to Starbucks for the 80% angle...
I currently live in Vietnam and I'd say it's probably 50% or less takeaway depending on the day and the venue (most takeaway is done from little stands that don't even have place to sit...)
I do have to say your "the old world ways that developed it." Is wrong on all counts...
1) I'm European and have consumed coffee in Europe... As well as America, Vietnam, countless other places.... over extended periods of time...
Context being everything aka american forum etc.... Unless a location is explicitly specified it would make sense to put it in an american context.
2) coffee drinking came from the middle east to Europe so unless you're using "the old world ways" to mean the middle east... (which would be an uncommon language / culture thing on your part.)
Again I understand your context but in this final post you really seemed to get nitpicky and rather look for where "he's wrong" rather than a quest for truth.
Anyway to speak/write or to communicate/seek that's the question. Have a nice day
As you age your interests and curiosity change, in ways you often don't see until later.
Very common in computer science contexts. Young undergraduates always pick up the new tech and make something that seems alien and wrong first. It's not even the masters students.
Possibly the same Kiro - Agentic IDE post would have been as interesting to you as the launch of Atom or something related to VS Code, etc.
90% gravity / 90% done is a bad perspective. You don't really have data on how long the false positives would have taken to succeed.
Unfortunately, getting from 0 to $100 in revenue isn't always much harder than $100 to $200. Even though the first $100 is insanely hard, so can the next $100 be. People don't like to talk about this in the startup space but the statistics at innovation centres for startups etc are insanely clear: at any given revenue, most startups are only going to keep it above the current value for part of the next 6 months, then crash and burn. And upwards line, let alone exponential growth, is an outlier (and still leads to revenue decline the next year most of the times it happens). Unfortunately, finding something that works (a fly well or net ROI positive channel) often takes so much time maintaining you take your eye and progress off other aspects you would have focused on for success and it becomes a revenue wave when it stops working rather than a stable way to grow.
Second problem is young people think they won't tire.. after three years almost anyone has a period of burnout. Atleast althetes like Olympians or Baseketball players have off seasons, with startups, it's not so. This is why having great people with you who flux at different times and take care of stuff you take your attention of increases success, if you can keep conflict minimal. Yet, most young people also don't want to relinquish control, if they are honest.
Dealing with 5 year old code is okay now. In 10 years it will cause you pain. It's like going back to an ex after you lose attraction. It never works out and hurts both parties (in this case your users, because you won't maintain it or want to pretty soon)
And or if you got any dependencies (even to "open" 'stuff') when vulnerabilities and bugs arise that will break the backwards compatibility to your codebase you will definitely be tempted/lured/asked to spend "only 5 mins" to update it.
Just don't. Keep a copy wherever others suggested, keep a photo in the folder with the ex-bf/gf think about it every few years (I wonder how she is doing - in a Morty voice) and quickly move on!
Good advice and beware the difference between docker export (which will fail if you lack enough storage, since it saves volumes) and docker save. Running the wrong command might knock out your only running docker server into an unrecoverable state...
