Clearly, that's not the case anymore. Nowadays you just swap out "email" for "LLM"

Comments URL: https://news.ycombinator.com/item?id=47331888

Points: 3

# Comments: 4

2. give up root because you don't need it any further.

3. Only accept non-root logins

4. when a user creates a session, if they need root within the session they can obtain it via sudo or su.

Its a walking simulator for the most part. (For those that know what that means) Think of it as a journey you take part it. But there are a few choices you can make to change a bit of who dies, and a affect a slight change in the ending.

I enjoyed it thorougly. And felt it was a great representation of the retrofuturistic world the book presented, and stayed mostly in the style of that era.

  Location: Santa Monica, California
  Remote: Yes (and local hybrid)
  Willing to relocate: No
  Technologies: Golang, Python, Javascript, Ruby, Java, AWS, Kubernetes, Postgres, Mysql, CI/CD, Serverless, Microservices, Scalability, Distributed Architectures
  Résumé/CV: http://resume.jason-stillwell.com/
  Email: dragonfax@gmail.com

https://en.wikipedia.org/wiki/Abuse_(video_game)

Good practice for using external APIs is to NOT use any default http client settings and always provide your own timeouts to what you consider reasonable for connections and responses, as well as using a context system with deadlines so you can time out any requests that are taking more than a reasonable time to complete. Making your described surprise long expensive requests into nothing more than short errors (which hopefully you'll pick up on after a while, as long as you've got your alerting system setup right).

The article mentions hot partitions becomming a problem with max partition size, but they're also a problem with scalability. Say, if your writing a very high throughput of logs into the table (contrived example), then your bottlenecked by the rate at which you can write to one partition.

Adding the bucket id (say, the current day or hour), is a common solution, and solves the max partition size issue, but not the scalability issue of hot partitions.

We are hitting the limits of its capability. Which is when applications get complicated or end up with lots of code. The javascript you write in your tool is running inside many layers of retool javascription and encapsulation.

But at this point if we decide to move such an app out of Retool, then the business logic is already written.