I try to always reply honestly when talking about having kids. And I'm lucky to only have friends who do the same.
Usually I say something like "It's really hard, but it's so awesome at the same time that you forget how hard it is all the time. In the end, you feel like it's worth it."
I confess I wasn't that positive when I was totally sleep deprived. I also have the impression that no two situations are the same... Some parents have it very tough while some others have quite an easy time with their kids. You gotta have some luck...
Learning: I learned a big deal of web development (HTML, CSS and JS) from view-source.
Tweaking: I sometimes fix broken closed-source/proprietary applications or websites by checking the source and writing a user script.
Those two can probably fall into the "Nerd" category, though...
I agree that discoverability and selection of well-maintained packages is problematic in node (I couldn't compare with .NET core though).
But I disagree with you on picking Express as an example of this. I see Express as stable and very well maintained. If by "rotting" you mean "no new feature added", then sure, but I'd consider it a good thing: it is mature and stable, and is used by a lot of people around the world to power pretty demanding apps.
Exactly my thought when I tried Vue.js: on the surface, it's knockout with some react-inspired additions that make it faster. I loved being able to pick up Vue.js and make something that just worked in 30 minutes.
I was pretty happy with openshift until I recently discovered it was impossible to update the version of an os package I depended on. On heroku, custom buildpack and it was done in 5 minutes.
I do the same. But my rationale for normal browsing with firefox is not about tooling, it's really about what OP says in the article. Agreed on the adress bar though.
In Belgium it isn't. What is often the case, though, is that you commit other crimes while escaping prison (stealing government property, violence or threats on guards, etc.) for which you're accountable.
I have this feeling with Intercom, that every bit of added value I want to extract next, I have to upgrade my plan or buy yet another plan. Their pricing pisses me off every single time, yet I pay every single time... after insulting them copiously.
They're that good.
At least for the Brussels one: the heist happened and was quite impressive, but the burglars didn't get away with it. They were caught pretty rapidly, weren't they?
In the CPH bridge solution too, you'll have to wait for the elevator to bring you upstairs, and another elevator ride to be back on the ground on the other side of the bridge.
Asking because it seems unusual to me, and I think those situations are really similar to what GP was referring to: "I paid to see what you had to say, but I don't like it so I'd like my money back". I can think of a lot of similar situations (movies, digital music, books, ...) where I wouldn't consider asking for a refund after I have consumed the content, whether I liked it or not.
Do you ask for a refund when you bought a newspaper and, after reading it, you don't like what you read?
Do you ask for a refund when you bought an app on the app store and you stop using it after 1 hour because it doesn't fit your need?
I think it probably depends on the amount you paid, though...
At least you can backup files. Applications, not so much...
I'd add that data should be stored in a standard open format, so that an application failure won't prevent you to 1. keep your data (because backups) and 2. use your data (because open format)
We implemented something similar 5 months ago, but wired to an event in segment (we don't use stripe).
The bot would post a random gif from giphy tagged with 'money'.
After a while we became tired of seeing Nicki Minaj appear in our slack...
Not sure, isn't the whole point of pipelining to avoid these domain-sharding workarounds?
This test case shows that the performance is better with the same code. The invert test case would show that the code is more complex (because of sharding) for the same performance (actually not quite, because of multiple handshakes).
My startup is currently discussing with a prospect/potential acquirer that was very clear about this: "We'll do it, with or without you, so you'd better accept our under-priced offer".
I'm not aware of any option to prevent any company to do that, is there?
> Visited-link styles aren't applied to links rendered in SVG images, so history information can't be retrieved, and native themes aren't rendered in SVG images, which makes it harder to determine the user's platform.