“It’s cheaper..” will grab attention. If you write anything thing else in the first 2 words you may not have had the same effect as people’s attention span is low
"Many of the passengers survived the initial crash, but they had disregarded, did not understand, or did not hear Leul's warning not to inflate their life jackets inside the aircraft, causing them to be pushed against the ceiling of the fuselage by the inflated life jackets when water flooded in. Unable to escape, they drowned."
The litmus test on this used to be those NFL Superbowl shirts for the losing team. To facilitate quick merchandising, they would print both teams as being the superbowl champions then whichever team one, sell that t-shirt. The losing teams 'champion' shirts would pop up in photos six months to a year down the road, being worn by children in third world countries. You don't see that anymore.
This is completely wrong. My laptop can solve the equations in fractions of a second. I believe that with some optimizations it should be trivial to do the calculations on a 1960s mainframe.
I can’t speak to rbenv or npm, but IMO it’s better of use well known and canonical tools for each rather than a more unknown mega tool that wraps or replaces these.
pyenv isn’t perfect, and isn’t what I’d use for prod images, but for dev setup it’s relatively bulletproof and less issue-prone than any alternative I’ve seen.
In a perfect world yes that is true, but I've worked at multiple places where Jira got reshuffled by someone and either entire projects got deleted or ticket ids were reset.
Slack history and requirement documents are rarely linked in commit messages and looking through thousands of documents and channels to search the context of a commit is nauseating.
There's never a need to write an essay in a commit message, but 2-3 paragraphs won't kill anybody either.
I actually tried to implement this exact feature about a year ago, but gave up after a day of working on it because it seemed too difficult. Given this feedback, it might be worth trying again. Thank you!
anything that is not in the commit message or in the commit itself is practically useless. documentation covers how to use a thing. it usually doesn't cover why a change was made. that why also normally does not end up in code comments, and even less so would be aparent from the change it self. the commit message remains the only place where the why can be documented meaningfully and along with the change where it is needed.
at least in my current project working with legacy code that i am not familiar with, the why is the most important detail about a commit.
Most teams I've been on just link to the PR from Jira and Slack. The PR links to the commit message, and the commit message explains the change.
Other stuff like "this is ready, can you review it?", or "we can ship feature X now" lives in the other tools.
Note that (in the rare case where you want to), you can then search for links to old PRs in the other tools. Also, putting the jira ticket number in the commit message usually makes sense.
I’d interpret ”Constactless card” as some form of RF variant of a traditional ticket card. Not as a way of describing your regular visa/mastercard debit/credit cards. Is “contactless card” a normal way of describing a debit/credit card? Can’t any rf card be said to be contactless?
The big revolution elsewhere was the transition from RF based ticket cards to RF based regular credit/debit cards. They’re both “contactless” though but one is s a hassle.
You don't need to keep track of aliases, can just as easily use your "one correct" way and never learn/forget the alternatives, so what's the downside? In general, the overhead of remembering precise tool-specific command is higher that using some common knowledge from other tools you remember that are aliased in this tool
> If you ever pull up a debugger and step through an async Rust/tokio codebase, you'll get a good sense for what the overhead here we're talking about is.
So I didn't quite do that, but the overhead was interesting to me anyway, and as I was unable to find existing benchmarks (surely they exist?), I instructed computer to create one for me: https://github.com/eras/RustTokioBenchmark
On this wee laptop the numbers are 532 vs 6381 cpu cycles when sending a message (one way) from one async thread to another (tokio) or one kernel thread to another (std::mpsc), when limited to one CPU. (It's limited to one CPU as rdtscp numbers are not comparable between different CPUs; I suppose pinning both threads to their own CPUs and actually measuring end-to-end delay would solve that, but this is what I have now.)
So this was eye-opening to me, as I expected tokio to be even faster! But still, it's 10x as fast as the thread-based method.. Straight up callback would still be a lot faster, of course, but it will affect the way you structure your code.
Improvements to methodology accepted via pull requests :).
--> The solution involves integrating a prompt-based paywall, which requires chat users to purchase a subscription via Stripe and validates the subscription by verifying the user’s email at the start of every conversation.
So no free tier/trial? I would highly recommend you implement a paywall after /near the user's "aha" moment. If that is after one chat / part of one/ multiple interactions that is where it needs to be.
You are in a growing market and are trying something different, you need to let prospects experience what differentiates you, before asking for a credit card. Esp if your audience is early-adopter, techies.
This seems to be over-analyzing. I take it to mean it didn't feel like any kind of physical object to him. You know how in the moment you're either going to react with "oh shit!" or "curious..." because you made an unconscious snap judgement. I don't think he deeply considered how different alien physical objects could behave with far advanced science, then decided how to feel about that.
You're saying there's no American Airlines near where you live? I find that hard to believe.
Regardless, even if you fly into phoenix, that's not a 4 hour drive away.
Regardless, even if a few underserved locations in the US are a 4 hour drive away from their nearest airport, it doesn't mean that EVs don't make sense as a rental car.
I find writing commit messages helps my development flow:
Why did I spend an hour refactoring 1000 lines of rust code again?
It worked the first time I got it to compile again, so it's probably fine, but it was a subtle non-functional change. I'd better commit + write a good message so:
- I don't forget why I just did that
- In case I need to back out the next step
- So that my coworkers know what I'm up to, and don't ask me on slack.
There were also some Java CPUs, which directly executed bytecode, in which case a "Java driver" would just be the lowest, system-level language available: https://en.m.wikipedia.org/wiki/Java_processor
