I like the system you have in place for it. I feel like I've been doing the same thing subconsciously without realizing how to verbalize it when others make that kind of mistake in code reviews. There's a difference between two methods that look similar and therefore should "reuse" code versus two methods that are referring to the same requirement and where if anything about that requirement changes then both methods should change even if the methods themselves look nothing alike.
The way Crystal and Dart 2 handles it? Null as a separate and unique type unrelated to Object where type unions solve the problem using syntax like `String?` that is equal to `String | Null`.
To your last point, Bentley software is standard for most DOTs for highway design. All their offerings are rife with quality issues to the point that I have never run their software without some spooky behavior requiring a reset or flushing the ProjectWise cache.
For software enabling a $150B industry, you would think it would at least run reliably. That there aren't objects that are aware that they are roads (just lines, arcs, and spirals) makes it laughably bad. The cost of this waste is tragic.
ICT departments in many large companies often force dev teams to use certain tools, because it's what's on their list of 'approved tools for devs'. Getting new tools on this list is often stonewalled for usually office-politics reasons.
Sometimes devs are locked into the tools they use. This situation is shit, but not uncommon.
The way I tie these together in phrasing it to teams is to ask yourself “Is this _necessarily_ the same or _coincidentally_ the same?”.
Code which is necessarily the same might be something like “how to calculate an invoice total”. If you need to calculate totals in multiple places, you can’t calculate different totals for the same invoice. Have a single source of truth for this.
Code which is coincidentally the same might be something like “well, to get an invoice total we add up all these prices multiplied by quantity… and this spreadsheet we’re importing has the product cost and a multiplier to reach a desired profit, so that’s the same dollar amount multiplied by a number again!”. Creating a single implementation for this will only cause pain.
Even if these things are the same _right now_, there’s nothing saying they must remain the same. And as they diverge, you are going to be either creating brittle franken-code that causes bugs in seemingly-unrelated parts of the application when you make (slow, tedious) changes, or you’re going to keep only the repeated logic as it evolves and you will make the code more and more generic until it provides no useful abstraction whatsoever.
Don’t repeat things that must be the same. Do repeat things that just happen to be the same _right now_.
I don’t understand how a law can expect someone to foresee and quantify potential future damage. I understand the impetus to hold companies responsible, but that is simply impossible to know.
Ha, I came here to comment that it can’t possibly be as good as this[1] homelab that I saw on Reddit recently…then I realized it’s the same guy. Seriously incredible.
it is even worse than that. the energy constrained model implies it is impossible to ever work off a pizza. you just simply burn fewer calories later to negate exercise, such as lowed BMR or less NEAT.
Because I banned it haha. There should not be more than one .env file. Our projects have a .env.example that has any overrides a dev might want to override but this list is kept intentionally very short.
I believe in convention over configuration. Most of our apps have hard-coded config, with a concise/short and finite number of things that can be overridden (like 3-4 parameters, tops). Secrets get injected.
We're still waiting for an answer to this most crucial question that you were asked above, as to what should happen once Palestine become truly "free":
What do you think should happen to the 9 million Israeli citizens on that land currently (or 7 million Jews if you prefer to split it by ethnicity)?
Absolutely. Unless you do some very vigorous exercise for many hours per week it’s not going to make much of a dent. I remember jogging for an hour (I’m out of shape) and it was very difficult - I felt like getting a pizza afterwards as a reward. That would have been something like -500 calories from the jog, +2000 from the whole pizza == +1500 net.
After many years of doing it wrong - now I go with low calorie and high protein meals until dinner. ~150 calories for breakfast for example and no snacking. Once I got used to being hungry, weight loss actually became realistic.
>…the vast international appeal of football. “It’s the only sport which is usually decided by one goal,” he theorised, “so the pressure on the moment is more intense in football than any other sport.”
• Early risers. Nearly 8 in 10 participants eat breakfast every day, but while many observational studies show an association between breakfast eating and either weight loss or simply lower BMI, clinical studies haven’t found a causal connection8,9—and a 2016 study found that NWCR participants were more likely to be “morning types” and report better sleep quality and duration than control participants currently enrolled in a weight loss intervention.10 “I think increasingly we’ll find there’s a lot of reciprocal patterns,” Thomas says. “Having an early start to the day is connected to eating breakfast, which could help, and getting to the end of your day and feeling good about your choices could motivate you to continue your healthful choices and help you get to bed earlier.”
This can be explained by dieters skipping dinner or having early dinner and going to be hungry and hence sugar depleted in the morning and craving food, hence early awakening and eating breakfast.
Maybe but not neccesarily by a long shot .. "Uncle" the english word used in any number of pidgin variation is a note of respect for an older man who isn't necc. a blood relative.
In various tongues there are more precise words for more complicated blood | marriage relations .. so "uncle" is mostly generic, but often will mean an elder from the same group, whether family or not (but likely).
This is something that definitely chafes. Even in a large-company enterprise environment, so many worthy & legitimate projects never end up shipping due to financial or office-politics reasons. Putting up paywalls between devs and their work that they to spend both time and money on is bloody stupid.
Chrome supported this for a long time and it really helped small developers outside of Google be able to build chrome without specialist machines.
But that feature was pulled by the chrome team with the stated justification being that since C++ guaranteed different things (iirc around variable scopes outside of a namespace) for one file vs multiple files, supporting the jumbo build option meant writing some language that was "not C++".
I remember mid-90s it was typical for a home computer to come with a prominent tutorial on mouse usage. There was definitely one for MacOS 7, while I don't recall if there was an official Microsoft tutorial for 90s Windows or just ones provided by OEMs.
Phi 3 has a unique architecture that needed some additions to llama.cpp's conversion script. Also Phi 3 is an absolute mess, there's no reliable way to latch on to when it's done writing a message and no one wants to admit it, people are patching around it instead.
ex. I could condition on "\n\n<|assistant|>||<|system|>||<|user>", but it'd still be wrong.
Pretty much everything Phi 3 feels like it needed to all come out within 48 hours a month too early. The ONNX genai library doesn't work on Mac, at all, the mobile SDKs don't support it...sigh
