HNHacker News
TopNewBestAskShowJobs

rwilinski

165 karma · joined July 30, 2016

submissionscomments
rwilinski··on The Principles for Reliable, Safe and Fast AI Agents
Building AI agents is hard. Most attempts end up with brittle systems that break in production, cost too much to run, or worse - make costly mistakes that could have been prevented.

Fortunately, there are several core principles that I’ve learned while building agents that actually work. Hope you find it useful!

rwilinski··on Ask HN: Side project of more than $2k monthly revenue? what's your project?
I made Dynobase [1], an alternative GUI for DynamoDB. Passed 2k/mo few years ago. Runs 100% automatically now, I spend ~2h/week mostly responding to customer inquiries. I could leave my full time job but I just like it (and money) too much.

[1] https://dynobase.dev

rwilinski··on AWS IAM Manager – Users, Groups, Policies as a Code with one simple Lambda
That's pretty good idea, I haven't thought about it.

I think that my format is easier to understand. You don't have to use `Ref`s and weird `Fn::Join`s which may be not obvious for developers which are not experienced with CF.

rwilinski··on AWS IAM Manager – Users, Groups, Policies as a Code with one simple Lambda
Hi Everyone,

At netguru.co we have to provide access for over 100 developers to different AWS accounts. Doing it from console or CLI was kind of a pain so I came up with this solution.

Basically, it "mirrors" structure from selected Github repository into AWS IAM Users, Groups and Policies. Everyone can request access to AWS account by creating pull request which must be Approved by a devops/cloud architect. Once merged, message will be send to SNS and then to Lambda which will take care of keeping everything synchronized.

Right now it does not support Cross-Account Access & Roles but I'm planning to implement it.

Let me know what do you think.

rwilinski··on Show HN: Realtime, self-hosted monitoring for Node.js inspired by GitHub Status
Good idea, didn't know about that.
rwilinski··on Show HN: Realtime, self-hosted monitoring for Node.js inspired by GitHub Status
It all depends on how much data you would like to keep and monitor. If you're going to keep data let's say for last minute, last hour and last 24 hours (100 data points each) you'll be fine. It will extend base memory footprint by about 4MB approx basing on my experiments. When it comes to CPU, these operations are not so expensive and consume up to 0.1% of my Macbook Pro power (on default settings which are 3 series of 60 datapoints)
rwilinski··on Show HN: Realtime, self-hosted monitoring for Node.js inspired by GitHub Status
I don't do that in my professional work, I do that only in my personal projects. It's just my project so I guess I set the rules here ;)
rwilinski··on Show HN: Realtime, self-hosted monitoring for Node.js inspired by GitHub Status
I don't have much experience in MongoDB Administration but if you're enterprise I think you should checkout Cloud Manager: https://www.mongodb.com/cloud/cloud-manager/

In Wikia we based on ELK + Grafana for everything that needed monitoring so pushing mongostat data to InfluxDB/Logstash should be OK.

rwilinski··on Show HN: Realtime, self-hosted monitoring for Node.js inspired by GitHub Status
I pick them randomly, sometimes I try to find something relevant to change but not in this project.