Lhiw
I fit the profile of person one in the article.
The reason I'm wondering / even looking at autism is because the meds for my ADHD just make everything worse even at really small doses and I don't really know what to do.
Computers are amazingly resilient if you don't need them for much more than office work.
I know it's popular, but nowhere near to the level it should be.
This is mostly to facilitate daily updates in lieu of stand ups.
Another thing I do along side my todo.txt is log important team changes, team switches, people encounters, side projects and any major project milestones that might be useful to point out in my 6 month reviews.
It's really amazing to search back and find links to things you did months ago when search won't pick it up.
But I don't aim for minimal images. Using alpine and installing what ever you like without worrying about all the bullshit to make caches stay empty still results in images only a few megs, don't need to do much better than that.
Though I tend to agree, if you're talking about a compiled language. Static binary and there is little need for anything other than `from scratch`.
They enable refactoring code in ways not possible without them.
If nobody else is disliking it maybe my biases are effecting my perception.
Not everything is confirmation bias. Some people use social feedback to regulate themselves into not being total weirdos.
It requires dwr to function, as soon as the dwr fails (pretty fast depending on your usage levels) its ability to breath ceases to function, at that point you're wearing a heavy, expensive, water proof coat that doesn't breath so it rains on the inside instead.
It's saving grace is that it's durable in heavy brush.
For a better alternative take a look at Columbia outdry, it doesn't require dwr so its breathability lasts for the life of the garment instead of requiring retreatments of dwr.
Frogg toggs are another option, way less durable but as far as breathable rain proof it doesn't get better.
Both outdry and frogg toggs are also way lighter than goretext. Though look around for the outdry they have heavy duty and light versions.
https://www.hakko.com/english/products/hakko_fx950.html
There are similar things on the market but nothing that ties it altogether quite so succinctly.
That's a lot of trade offs to avoid maintaining the subset of features you need from said software in house, being able to leverage internal knowledge, being able to streamline all your environments and tooling to suit your needs instead of catering to the needs of said software.
This isn't an argument one way or another, it's just pointing out that there are trade offs you need to make consciously or otherwise.
In your position I would be extremely concerned about pushing off the shelf software onto Devs that either lack the clout to be comfortable pushing back or lack the communication skills to clearly articulate all the trade offs really taking place.
It's very easy for a boss figure to push through requirements with off the cuff pointed questions. The reports often need to push back with orders of magnitude more research and thoughtfulness than went into the question or suggestion.
Is there potential treatments that could result from this?
I wonder if type one also exhibits this trait?
My wife and I are thinking about it.
I don't really have a problem with vegetarians but I do struggle to understand the lines they seemingly draw at random.
Minimising harm should be a given for all but that doesn't rule out all meat eating that veganism somehow does.
Github is annoying as crap. Can't even comment on a line in the file that needs changing but was missed in the PR, can only comment on a tual changes.
Phab is god awful, it's like someone built that whole system with a purist mindset, everything is perfectly designed with perfect referential IDs. But every screen is a view into the db table, no screens join information and make it usable. This is worse when you have n:m relationships because they expose those tables via screens too, it's just plain awful.
The best argument I've seen so far is that it just makes all videos look "liked", and none "disliked" because likes are still shown.
Dumbing down the platform in pursuit of simpler interfaces (however you want to justify it) isn't always what actual users want and or need.
> Previous estimates, when accounting for glycogen depletion, suggest that a human could run at about a 10 minute per mile pace, which allows existing fat stores to be converted to glycogen, forever. The only limit to our eventual mileage, therefore, is our need for sleep. https://nikomccarty.medium.com/how-far-can-humans-run-d5c97f...
This is like eBay promoting sales of items on their marketplace using advertising.
Which they've done for years.
I still don't know how to do arrays in yaml.
Is it new line, tab to same indent or same indent + one space, do I need a dash? Does a dash make it an array or an object?
It's just simply not that big of a deal to add a few quotes and braces to make everything make sense.
The only real issue with Json is the lack of comments and strictness about extra commas.
I also have far less complications as a result. My desktop hasn't changed in close to 10 years.
Been a while but I had real issues using udev rules as they created timing problems or something like that.
Except this is not comparable to most of the 70s at all.
Household leverage and disposable income change how serviceable debt is at different rates.
The numbers I saw puts a 2021 mortgage rate of 3% at an equivalent benchmark rate "in your pocketbook feels" as a 6% rate in pre gfc 2007.
Are you sure 10% doesn't warrant the same emergency as the high-teens of the 70s?
Prices go down 40-50%?
Normalizing for household leverage and disposable income, a 3% mortgage in 2021 is close to a 6% mortgage in 2007. Assuming it scales linearly (not sure it does), what you're talking about would mean an equivalent effect of around a 15% rate in 2007 against 2007 prices.
I tried to track down where I saw these slides but couldn't find them, I think it was a morgan stanley presentation looking at comparison rates and leverage normalization to predict how bad different rises in rates would be in terms of how the rate "feels" to the average mortgage holder.