1,492 karma · joined January 23, 2024
- someone else proxied your API to the public
- someone else leaked credentials you assigned them in the public code of a game
As someone working on a team that publishes APIs to the greater large organization, you can't trust other people. People be doing wild things.
Been on teams where every individual was free to use their best judgement, we didn’t have a lot of documented processes, and… nothing ever went wrong. Everyone knew sloppy work would come back and bite, so they just didn’t ever do it. Deadlines were rarely a problem because everyone knew that you had to estimate in some extra time when presenting to stakeholders. And the team knew when to push back.
On the other hand, I’ve been on teams where you felt compelled to define every process with excruciating detail and yet experienced people somehow screwed up regularly. We didn’t even have hard deadlines so there was no excuse. The difference between implicit and explicit error handling would have not mattered.
At the end of the day, some of these teams got more done with far fewer failures.
We have a drug now that you can take so you won’t catch HIV, as well as another drug for HIV+ that keeps it at bay.
We haven’t found a cure-all. Rather, now we have a lot more treatment options nowadays depending on your specific cancer or illness.
Idk. Even in Jira tickets, I write a short background section to bring everyone up to speed.
I like when everyone gets a chance to be on the same page.
I know the biggest complaint with checked exceptions is that people tend to just use catch all exceptions, but that’s just sloppy work. If they’re a junior, that’s when you teach them. Otherwise, people who do sloppy work are just sloppy everywhere anyway.
As a way to ultimately render a view, it has never been elegant.
I’ve done it every possible way:
- Templating libraries
- XHTML with embedded XML data
- XML and XLST
- XML embedded in JavaScript (EMCAScript), aka React before React existed
- React, which is similar EMCAScript
I used the first public releases of React. I was immediately sold. No one had to sell anything to me. I knew it was going to win.
I can’t imagine anyone with strong experience in all these ways possibly think that these other ways are more enjoyable.
p.s. I’m not talking about Redux. I was never sold on Redux/Flux.
I'm not sure having a smartphone has at all impacted their outside time.
Which comes in very critically when chucking away trash overhand in public and you never want to embarrass yourself.
I would trade that for one piece of mediocre abstracted code any day.
Oh yeah and everything in the codebase is copy and pasted.
Let’s take Markus: before he made Minecraft, he made relatively mediocre games that didn’t get much traction. Minecraft was an exact copy of someone else’s game (Infiniminer) that was posted on the same forum that he went to. He saw potential when its original creator did not (the creator of Infiniminer got angry that people extended his game so he shut it down). Minecraft blew up. The games that Markus made after Minecraft? Relatively mediocre again.
So what can you learn from the example of Markus? Nothing. Nothing at all. Sometimes you just get lucky.
I’m just speaking from my experience. I put a lot of practice into things that I am also talented at and life is good. shrug
I put practice into other things like cooking and music too but I’m not going to become a chef or play music for anything but fun.
- All of us are more naturally talented at some things.
- When you end up working with your natural talents, you have it easier than everyone else.
- Working in your talents often translates to passion, and that’s how you get the so called “agency.”
- To find your talents, you have to try everything once (e.g. wakeboarding, tennis, programming, accounting).
- More well off parents can offer their kids more opportunities to find their talents.
- Schooling and “doing” are orthogonal to finding your talents. Neither learning or doing will tell you your talents, passion, or give you agency, but you should do them both anyway.
I also don’t get people who look up YouTube videos on how to do things in Factorio.
What’s the fun part left to do if you just use someone else’s factory or belt design?
Covered in [The Whatever Times] was an article about something something,
Seems they still have the docs up: https://www.php.net/manual/en/book.pthreads.php
You could make asynchronous servers using socket_select(), which was added in PHP 4.1.
https://www.php.net/manual/en/function.socket-select.php
There was also a third party extension that added threads to PHP 15 years ago, although it was buggy.
e.g. if you overtrain or don’t wait long enough after an injury, you may permanently damage something forever. Speaking from personal experience and knowing a lot of people who have done the same. There’s also some documentaries about athletes doing it and losing it all. Go the extra mile but don’t look back and have regret about that one time.
Why would Tesla have been invited to a summit that was primarily centered around United Auto Workers? Tesla is non-union. “EV” was only a pretext.
The summit didn’t invite any non-US carmakers, who also make EVs. It was an event about UAW. Everyone invited was UAW.
The administration even said as much: https://cleantechnica.com/2021/08/05/white-house-answers-why...
And I'm big on reusability because I'm lazy. If requirements change, I rather tweak than rebuild.
It's no conspiracy why nuclear never gets traction these days -- maybe it was cost-effective 10-30 years ago but renewable technology has gotten relatively cheap. (Shutting down active nuclear reactors earlier than needed is a whole different issue though.)
Here's the report for 2023: https://www.eia.gov/outlooks/aeo/electricity_generation/pdf/...
There is no report for 2024 because they are building a new model to take into account even newer technologies: https://www.eia.gov/pressroom/releases/press537.php
It is still the basis for a lot of WYSIWYG editors, but it's not perfect and sometimes provides too little control (produces messy HTML), so sometimes people avoid it and build a WYSIWYG editor from scratch using something like <canvas> (e.g. Google Docs) but this is way more effort.
Some of the O.G. WYSIWYG editors (e.g. CKEditor) still use "contenteditable" but patch over all the problems with it.
People build outwards first and then upwards.
Because when you study people who eat a certain thing, they also all tend to eat another thing.
I religiously read nutrition labels and a lot of vegan ultra-processed foods are not particularly healthy, but not necessarily because they are ultra processed but because they mimic non-vegan foods which themselves are unhealthy.
Even if you cook all your meals, it doesn’t mean that you are eating healthy because it still depends on your ingredients.
And as the article hinted to, a lot of people who initially start eating vegan foods tend to buy non-vegan analogues which are not healthy. The better analogues tend to be ultra processed. Are these people at higher risk of certain diseases because they are eating ultra processed foods or because they’ve limited themselves to unhealthy vegan substitutes? Hard to say.
Other people just have very different values and the direction of an organization reflects this.
I see people bifurcated into "people good at time estimates" and "people who think time estimates are always wrong." The former have been keeping track, improved continuously, and have become good. The latter have no clue.
Setting up a website from scratch is not hard, but it is time consuming, especially when you throw in maintenance.
And long before the Internet, people slapped random concoctions together and sold them as medicine, advertising them as cure-alls.
But I feel like soldering something is no different than just like splicing a telephone cable in half and putting your own headset in the middle…
Except instead of putting a headset, you crudely use a lighter…