Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
jampa
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
8 ms
·
61.
▲
Things I've learned in my 7 years implementing AI
(jampa.dev)
156 points
by
jampa
1y ago
|
55 comments
62.
▲
by
jampa
1y ago
The headline and article try to bias and frame the story to make people question: "Is OpenAI snitching on me?" In reality, Uber records and conflicting statements incriminated him. He seems to be the one who provided the ChatGPT r
63.
▲
LLMs and the Lessons We Still Haven't Learned
(jampa.dev)
2 points
by
jampa
1y ago
|
0 comments
64.
▲
by
jampa
1y ago
I'm sure the OP means well, but I think this approach is misguided. It comes across as self-centered rather than supportive. You might get a polite "thanks" in response, but I doubt it will be genuinely appreciated. If you ca
65.
▲
by
jampa
1y ago
The automation is powered through Browserbase, which has a captcha solver. (Whether it is automated or human, I don't know.)
66.
▲
by
jampa
1y ago
It's still around, but the hype has faded. Users discovered numerous issues with the project and began abandoning it. I remember one month when everyone was all, "LangChain is the future," and another month when the sentiment
67.
▲
by
jampa
1y ago
As a JS developer for over 10 years who has seen multiple hype waves, here is my advice: You don't need to ride the first wave. You can wait until technology matures and see if it has staying power. For example, React and TypeScript we
68.
▲
by
jampa
1y ago
The enterprise customers will care, and they probably are the ones that bring significant revenue.
69.
▲
by
jampa
1y ago
I wonder if they do a routine map of the delivery area (with a Lidar plane) so they have a high-resolution scan of the city for better pathing. But they didn't expect something like a crane that could be assembled so high and fast to b
70.
▲
by
jampa
1y ago
I was in your shoes when I was 17. I built a social app to replace Orkut's communities (which Google bought and killed) and a chat app before Discord took off. Some advice: - If you want to improve as a developer, keep building feature
71.
▲
by
jampa
1y ago
I should have added that to the post, but we verify by running a full test suite in a cron job, so if a bug slips, we will know. The full suite sometimes breaks, but these are due to changes outside of PR (e.g., a vendor goes down).
72.
▲
by
jampa
1y ago
Thanks! > Are you seeing a lower number of production hot fixes? Yes, with E2E tests in general: They are more effective at stopping incidents than other tests, but they require more effort to write. In my estimation, we prevent about 2-
73.
▲
by
jampa
1y ago
We still run E2E tests before deployment, but running them on pull requests also eliminates the question: "We want to deploy, but have a bug. Which PR caused it? and how do we fix it?" This approach essentially saves you from havi
74.
▲
by
jampa
1y ago
I think you might be confusing end-to-end (E2E) tests with other types of testing, such as unit and integration tests. No one is advocating this approach for unit tests, which should still run in their entirety on every pull request. Runnin
75.
▲
Using Claude Code SDK to reduce E2E test time
(jampauchoa.substack.com)
105 points
by
jampa
1y ago
|
75 comments
76.
▲
by
jampa
1y ago
> And charging stations are run by multiple vendors with multiple apps and payment methods. I rented a PHEV in Spain, and this was the biggest issue. Every charger has an app. They want all your information, even your home address, befor
77.
▲
by
jampa
1y ago
As someone who is also writing a book (for the first time), I hate how accurate this is. I wrote my first draft in 3 months, about 200 pages... Six months later, I haven't delivered a quarter of the book. And I will probably revisit th
78.
▲
by
jampa
1y ago
"Carbon offsetting is like saying to your husband or spouse: ‘I’m going to cheat, but I’ll buy you a diamond ring.’" Sometimes, the carbon offsets are from projects that would be built anyway, and there is a lot of sketchiness all
79.
▲
Distilling Impact and Prioritizing the Right Things
(taoem.com)
2 points
by
jampa
1y ago
|
0 comments
80.
▲
by
jampa
1y ago
I think not hiring juniors is a tragedy of the commons situation. It started before the AI boom, during COVID. It's not tax-related as people claim here, since this phenomenon is not US-only. The ZIRP era made companies hire people as
81.
▲
Why AI for coding is so polarizing
(jampauchoa.substack.com)
1 points
by
jampa
1y ago
|
0 comments
82.
▲
by
jampa
1y ago
I remember working at a company where we used a vendor extensively in their mid-tier plan. We wanted an enterprise plan with more features, so we reached out to buy it. So, their salesperson was shooting a penalty with no goalkeeper: All th
83.
▲
by
jampa
1y ago
I feed the `git diff` of the branch (excluding large files like package-lock) and a list of the E2E files. Claude reads and compares the E2E tests against the modified content. The good thing about Claude Code is that it uses tool calls to
84.
▲
by
jampa
1y ago
I work in an app where bugs are unacceptable due to the nature of the company's reputation. We've been having a lot of success with E2E, but getting there was NOT easy. Some tips: - False negative results will make your devs hate
85.
▲
by
jampa
1y ago
Unless something changes in the underlying infrastructure, most packages don't need active maintenance after achieving their objective. If there is a major change (e.g., Python 3, React Native new arch), they are replaced/forked.
86.
▲
My advice to Software Engineers starting their careers
(jampauchoa.substack.com)
2 points
by
jampa
1y ago
|
0 comments
87.
▲
by
jampa
1y ago
The blog works for me: https://www.anthropic.com/news/claude-for-chrome
88.
▲
by
jampa
1y ago
The Pokémon Go company tried that shortly after launch to block scraping. I remember they had three categories of IPs: - Blacklisted IP (Google Cloud, AWS, etc), those were always blocked - Untrusted IPs (residential IPs) were given some le
89.
▲
Agile: Rise, Fall and What Remains
(taoem.com)
3 points
by
jampa
1y ago
|
0 comments
90.
▲
by
jampa
1y ago
I felt that, too. It turns out I was getting 'too comfortable' while using CC. The best way is to treat CC like a junior engineer and overexplain things before letting it do anything. With time, you start to trust CC, but you shou
More ›