15 Matching Annotations
- May 2021
-
twitter.com twitter.com
-
Ashish K. Jha, MD, MPH. (2020, December 1). There is something funny happening with COVID hospitalizations Proportion of COVID pts getting hospitalized falling A lot Just recently My theory? As hospitals fill up, bar for admission rising A patient who might have been admitted 4 weeks ago may get sent home now Thread [Tweet]. @ashishkjha. https://twitter.com/ashishkjha/status/1333636841271078912
-
- Apr 2021
-
boardgamegeek.com boardgamegeek.com
-
Thanks for pointing out my poor wording in the review. You are of course, correct. I will edit the review accordingly.
-
-
store.steampowered.com store.steampowered.com
-
The game has been on sale for a year, but sales have been dismal.
-
-
store.steampowered.com store.steampowered.com
-
this game is purely amateur production, material selection and creation is not professional, just hope you can like this story.
-
-
github.com github.com
-
Yes, you are right. That was a very bad workaround. Stubbing methods on NilClass can be compared to switching to dark side of force. Powerful but comes with a huge price. I highly don't recommend using my workaround from 1 year ago.
-
- Mar 2021
-
store.steampowered.com store.steampowered.com
-
Ever want to experience a game that makes you want to play Rocket Ghost Aidan 2? Just play this! Its completely inferior to RGA 2.
-
-
github.com github.com
-
I'm not sure about all consequences of my change and this is very complex.
-
-
trailblazer.to trailblazer.to
-
Admittedly, both the signature and the return values of invoke feel a bit clumsy. That’s becaus we’re currently working with the low-level interfaces.
-
-
trailblazer.to trailblazer.to
-
The circuit interface is a bit more clumsy but it gives you unlimited power over the way the activity will be run.
-
- Feb 2021
-
trailblazer.to trailblazer.to
-
You’re allowed to blame us for a terrible developer experience in Trailblazer 2.0. It’s been quite painful to find out which step caused an exception. However, don’t look back in anger! We’ve spent a lot of time on working out a beautiful way for both tracing and debugging Trailblazer activities in 2.1.
-
-
trailblazer.to trailblazer.to
-
Around 2 years ago I decided to end the experiment of “TRB PRO” as I felt I didn’t provide enough value to paying users. In the end, we had around 150 companies and individuals signed up, which was epic and a great funding source for more development.
-
To make it short: we returned to the Rails Way™, lowering our heads in shame, and adhere to the Rails file and class naming structure for operations.
-
There is nothing wrong with building your own “service layer”, and many companies have left the Traiblazer track in the past years due to problems they had and that we think we now fixed.
Tags
- funny
- recant/retract/revert/withdraw your previous plans
- experimental
- freemium model
- discontinued products/services
- rails: the Rails way
- admit when you failed (failures)
- shift in preference
- more than one right way (no one right/best way)
- software preferences are personal
- admit the limitations/shortcomings of your argument/benefits
- transparency
Annotators
URL
-
-
github.com github.com
-
In this simple example, the destroy interaction doesn't do much. It's not clear that you gain anything by putting it in an interaction.
-
- Jul 2020
-
lwn.net lwn.net
-
Own the mistake. Say to yourself "I am human and I screw up sometimes" and remember that when you see somebody else screw up too.
Tags
Annotators
URL
-