scott_w

31 ms·

601.
by scott_w 1y ago
> Maybe you had the luck of learning 0 based language first. Then most of them were a smooth ride. Given most languages since at least C have 0-based indexing... I would think most engineers picked it up early? I recall reading The C Pro
602.
by scott_w 1y ago
Yes, I think you are. The challenges people describe with Rust look more difficult than remembering to start from 0 instead of 1…
603.
by scott_w 2y ago
You’ll have been on a variable speed zone of the motorway which is covered in cameras to enforce the limit reductions. People tend to behave themselves when they think they’ll lose their toys. If you drive in an area that’s known to not be
604.
by scott_w 2y ago
Semi-related: this type of thing is actually covered in the Site Reliability Engineering book by Google. They highlighted a case of a system that outperformed its SLO, so people depended on it having 100% uptime. They "fixed" this
605.
by scott_w 2y ago
> My only point has been, "Pythonic" things tend to be pretty liberal in what they accept Being able to use a string as a string and an int as an int are not “pretty liberal in what they accept,” it’s just programming language
606.
by scott_w 2y ago
Well yes but the alternative is to never make language improvements because legacy code exists.
607.
by scott_w 2y ago
I know about Decimal/int mixing but that’s for a good reason: it’s fine to intermix here. But not for floats (precision issues). The bool/int mixing isn’t “good.” It’s a bad implementation detail that Python is stuck maintaining f
608.
by scott_w 2y ago
You wouldn’t really do your example, though. If you’re using an f-string, you’d just directly interpolate, because it’s convenient. You wouldn’t use an extra library to properly make it safe, otherwise you’d just use a proper template libra
609.
by scott_w 2y ago
That Python lets you blindly interchange different types for no good reason. It simply doesn’t. Yes, it’s common for Python to be strict for inputs when the types are different. For example, try: Decimal(‘3.0’) / 1.5 You’ll get an erro
610.
by scott_w 2y ago
That’s a library author problem, so it’s less likely since library authors tend to be fewer in number and, for popular libraries, get a reasonable number of eyes on this type of change.
611.
by scott_w 2y ago
Programmers being lazy and shit at their jobs is not a reason to not improve the language.
612.
by scott_w 2y ago
Er… that’s just not correct? Python can be more liberal but it’s not always. It depends entirely on the tooling. Libraries will take time to catch up but I can definitely see people creating libraries that enforce t-strings, even if they’re
613.
by scott_w 2y ago
Because, as the article states, people aren’t using prepared statements. Instead, they pass f-strings because they’re more convenient.
614.
by scott_w 2y ago
Pretty much, yeah. The article highlights that people were using f-strings directly, and they wanted to provide an alternative for lightweight template/interpolation.
615.
by scott_w 2y ago
Your problem is you can’t really pull this out of evil people so easily. They’ll happily lie to your face, despite evidence you present to the contrary. The truth is a flexible concept to them.
616.
by scott_w 2y ago
> People will shut off the moment they get the full file. Perhaps but the time spent downloading it is also time spent uploading some of the file, so there's still some benefit. By having it in random order, you more evenly dist
617.
by scott_w 2y ago
This is only useful if the person is arguing in good faith, something a quick listen to Nick Ferrari, Nigel Farage, Ben Shapiro or any other shock jock will quickly disabuse you of.
618.
by scott_w 2y ago
So a couple of things: 1. The EU has that reprieve. Given the EU can bite back, it's possible that reprieve becomes permanent. 2. Last time Trump slapped tariffs on UK + EU, Biden prioritised reversing tariffs on the EU first because
619.
by scott_w 2y ago
You get a letter from your delivery company (in the UK, usually the Post Office or Royal Mail) with a link to pay import taxes. Once you pay, the delivery is scheduled. Depending on country rules, it is sometimes possible for the sender to
620.
by scott_w 2y ago
> Pretty much all drivers agree that most or all of these requirements are reasonable Twitter used to be a great source of taxi drivers bitching about getting caught on their phone, driving dangerously, driving drunk, no insurance, expir
621.
by scott_w 2y ago
> It is interesting how hostile cyclists are to any suggestion of regulation, even for safety. Wait until you hear about this group of people called “drivers.”
622.
by scott_w 2y ago
First link from searching Google: https://www.cyclehelmets.org/1194.html#:~:text=The%20enactme...
623.
by scott_w 2y ago
Bear in mind, Australia has strict bicycle helmet laws that mean fewer riders (higher % of enthusiasts), so maybe it's a higher chance that they're ragging their bikes harder? It could also be the classic bad workmen blaming our t
624.
by scott_w 2y ago
Your second paragraph perfectly explains why your suggestion in your first paragraph doesn’t happen.
625.
by scott_w 2y ago
Honestly, no. There are times when you want to get low level but, when you do, you need to commit to learning that domain as well as the problem domain you’re being paid to solve. If those are disjoint, well, have fun!
626.
by scott_w 2y ago
The author wrote a blog post describing that the problem is datetime inherits from date when it shouldn’t. The fact they do but can’t be compared is a compounding of the problem with hidden bugs
627.
by scott_w 2y ago
Given the list of issues (most of which I had never heard of) that the library author describes with datetime, I think I trust his tests over the ones I’d write. Given how many tests I see fail on 29th February at the companies I’ve been at
628.
by scott_w 2y ago
A member of staff who goes “poof” as the only one who understands your wrapper library that has a critical bug is a more common kind of hidden debt.
629.
by scott_w 2y ago
It's not about forcing every Dev to learn every aspect of Ops work. It's about ensuring the team that builds the feature manages its delivery end-to-end, including dev, test, deployment, failure response. The reason for this is, a
630.
by scott_w 2y ago
> Having 10,000 production ready features with 97% uptime and no backups is not desirable You’re the only one making this strawman argument, here. > the 10+deploys a day talk Most teams aren’t doing this outside of a rush to wrap up a

More ›