Literally only reason I started looking at potentially (but most likely not) getting a PS5 is because Rockstar refuses to release PC versions together with console versions...
Because not all code is yours. In a team, the time spent on “rabbit holes” adds up, increasing the risk of bugs. A `slower` but predictable language can lead to more consistent, maintainable code, which is often more valuable in the long run or last but not least, running in production.
> In a team, the time spent on “rabbit holes” adds up, increasing the risk of bugs.
It adds up with the number of people on the team? Or the number of people on the team squared? Cubed? nlogn? Because a lot of those options would still favor the former language.
And if it's happening particularly often, that means the rate will fall off drastically as mastery is achieved.
I see a risk when code does something different from expectations. I don't see any risk when code has some kind of novel syntax that requires looking it up. Or when you learn about a feature from the documentation or a blog post.
Being predictable is quite valuable, but predictability is different from memorizing every feature.
I found an old Leap Motion device in a storage box with USB devices last week. The support you provided for it was great and had me waving at my desk all day.
Even though the Leap Motion is now unsupported, I still enjoy using BTT daily.
Haha, yes Leap Motion was a lot of fun and I think the BTT integration landed me my first job (@Siemens) after university. That must have been almost 10 years ago -- yep: https://www.youtube.com/watch?v=SDJKFtLDx4k
Wait, the software I’ve been using for what feels like decades and which always gave me a charming, cosy old school vibe due to its almost infinite options and deep understanding of OS X/macOS was written by someone younger than me!?
Mind blown.
It’s an incredible tool and among the first things I install on a new Mac.
oh that's cool. I have the original (first version) of the Leap Motion in a box somewhere. Now I want to pull it out and install BTT and see what I can do with it.
When I was briefly working in a construction plant. Weekends is when non critical or potentially risky operations on machinery would be done, as to not block the production chain during workdays.
I've yet to see the place that had the level of testing, and infallability of the CI process, to where I wanted to deploy on a Friday. Yeah, it may be a low chance that anything will go wrong, and an equally low chance we'll be unable to easily rollback, but so few things can't wait until Monday that I want to roll those dice.
reply