HackerTrans
トップ新着トレンドコメント過去質問紹介求人

mnapoli

no profile record

投稿

[untitled]

1 ポイント·投稿者 mnapoli·20 日前·0 コメント

[untitled]

1 ポイント·投稿者 mnapoli·3 か月前·0 コメント

Show HN: Family Tree Maker

family-tree-maker.mnapoli.fr
3 ポイント·投稿者 mnapoli·3 か月前·0 コメント

Executable specs: running Gherkin tests with Claude Code

github.com
2 ポイント·投稿者 mnapoli·4 か月前·1 コメント

Show HN: Get the Favicon of Any Website

favicon.show
3 ポイント·投稿者 mnapoli·11 か月前·2 コメント

A bank runs serverless with PHP and AWS Lambda

bref.sh
111 ポイント·投稿者 mnapoli·3 年前·126 コメント

2022 Serverless Community Survey

serverless-survey.paperform.co
1 ポイント·投稿者 mnapoli·4 年前·0 コメント

コメント

mnapoli
·3 か月前·議論
I built favicon.show because I needed a way to display the favicon of any website.

This is built on Cloudflare Workers and their KV store.
mnapoli
·4 か月前·議論
The problem: coding accelerates, I can't keep up with tests. Either I review everything and we're not moving faster, either I don't and don't trust them

The idea: executable specs Write plain text tests, i.e. revive Cucumber/Behat (the "gherkin" language), BUT without the implementation step. AI run the tests in a browser, like human QA would.

I've been trying it out for 3 weeks:

1. serves as specs for new features 2. serves as acceptance criteria (Claude/Codex runs them after implementing) 3. serves as regression testing: run the full test suite every night

`npx exspec` runs Claude Code under the hood (with your existing Pro/Max subscription) with Playwright, all built-in. So using exspec is as easy as running PHPUnit/Pest/Vitest/… tests, nothing to install.

To be clear, it comes on top of unit tests, it doesn't replace them. It's great for covering happy paths and important business logic. It helps increase confidence, and also helps specifying new features.

I am cautious with letting AI "interpret" how to execute each step. But so far I'm pleasantly surprised : - Claude seems to respect the steps (and not fake it) - AI being very resilient, it's able to figure things out and recover (e.g. it needs to create a user but the email is already used -> no problem, it tries again with a different email address) - It uses the website UI and nothing else, it's like a human QA -> it cannot edit files, cannot touch the database, or run code - It reports failure with plenty of details, making it super easy to create issues from failures

I'm still careful and I want to scale up testing the idea, that's why I'm sharing publicly.
mnapoli
·11 か月前·議論
They are cached
mnapoli
·3 年前·議論
PHP is great for serverless because its execution model is compatible with it.

Unlike Node, Python, Java, etc. that start a long-lived server, each request is handled by PHP in a separate process.

That's what makes it really to use with serverless (and lift-and-shift, like what Treezor did).
mnapoli
·3 年前·議論
Their clients have very variable traffic patterns because they are in very different industries. They have traffic spikes at lunch, or at the end of every month for example:

> infrastructure must be able to scale and be resilient to accommodate various usage patterns. Whether it's a luncheon voucher transaction spike at lunchtime or a monthly batch of transactions by corporate clients
mnapoli
·3 年前·議論
You can deploy using the CDK for example: https://bref.sh/docs/deploy/aws-cdk
mnapoli
·3 年前·議論
Happy Depot user here, our builds are now 10 to 20 times faster: https://twitter.com/matthieunapoli/status/162009074440824422...
mnapoli
·4 年前·議論
Last step: https://bref.sh
mnapoli
·4 年前·議論
This is pretty incredible TBH