O look another amazing and riveting discussion on emerging technology with real world implications… o wait it’s just a bunch of cranky people complaining about crypto.
Readit Newsbogota commented on Canadian math prodigy allegedly stole $65M in crypto theglobeandmail.com/busin... · Posted by u/bookmtn
Dead Comment
Dead Comment
Dead Comment
bogota commented on El Salvador abandons Bitcoin as legal tender ticotimes.net/2025/02/02/... · Posted by u/smallerfish
If you need to go to the IMF for a loan of ~3% of your GDP to mitigate the risks associated with Bitcoin, well, that's a pretty good sign that adopting Bitcoin as legal tender was a pretty disastrous failure.
Where did you draw that conclusion? Because nothing in the article or reality would lead one to believe that.
bogota commented on String of recent killings linked to Bay Area 'Zizians' sfgate.com/bayarea/articl... · Posted by u/davikr
… i can’t think of a faster way to lose support from others.
bogota commented on Ross Ulbricht granted a full pardon twitter.com/Free_Ross/sta... · Posted by u/Ozarkian
I feel like I'm taking crazy pills reading the comments on this thread. Multiple teenagers (one in Australia) died from the drugs distributed on Silk Road. Ross was ok with selling grenades, body parts, etc on there. But everyone is saying he served his time ???
Maybe spend a little less time reading propaganda.
bogota commented on Six Sins of Platform Teams serce.me/posts/2025-01-07... · Posted by u/kaycebasques
You describe the toxicity I have experienced working in the product team vs a platform team.
If you don't find it interesting to build products with whatever tool is most adequate (excel some times) maybe you should not work at a company building products. At least you should understand that you are part of the support team not the main guy.
And yes, moving to GitHub from Jenkins is maybe objectively a good choice. But if it stalls product development for 6 months, is that objectively-objectively a smart move? It could of course be, but it requires more situational awareness than "is this tool better".
Platform teams also need to make calls where the experience might be worse for some but collectively better for the company.
This is normally where you see the product engineers start to freak out.
Counterpoint: nope.
Logging is great for long term issue resolution. There's tracepoints/logpoints which let you refine the debugging experience in runtime without accidentally committing prints to the repo.
There are specific types of projects that are very hard to debug (I'm working on one right now), that's a valid exception but it also indicates something that should be fixed in our stack. Print debugging is a hack, do we use it? Sure. Is it OK to hack? Maybe. Should a hack be normalized? Nope.
Print debugging is a crutch that covers up bad logging or problematic debugging infrastructure. If you reach for it too much it probably means you have a problem.
What is the difference between print debugging and logging? With most deployments setups now days you can pipe prints to some logging solution anyways.
Just use jsonnet if you want this IMO. No need to change json into yaml.