Hacker Newsnew | past | comments | ask | show | jobs | submit | yoyar's commentslogin

Windows itself is malware.


Planke plastics


I struggled with weight for decades but this last year I've lost 60+ pounds, and I will lose more. All the weird tips in the world won't help IMO. I used an app that worked for me finally. It worked because I was able to get the education, and mindset / motivation I needed. Little tips and tricks won't work, you need a comprehensive solution that works for you. I'm not shilling for some company, this was the only thing that has worked consistently for me after decades of trying. Anyway, at the risk of sounding like an advert which this is not, it was noom. It takes a lot of work and persistence but having the reasons and knowledge to make it all come together and be consistent is what is key.


Anytime I learn a new language (I regularly write code in several) I start asking how is testing done, where are the libraries, where is this, and how do I do that? I already have all of that and more at my fingertips. Also, Groovy is vastly underrated. It’s the most economical and easiest to understand language I know meaning I can do more with less code and faster in general.


Groovy is definitely underrated when it's done properly (pretty much my favorite language when used as a "java substitute"). Unfortunately most people's exposure to it is in Jenkins or Gradle where it's a bit of a train wreck.


That’s too bad. That helps me understand why it isn’t favoured as much as I would think/like.


Every complaint I’ve ever seen about OOP (and other tools) amounts to “we misused and abused the tool/language/whatever so therefore the tool itself is bad “


But don't worry, someone will accuse of the No True Scotsman fallacy shortly.


Inflation of the money supply leads to prices that end up higher than they otherwise would have been.

This does not necessarily mean nominally higher prices.

This is a distinction that leads people to say things like: Obama did it and prices didn't go up. With the implication that it might be ok to inflate to infinity.


I think the causal nature of this relationship is way overestimated.


I’m curious, why do you think that?


Playing devil's advocate, do we have any reason to believe that people who are genetically more succeptible to depression aren't also more likely to have this sort of gut via genetics? That would result in this correlation.

Perhaps improving your gut biome wouldn't actually help with depression?


If people with depression have this sort of gut, that still doesn’t establish directional cause or mechanism.

The semi-autonomous nervous system in our guts, the microbes in our guts, and our central nervous system have complex chemical signaling interactions. Neurotransmitters linked to effects on mood are generated by the gut. Therefore, the brain can signal to the gut that it should release neurotransmitters, and the gut can release those neurotransmitters itself.

Because of this interaction, it’s possible the ‘culprit’ for depression is behavior by the brain, microbes on the gut, the gut itself, or the brain-gut interaction (Or any combination of the four.)

A good summary of our understanding of these mechanisms is at https://www.ncbi.nlm.nih.gov/pmc/articles/PMC5772764/


Agreed. No one knows.


Not building garbage software in the first place is an option


Building software is not done by making one decision -- to build garbage or not -- rather, it is done by making a series of decisions, usually by many people, with different contexts and tradeoffs.


If that is the situation then sure, do that. But sometimes market realities mean corners need to be cut and that is when taking on tech debt makes sense.

Better to have a business with some tech debt than no business.


I don’t think your comment contributes anything useful to the conversation. Nobody sets out to write garbage code. Nobody decides to add more legacy code. However it still happens despite software developers best intention. So do you have any practical solutions to solve the problem?


The point here for me is team dynamics, maturity, and skill level.

If you have a team that can't competently write and maintain a monolith that is modular and built/tested via automation, then that team has no business trying to build and maintain microservices.


No single person understands everything about how a pencil is made.


In case somebody doesn't know the reference:

https://mises.org/library/i-pencil


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: