narvidas

Yep, that was exactly my point with the ask to elaborate.

MCPs and CLIs feel like two wholly different things. Contrasting them feels even more confusing than comparing Skills vs MCPs, which would also be wrong in my personal view. Different runtime requirements, different access patterns, different distribution, different discoverability.

I agree with @martinanld that MCPs, especially with the advent of EMA, are a completely different beast thanks to a structured way for auth and access control.

Could you elaborate on this thought? MCP vs CLI feels very much like a Apples/Oranges comparison, without additional context.

As someone who has written both React and Svelte for many years I must interject. React is itself just a library. No, you don’t need any specific “wrappers” for it. Let’s not mislead the readers here.

That's so interesting, isn't it?

What this person could've take away here was that: - Contrary to what the article states, parenthood in males can sometimes even boost testosterone through external factors. - Or that resitance training and diet is a great way to deal with daily stress.

What instead they took away was that improving oneself for family somehow makes you unfit to be a parent.

A rather dark interpretation. Sincerely hope they are OK and well.

Just a personal anecdotal datapoint, but relevant and possibly interesting nonetheless.

I work full time and even by modern standards I'm what most would call a heavily-involved father. I have an 18month old.

After my daughter was born, due to the amount of stress and lack of sleep I very soon realised I had to return to doing regular resistance training, clean diet and cut other things like drinking alcohol. In order to keep my energy levels sufficiently high and mental health in check.

I now feel much better than I did in years. Albeit still heavily sleep deprived most days. Recent bloodwork shows that my T levels nearly doubled (compared to before becoming a dad) from average to slightly off-the-charts high.

Take it as you will, but for me fatherhood forced me to reevaluate how I spend my time very carefully, forcing me to take care of myself more so I can take care of my family sufficiently too.

In full-time employment this is sad but true. There is a way out of this toxic loop however.

As a consultant/contractor I always evangelise simplification and modelling problems from first principles. I jump between companies every 6-12 months, cleaning up after years of complexity-driven development, or outright designing robust systems that anybody (not just the author) can maintain and extend.

This level of honesty helps you build a reputation. I am never short for work. I also bill more than I could ever as a full-time engineer based in Europe.

As a rule of thumb, "magic" is a code smell. Libraries should be preferred over frameworks whenever possible.

A toolbelt of small utility-like composables are often easier to maintain and reason about. This results in added explicitness (i.e. less magic, fewer surprises).

Personal experience shows that the immediate efficiency gains of a framework often get diminished in the face of all the hacks people introduce later, just to work around the remaining 10% of cases that the framework did not anticipate or traded-off against.

Please note this is a comment based on personal experience and professional preference.

BOCTAOE.