hosh

Software would benefit more from some training in philosophy than in scientific thinking.

The article was talking about solo devs, small businesses, and startups. A few physical servers that can handle millions of request per day.

I think that is pretty normal while dreaming, daydreaming, or awake if you don't have aphantasia. Someone skilled in neural-linguistic programming can guide someone into developing greater and greater details.

Psychedelics and certain meditative practices can enhance this effect. There are also specific practices that allow imagined object to take a life of its own.

That's in the private imaginative mindspace. There are other mindspaces. There was one particular dream where I can tell, it was procedurally generated on-demand. When I deliberately took an unusual turn, the entire realm stuttered as whole new areas got procedurally generated. There were other spaces where it was not like that.

25 and 26 has been my experience with this as well (not at Amazon; at much smaller organizations) Those paradoxes happen there.

Just my opinion: one of the key mindset shift that happens before someone steps into staff and principal engineering is understanding that the technical choices you make are tradeoffs. You give up conceits (or one should) that a technical opinion is separated from context, while also getting to deeper technical principles that appear across architectural levels or disciplines (such as queues). You also see how technical systems are inseparable from the people using it, and being a part of it.

When you start seeing that, you start seeing that everywhere. You start to act in a way that is informed from that understanding. You need to be on the critical path in order to do what matters, but you also need to connect those dots that are overlooked.

But that is also one flavor of principal engineering. I tended to do the horizontal influence than deep technical and domain expertise. At early stage startups, people have to wear multiple hats, often exceeding the scope of what they were initially hired for.

I appreciate this long comment.

I am in the middle of convincing the company I just joined to consider building on GCP instead of AWS (at the very least, not to default to AWS).

Table-oriented layouts was a thing back then too.

Were you talking about this incidence? https://arstechnica.com/gadgets/2024/05/google-cloud-acciden...

I am currently evaluating between GCP and AWS right now.

I’ll be on the lookout for a Show HN!

Wow, neat idea!

Is this going to be proprietary or OSS?

I think the line of thinking you want to explore has more to do with how we perceive beauty and elegance. That has been the subject of philosophers all over in our recorded history, and I doubt a single article will be able to cover this.

Christopher Alexander studied this deeply for building architecture, and his ideas had influenced many thinkers of software architecture; Alexander asserts that there is a thing to objective beauty. Alexander’s keynote to the OOPSLA conference is worth reading, as is Roy Fielding’s dissertation. The “values” mentioned in this article is organized as “architectural properties” in Fielding’s dissertation.

Maturity is not exactly correlated to time in experience, just as emotional and social maturity doesn’t exactly correlate with biological age.

I was 12 years into my career before the ideas in this article started filtering into my mind.

The “values” in this article maps to Roy Fielding’s PhD dissertation on software architecture. Fielding’s dissertation is better known for REST, but his dissertation is much broader and more versatile. He actually organized a way to think about and reason about any software architecture and then presented REST as an example.

The “values” mentioned in this article maps to the architectural properties (versatility, scalability, observability, readability, maintainability, etc.), but I have found that understanding architectural constraints is even more important because that tells you where anti-patterns are, and how an architecture can evolve (or not evolve).

https://ics.uci.edu/~fielding/pubs/dissertation/top.htm

Yes, I know bundler does that. But I thought we were talking about urn instead of uri. Seems I was mistaken.

Were those tech open source?

A decade before Rails puts it in 1995. Do you have some resources on this? I like looking into the history of tech.

Chances are, this will make rv into a bigger success. Assuming the rv developers delivers on their promises. (I tried using their first version on launch only to find that the features I wanted have not been written yet).

Where are you getting that Shopify fears rv?

That sounds like a neat idea. Do you have a proposal for that?

Would it be compatible with specifying urls (such as git repos)?

Do you have a source for that? I always wondered why Merb disappeared, even after Katz refactored Rails to use ideas from Merb.

The proliferation of frameworks came about from the ideas and design of Ruby on Rails. MVC and ORM had been around before web apps, but it was not consistently used in a web framework until Rails. Convention-over-configuration, “nested doll pattern”, and Rack protocol were all ideas widely ported and copied into other language platforms and frameworks.

Also, ActiveRecord gained significant capabilities with named scopes, something that isn’t as widely copied.

Finally, Ruby itself lends itself well to writing DSLs, something that Javascript and TypeScript sucks at, but sometimes I still see people try and fail.

To be fair, it is my personal opinion that there has not been anything substantially innovative since Rails 5. The features I have seen since is better done with Elixir/Phoenix, mainly because the BEAM runtime makes better concurrency primitives available.

Does the law as written distinguish between B2C and B2B?

Would this law have helped that non-profit that had their annual Slack subscription increased from $5k/year to $200k/year?

https://news.ycombinator.com/item?id=45283887

Does that mean, things like AWS Reserved Instances or Savings Plans do not comply with this EU law?

And they are already migrating things to Mattermost. So again, how does talking about the stages of grief help?

Or an infra engineer willing to volunteer and teach the teens and adult members how to set up and maintain the self-hosted chat.

The non-profit is still in crises mode and can use help. The grief and reflection can come when the crises has passed. Whether it is grief or not, how is describing these stages of grief helpful for the situation as it is right now?

How is this helpful for the non-profit?

And Kübler-Ross did not describe a linear progression of grief. It was meant to be enough of a framework to start conversations, to put experiences in perspective, to help reflect. And plenty of times, life still has to go on even with devastation -- no time to grieve and reflect until crises has passed.

The wording of the co-founder's comment and the post did not strike me as grief. They are calling out enshittification without trying to burn bridges and requesting help.

There are local chapters of the Society for Creative Anachronism that uses Facebook heavily. The thing is that the use of FB grew out from the in-person community that had formed, and people would rather interact in-person than only through social media. The community already has its own customs and ceremonies for recognition; people there upvote and collect following in an attempt to get the FB algorithm to spread the word for each other (on events and happenings).

When there is an already-existing community like that, I think a dedicated social media platform for that particular community can be beneficial. That platform then does not have to be the social media for everyone.

However, funding (for hosting and maintenance) is still an issue.

Do you count LiveView (Elixir) in that assessment?

There is a project called Iocaine that does something similar while trying to minimize resource use.

Not immediately practical -- I've been looking into using Pharo (smalltalk) to build a web authoring / static site generator that non-devs can use, and something that devs can quickly customize or extend.

There is a form of delegation that develops the people involved, so that people can continue to contribute and grow. Each individual can contribute what is unique to them, and grow more capable as they do so. Both people, and the community of those people remain alive, lively, and continue to grow. Some people call this paradigm “regenerative”; only living systems regenerate.

There is another form of delegation where the work needed to be done is imposed onto another, in order to exploit and extract value. We are trying to do this with LLMs now, but we also did this during the Industrial Revolution, and before that, humanity enslaved each other to get the labor to extract value out of the land. This value extraction leads to degeneration, something that happens when living systems dies.

While the Industrial Revolution afforded humanity a middle-class, and appeared to distribute the wealth that came about — resulting in better standards of living — it came along with numerous ills that as a society, we still have not really figured out.

I think that, collectively, we figure that the LLMs can do the things no one wants to do, and so _everyone_ can enjoy a better standard of living. I think doing it this way, though, leads to a life without purpose or meaning. I am not at all convinced that LLMs are going to give us back that time … not unless we figure out how to develop AIs that help grow humans instead of replacing them.

The following article is an example of what I mean by designing an AI that helps develop people instead of replacing them: https://hazelweakly.me/blog/stop-building-ai-tools-backwards...