10 Tintin comics/books came as donations to my small school in a small town in India. Hardy boys were also donated but Tintin just hit the sweet spot for me.
I sometimes think it's the artsy design which feels so warm. As an 11-year-old, I was mesmerised by them. I didn't understand a ton of things Captain Haddock said with English being the 2nd language.
The adventures were sooo good. I saw the movie when it came out more than a decade ago and it brought back so many memories.
Even today, I love it's aesthetic design a lot. I discovered Asterix and Obelix when I was 17 and they had similar vibes and energy with their designs in them too.
Popular Indian comics at the time (Chacha Choudhary and others) were great too but the design aesthetic were worlds apart.
We build Spike.sh to be a very simple incident alerting alternative to Pagerduty. I had put shown this community what we had built 2 years ago as well (https://news.ycombinator.com/item?id=24503585)
It didn't get a lot of attention. eh!
I started Spike.sh (https://spike.sh) because I always thought the potential of incident management is a lot lot more. There are numerous things once can do but yet nothing has been done by any of the others, even OpsGenie (which is quite neat in itself)
Spike.sh is my attempt to improve the current systems of how incidents are handled.
Problems we are looking to solve
- alert noise
- a better way to classify incidents (symptom - cause - effect categorization of incidents)
- responder care (responders should be able to go into cooldown after resolving a critical incident)
- transparency for everyone and not just managers
- a more welcoming user experience
Since the last time I showed HN about Spike.sh, a lot has changed. Let the features stay aside, we actually got 100s of customers using Spike.sh. I hadn't ever imagined that could happen when I started. Super happy about it :)
Me and the team at https://spike.sh are incident management nerds. Its rare to find people interested in this practice. I usually keep my ears to the ground finding Incident management nerds, its not easy though.
Open to collaborate on content, practices, experiments, and in general of how different engineering and non-engineering teams across the world instill and follow incident management practices.
We named our product https://Spike.sh, an incident management product with alerts. Our server "spiked" is commonly used so we thought it made a lot of sense that we will alert every time it does.
It also fits into our target audience better. Allows us to foray into horizontal products too.
There are two types of commonly used names. One is a combination of two words such as Datadog and others are single worded like Spike, Stripe, Slack
Single worded domains are neat and are quite sticky in my opinion. I recommend it. We also live in a world of increasing adoption of rare tlds. Magic.link, reflect.run and plenty more. I believe people are leveraging it pretty well. We share our .sh tld with shell extensions, which is pretty cool.
For single words - stick to 6 or less characters and explore tlds other than .com
For double words - ensure at least one word is super relatable and one of the words is short. Peter Parker (pp) -> Datadog (DD) helps in remembering and using it more.
Rate of features added being high could be directly proportional to our code going obsolete sooner than later. Wouldn't it?
I also understand that Rust is quite backwards compatible which is good but a planned better version of releases would be easier for everyone to keep track, update codes, etc.
Is the rate of features being added high? Things that wouldn't even be a footnote in a new C++ release announcement can be highlighted in a Rust release announcement which may give the impression of lots being added but it ultimately doesn't amount to much.
As long as the compiler remains backwards compatible nobody forces anyone to rewrite programs that deliver their requirements at the time they were developed.
Major compatibility breaks occur on a very long time-frame and most certainly with a version bump prominent enough to draw anyone's attention. Personally, I expect builds to suddenly break on dependencies rather than anything else.
Rust is pretty stable. The point is that the work on Rust is happening so fast it's getting impossible to keep track of releases whilst making sure that your code doesn't go obsolete.
I think people just have to learn that "not using the newest features of the language" is not a problem. I have no problem with obsolete code, where "obsolete" means just that. I have a problem with broken code. If it ain't broken, no need to fix it.
One thing that makes these sorts of conversations tricky is that different people mean different things when they say stuff like "going obsolete." To some people, it means "this code literally doesn't work anymore," and to other people, it means "oh no the error handling library I use isn't in vogue anymore and I feel the need to re-write everything to use the latest library."
There is not a lot of the former, but there is some of the latter, and even if it's self-imposed, some people do feel that pressure.
I sometimes think it's the artsy design which feels so warm. As an 11-year-old, I was mesmerised by them. I didn't understand a ton of things Captain Haddock said with English being the 2nd language.
The adventures were sooo good. I saw the movie when it came out more than a decade ago and it brought back so many memories.
Even today, I love it's aesthetic design a lot. I discovered Asterix and Obelix when I was 17 and they had similar vibes and energy with their designs in them too.
Popular Indian comics at the time (Chacha Choudhary and others) were great too but the design aesthetic were worlds apart.