fazlerocks

5 ms·

1.
Structural steel estimating: the steps were never the hard part(bidferra.com)
2 points by fazlerocks 4mo ago|0 comments
2.
Which AI tools have you used every day for the past year?
1 points by fazlerocks 10mo ago|0 comments
3.
Playwright new Test Agents explained(bug0.com)
1 points by fazlerocks 1y ago|0 comments
4.
Ask HN: What's your 2025 "quality stack"?
1 points by fazlerocks 1y ago|0 comments
5.
Show HN: Mail42 – Disposable emails with AI-based text extraction
1 points by fazlerocks 1y ago|0 comments
6.
by fazlerocks 1y ago
honestly? teaching or coaching. been thinking about this a lot lately and realized the skills that made me good at building products, breaking down complex problems, explaining things clearly, helping people think through decisions… those t
7.
by fazlerocks 1y ago
we've shifted to focusing way more on problem-solving ability during interviews rather than just coding skills still do technical screens but now we give people access to AI tools during the process - because that's how they'
8.
by fazlerocks 1y ago
we've tried a bunch of different approaches and honestly the best feedback comes from getting people in a room (or zoom) together widgets are fine for quick "this button doesn't work" stuff but for real UI feedback you n
9.
by fazlerocks 1y ago
the best "payment" is often just updating them on how their help changed your trajectory. a simple message years later saying "that advice you gave me led to X" means everything also - helping the next person who reminds
10.
by fazlerocks 1y ago
This is actually a really cool direction, using LLMs to interact directly with Android UIs could solve the brittleness problem that's been killing traditional automation. Like just telling it "navigate to settings and enable dark
11.
by fazlerocks 1y ago
We're building tools that could genuinely make people's lives better, but instead most companies are laser-focused on "how many jobs can we eliminate?" The whole conversation around AI safety isn't even about keepin
12.
by fazlerocks 1y ago
Been messing around with the different memory files and honestly it's pretty useful once you get the hang of it. I mostly use: Project ./claude.md - team stuff like our weird API naming conventions, how we structure components, de
13.
Ask HN: What tools are you using for AI evals? Everything feels half-baked
6 points by fazlerocks 1y ago|3 comments
14.
by fazlerocks 1y ago
Learn prompt engineering and how to effectively use AI coding assistants… that's immediately useful and will save you hours daily. Vector databases (Pinecone, Weaviate) and building RAG systems. Tons of companies need this now and most
15.
by fazlerocks 1y ago
Honestly X is still pretty good for this if you follow the right people. The AI/ML research community is super active there - Andrej Karpathy, François Chollet, Yann LeCun, etc. Plus a lot of the good startups announce stuff there firs
16.
by fazlerocks 1y ago
Right. We're optimizing for the wrong metrics. Hours spent arguing if something is a 3 or 5 story points could've been spent just building it. The obsession with predictability in an unpredictable process is the real problem, espe
17.
by fazlerocks 1y ago
Running Llama 3.1 70B on 2x4090s with vLLM. Memory is a pain but works decent for most stuff. Tbh for coding I just use the smaller ones like CodeQwen 7B. way faster and good enough for autocomplete. Only fire up the big model when I actual
18.
Ask HN: What's the most overengineered tool everyone uses but won't admit sucks?
28 points by fazlerocks 1y ago|42 comments
19.
by fazlerocks 1y ago
4 cents per request adds up real quick when it's doing stuff you didn't even ask for. Have you tried disabling the GitHub integration entirely? Wondering if that's what's triggering the phantom requests.
20.
by fazlerocks 1y ago
This is pretty cool - the Jira/Linear integration could save a ton of manual work. How do you handle test data setup and teardown? That's usually where these workflows get messy. For alternatives in this space, there's qawolf
21.
by fazlerocks 1y ago
The indexing costs would be nuts - Anna's Archive is like 200TB+ and growing fast. Even with decent search infra you're looking at serious compute/storage costs. Plus there's the obvious legal stuff that would make this
22.
by fazlerocks 1y ago
Have you considered implementing velocity limits and requiring phone verification for new accounts? We faced similar issues and found that slowing down rapid fire purchases + requiring SMS verification eliminated 90% of the fraudulent attem
23.
by fazlerocks 2y ago
Thanks for the detailed response! I actually tried fly.io briefly with Next.js apps and the deployment experience was smooth. Really interesting to hear you're using it for AI workloads too. For fly.io with AI workloads: Are you using
24.
Ask HN: What's your serverless stack for AI/LLM apps in production?
3 points by fazlerocks 2y ago|3 comments
25.
Show HN: Awesome Docs Gallery – crowdsourced list of the best dev docs(awesome-docs.gallery)
1 points by fazlerocks 2y ago|0 comments
26.
by fazlerocks 2y ago
Well, I was right, I guess.
27.
Show HN: Docs by Hashnode, we built another docs product in 2024, here's why
3 points by fazlerocks 2y ago|1 comments
28.
Show HN: We built a developer-friendly Headless CMS for blogs(hashnode.com)
5 points by fazlerocks 3y ago|2 comments
29.
Why Postgres is winning over MySQL?(youtube.com)
3 points by fazlerocks 3y ago|0 comments
30.
The ideal headless CMS for blogs(hashnode.com)
2 points by fazlerocks 3y ago|0 comments

More ›