On the other hand, I’ve also seen single developers create a tool or dashboard off-the-books that had widespread adoption. Things that would never have breached the top 100 features list since they are entirely internal. The irony is then they are expected to maintain it indefinitely without official effort allocation.
I don’t see middle managers taking the initial brunt unless they truly are just pushing papers around. At companies of sufficient size, they do play a role of separation between C suite and the grunts. To me, certain low-performing grunts will be the first out. Then a team reorg to rebalance. Then some middle managers will be out as fewer of them can handle multiple teams.
At least at my company, we have never really cared how it gets done, even before AI. It just has to work (ideally bug-free and maintainable) by the deadline. If you can keep up with shorter deadlines, more power to you. It’s basically a modern John Henry vs the steam drill.
That is why I do not use the multi agent team technique. My code generation has atrophied, but my code review skills have only gotten stronger both for human and AI code. If I handed over both, it hurts my employability and will definitely lead to that hangover.
Sure, age restrictions played a part. But the larger reasons are the increased awareness of direct health effects, banning it in public spaces, and taxing the hell out of tobacco. I’d bet if they restricted app usage in specific locations, that alone would break the habit for some people. And imagine if you charged them each time they logged on.
The mortgage payments always confused me and that link has a good explanation of how it works. Have you used that code base in your own system or just the principles? I don’t know Haskell so not sure how much I can/need to modify.
Do you want to share what's confusing about mortgage payments?
You have a balance that accrues a monthly interest. Separately, you're told that you're owed a monthly payment. If monthly payment > interest, then the difference is subtracted from the balance. No need for haskell.
Loans can be confusing in double entry accounting for the uninitiated.
On the accounting side you have liabilities:mortgage which would only include the principal. Then for an individual bill you have to debit liabilities:mortgage the principal portion and debit expenses:interest the interest portion.
I’m not sure how mortgage bills usually come but for my auto loan the principal vs interest were not noted on the bill, so i had to calculate via apr myself for each payment for which the interest accrued daily. If i imported those payments from my bank statement or the bill i would not be able to enter the transaction correctly without doing the math.
For calculating interest automatically upon entry based on the rate and payment amount and date I used python iirc as i used beancount, but that was a while ago.
Yes, I'm using parts of this codebase. But Haskell is only being used as a build tool, so you can replace it with anything that you're comfortable with, like make, bazel, ...
Depends on how many different financial systems you need to import from. It took me a weekend to set up the importers alone between checking, savings, investments, mortgage, pay slips, and all the credit cards. Some don’t have csv output so had to do pdf to text conversion. There are examples in beancount but each bank was different for me.
As a kid, I had a bulls-eye rash which is the tell-tale sign of Lyme disease. My dad snapped a Polaroid since we were on a trip and couldn’t get to my pediatrician for a week. The rash cleared up before I went in. My doctor didn’t want to diagnose it as anything or write an antibiotics prescription…until my dad pulled out the photo. She then immediately wrote the antibiotics for it. The danger of under diagnosis for Lyme disease versus antibiotic resistance tilts so far towards writing the prescription that I will never understand her reasoning. Point is we knew to go in and to advocate for my own health. Doctors are fallible humans too.
These days I hike a lot, I've had bullseye rashes before and the treatment is so much less worrisome than the rare possibility of developing lyme.
Last time I was in for getting hundreds of tick bites in one hike (that was fun), I was also told to avoid eating red meat until labs came back. That Alpha-gal is getting more common in my area, and the first immune response is anaphylactic in 40% of the cases, best not to risk it.
>These days I hike a lot, I've had bullseye rashes before and the treatment is so much less worrisome than the rare possibility of developing lyme.
Yeah, if you develop a rash from a tick bite that even remotely looks like it could be lyme, just go to a pet store to buy amoxicillin (you can get exactly the same stuff they give to humans) if you can't quickly find a doctor who'll take it seriously enough to immediately write you a prescription (unless, of course, they have a very well reasoned explanation for not doing so).
The potential consequences of not getting fast treatment are indeed so so much worse than the practically non-existent consequences of taking amoxicillin when you don't need it, unless you're a crazy hypochondriac who constantly thinks they might have lyme.
But hey, also don't blindly trust medical advice from HN commenters telling you to go buy pet store antibiotics :)
Amoxicillin isn't the best for Lyme. It does work but it takes more and longer for it to work than doxycycline. And what you're going to pay at the pet store is going to be way more than urgent care and a human script.
Advanced diffusion certainly benefited from the acquisition speed ups. That is its biggest challenge in my opinion preventing it from wider clinical adoption. It takes too long to get enough images for the models. Hyperpolarized MR will run into issue of lack of expertise in clinical imaging centers. There is already a shortage of good techs and MR companies are working to further automate the workflows. Unless there is a major benefit of the advanced techniques, people will stick to the bread and butter FSE and DWI.
reply