aray07

8 ms·

91.
by aray07 1y ago
Claude Code has changed the way I write code. Programming for me has become a lot more fun because of Claude Code. I get to spend more time planning and researching. I have been working on https://codient.dev to be able to run C
92.
Show HN: ImportCSV – Open-Source CSV Importer(github.com)
2 points by aray07 1y ago|0 comments
93.
What Makes CSV Parsing Surprisingly Hard?(importcsv.com)
3 points by aray07 1y ago|2 comments
94.
Show HN: ImportCSV - Open-Source CSV Importer(github.com)
1 points by aray07 1y ago|1 comments
95.
by aray07 1y ago
Hey HN, I'm building ImportCSV, a self-hosted CSV importer that makes CSV onboarding easier for SaaS apps. Here is a quick demo: https://screen.studio/share/8STvmqkq CSVs are like the cockroach of data transfer—th
96.
Respect the CSV(github.com)
3 points by aray07 1y ago|0 comments
97.
Docs-First Design: A Better Way to Build Developer Tools(octopipe.com)
3 points by aray07 2y ago|0 comments
98.
I used to write code first, now I write docs first–here's what changed(octopipe.com)
5 points by aray07 2y ago|0 comments
99.
by aray07 2y ago
Working on building a copilot for oncall engineers. Goal is to automate or reduce the grunt work oncall engineers have to do. Code is here: https://github.com/opslane/opslane
100.
by aray07 2y ago
I do think AI will automate a lot of the grunt work involved with incidents and make the life of on-call engineers better. We are currently working on this at: https://github.com/opslane/opslane We are starting by tack
101.
by aray07 2y ago
I did a bug squash interview when I was interviewing for new grad positions and it was one of my favorite interviews (both as an interviewee and an interviewer) - People were allowed to use their favorite IDEs - so you could see how profici
102.
by aray07 2y ago
Thanks for the feedback! I completely relate to PD scheduling issues and something that we want to take a look at as well.
103.
by aray07 2y ago
Yeah, I was surprised at how common this behavior has been across companies. I don't have a good solution for this problem - I am hoping additional visibility and accountability into these alerts can be useful. One of the things we hav
104.
by aray07 2y ago
Yeah, that was one of the goals we had. We try to classify when an alert comes up and let the engineer give us feedback. We use that to generate a report so that teams have visibility into which alerts are causing the most amount of noise.
105.
by aray07 2y ago
I agree - fixing the original problem is the main motivation. We wanted to provide that awareness because a lot of teams arent fully aware how bad the problem might be (on-calls change weekly, there might be a bunch of other issues)
106.
by aray07 2y ago
yeah, thats the goal of adding the context and the report - to hopefully bring awareness to the team that this alert should be removed. My rationale for flagging the alert was to help prioritization for the on-call (lets say there are multi
107.
by aray07 2y ago
Thanks for the feedback. Yeah, ideally, teams would go back and fix their misconfigured alerts. Unfortunately, on-call ends and people forget. The aim was to both provide context when an alert comes up as well as provide a report at the end
108.
by aray07 2y ago
Thanks for the feedback! I saw the incidental launch on HN and have been following your journey!
109.
by aray07 2y ago
derp, thanks for catching. It has been fixed!
110.
by aray07 2y ago
yeah the best managers i worked with used to be on the same on-call rotation such that they would also get paged every time. That helped build empathy and visibility into the situation.
111.
by aray07 2y ago
Yeah, thats fair feedback. The main aim was to reduce the alert fatigue for on-call engineers and provide a way to get insight into the alerts at the end of the on-call shift. This way there is data to make a case that certain alerts are no
112.
by aray07 2y ago
Yeah, unfortunately, I don't think these messaging tools are async. During oncall, I used to pretty much live on Slack. Incidents were on slack, customer tickets on slack, debugging on slack...
113.
by aray07 2y ago
I completely agree that technical tools cannot fix culture problems. However, one of the things that I noticed in my previous companies was that my management chain wasn't even aware that the problem was this bad. We also wanted to add
114.
by aray07 2y ago
Thanks for the feedback. We want to get something out quickly and we had experience working with Slack so it made sense for us to start there. However, the design is pretty flexible and we don't want to tie ourselves to a single platfo
115.
by aray07 2y ago
Yeah, I agree that slack is not the best medium for alerts. I think we it has somewhat become the default in teams is that it makes it easy to collaborate while debugging. I don't know a good way to substitute that and share informatio
116.
Show HN: I built an open-source tool to make on-call suck less(github.com)
319 points by aray07 2y ago|169 comments
117.
How to build a tool like Zapier using serverless(learnaws.org)
4 points by aray07 6y ago|0 comments
118.
How to build your own Zapier alternative for free(learnaws.org)
2 points by aray07 6y ago|0 comments
119.
How to create automated AWS billing reports(learnaws.org)
7 points by aray07 6y ago|0 comments
120.
AWS Lightsail Deep Dive: What is it and when to use(learnaws.org)
3 points by aray07 6y ago|0 comments

More ›