Your story isnt important enough to deal with God awful UX.
341 karma · joined March 6, 2022
Your story isnt important enough to deal with God awful UX.
And no I'm not talking about govt ID or a card. I'm talking about a digital identity you log into and then oauth into other govt services like the tax office or healthcare systems.
https://www.amazon.com.au/Dont-Make-Think-Revisited-Usabilit...
For design itself I'm just not that way inclined and use existing frameworks instead.
Code shouldn't require imagination. Sometimes the simple and readable solution is just better.
You shouldn't be setting nullable variables to null so far away from where they're used that they're a problem.
E.g. if you're passing around an object with a possibly null value attached you should instead set it to a default empty state, empty string, zero, false etc.
Its only in rare circumstances that you should be needing to worry about null values.
I will however concede that non nullable types are super useful. I just don't think languages should remove null entirely. E.g. some rust projects have so many options types null would have been easier to code around. I know this is down to inexperience but at that point you've lost me - inexperience with null types is the only thing that makes null types a big problem.
This is a common strawman used to advise against null.
Null only means one thing. Null. It doesn't convey any further meaning. It is a "not set" or "not initialised" state.
It isn't a default, it isn't false, it isn't not enabled.
If you have a user interface tied to this variable. Null means not yet set.
This is entirely logical. The only people getting their knickers in a bunch are those that don't want to admit there is uncertainty and context required to determine what null means in your application.
My advice: don't apply further meaning to null other than null or not set.
Is anyone using it in production for anything substantial?
We have a couple of uses of it but I'm still not convinced it was worth the trade offs and felt mor like someone was having fun with a hammer.
Most of the webs applications were written in C/C++ pre PHP days.
Except in cases where they are, like this one.
Just cause you want convenience doesn't change the fact your fingerprints aren't good passwords.
Similar to misses, we don't really get much from shipping on that cadence either, other than progress and building confidence in upper management to base their timelines on us delivering what we expect.
My team asked for this. I dont know why they need it but apparently it helps them understand how much work theyre agreeing (and committing to shipping) in a sprint.
I think if you have a good grasp on what each issue will entail, you dont really need it but if youre less experienced maybe it helps?
There's a chance younger people simply won't understand or appreciate the interest in DEADBEEF.
Personally I found it kind of neat and wondered if I could design a colour palette out of rememberable code names.
https://en.m.wikipedia.org/wiki/Deadbeef
https://en.m.wikipedia.org/wiki/Hexspeak
Heh looks like this has been done before too: http://bada55.io/
But at this point, USBC is the better mousetrap, they're now just using their market dominance to force a worse mouse trap on everyone to keep milking lucrative patent fees outside of what an efficient market would allow.
So again, fuck em.
Side note, this is why I really hate IP law (or at least the over the top term lengths of it). If they didn't have a monopoly on lightening connectors this wouldn't be a problem and the market would resolve this "problem" on it's own.
You don't get to act like they're just behaving like a free market participant should when they're actively exploiting a different market regulation.
I wonder what the fix here is. Would it be choosing a patent term length that optimises for spurring innovation?
Too short and you make it not worth while. Too long and things stagnate like this. Why does society put up with such suboptimal market parameters?
I think this is a step over the line for regulators but so is apples behavior for the last decade or two when it comes to repairability.
Fuck em.
Here's an article showing comparisons to various moon ice.
https://www.businessinsider.com/earth-water-ice-volume-versu...
It also sort of explains how easy it would be for earth's water to have come from asteroid impacts.
https://d9-wret.s3.us-west-2.amazonaws.com/assets/palladium/...