It’s a load bearing S.
It’s a load bearing S.
There are so many more, and better!, options than testing in prod, but they take time, money, and talent and ain’t no company got time for that (for a business segment that “doesn’t generate revenue”)
Abraham Lincoln: Secretary of Ghosts
The “Big Boys” use tests to gauge when code is production ready, they don’t rely on a typing system and call it a day. I’ve seen monoliths made out of bash serve their purpose for years without a glitch, thanks to tests.
I used to work at a place that required daily progress reports on tasks (this was before agile took off so ‘daily standup’ wasn’t a thing.). So I wrote a script to schedule my git commits throughout the week (so that I had at least one a day), and every afternoon it would pull my git history, generate a summary, and email it to my manager.
He knew it was automated and hated me for it but I had the most consistent and detailed reports. On the upside, it really trained me to make good commit messages. On the downside It really instilled me with a strong “burn the building down” kind of vibe that persists to this day.
The whitespace is not only required, but it must be tabs and spaces.
That is 100% a chatbot using a regex email validator someone wrote as a meme that the chipotle dev copied from stack overflow without context.
As a Texan, I’d be remiss if I didn’t post about HEB:
Practically every store is different, they tailor them to the neighborhoods they’re built in.
https://thcshoanghoatham-badinh.edu.vn/descubrir-70-imagen-heb-interior/
Well, the secret is getting batteries as cheaply as possible, how you get there is the magic of capitalism*
I know this answer is flippant and dickish, but:
python3 -m http.server 80
shadowsocks seems to be the best way for now.
I heard this song for the first time yesterday, that’s so weird.
Yeah, I remember now. the name squatting was from people putting malicious packages under misspelled names of well known packages, like “requets” instead of requests.
packages installing but not working due to missing dependencies
This is the fault of the package author/maintainer
packages installing but not working due to broken dependencies
Sometimes the fault of the package author/maintainer. Sometimes this is the fault of a different package you’re also trying to use in tandem. Ultimately this is a problem with the shared library approach python takes and it can be ‘solved’ by vendoring within your own package.
packages not building and failing with obscure errors
Assuming the package is good, this is a problem with your build system. It’s like complaining a make file won’t run because your system doesn’t have gcc installed.
one package was abandoned and using Python 2.7
Unfortunately there’s a ton of this kind of stuff. I suppose you can blame pypi for this, they should have some kind of warning for essentially abandoned projects.
I don’t think it’s fair to blame pip for some ancient abandoned packages you tried to use.
I believe that was just name squatting.
They’re building out in Idaho, but the rising cost of pretty much everything globally slowed them down. They just got the approval for the cost increases in January.
It is, and it’s a valid complaint. Go and Rust have handled it differently than Python or JavaScript, and all of them have their faults and bonuses.