anttiviljami

7 ms·

1.
Product Engineer Checklist [pdf](productengineer-content.s3.eu-west-1.amazonaws.com)
1 points by anttiviljami 2y ago|0 comments
2.
productengineer.org(productengineer.org)
1 points by anttiviljami 3y ago|0 comments
3.
Product Engineer Manifesto(github.com)
1 points by anttiviljami 3y ago|0 comments
4.
by anttiviljami 3y ago
Thank you for the kind words!
5.
by anttiviljami 3y ago
Ah nice! Mind sharing what you’re using to generate the spec?
6.
by anttiviljami 3y ago
You don’t actually want that. Code should not inform design. Design informs code.
7.
by anttiviljami 3y ago
The code first approach is surely enticing and miles better than manually keeping the openapi spec up to date. But I’d always advocate for going schema first. This has huge benefits for collaboration between frontend and backend engineers a
8.
by anttiviljami 3y ago
The spec is used in runtime for routing and validation. https://openapistack.co/docs/examples/building-apis/
9.
by anttiviljami 3y ago
> The average GraphQL API is definitely in better shape than the average REST API Totally agree. GraphQL tooling is generally just better. It enforces a Schema first workflow and thus more emphasis on conventions and design. OpenAPI tend
10.
by anttiviljami 3y ago
Cheers! Going from code first to schema first is definitely worth it in my experience! Especially when working in a team. The nice thing is you already have an openapi spec, so it’s pretty trivial to eject from fastify swagger and switch to
11.
by anttiviljami 3y ago
I think the point is, graphql apis tend to be so flexible that it’s easy to accidentally ship an API that allows clients to craft excessively heavy nested queries in a single request. Supporting nested queries isn’t really a common thing in
12.
by anttiviljami 3y ago
I don’t really agree GraphQL is somehow more ”future proof” because it doesn’t use as many HTTP features. It’s not like HTTP is going to go away in a while. I find that AsyncAPI is a nice extension of OpenAPI/REST ideas if you need to
13.
by anttiviljami 3y ago
Speaking personally as a full stack engineer, unless the backend is completely trivial to implement I find it much faster and more efficient to write and iterate JSON schema while implementing frontend features than actually implement backe
14.
by anttiviljami 3y ago
Thank you for your encouraging words and insights! There are indeed popular DSLs and code to openapi solutions out there. Many of which are easy to plug in to the openapi-stack libraries btw! I guess I personally always found it frustrating
15.
by anttiviljami 3y ago
Thanks for the feedback! There is a full interactive sandbox example on the front/landing page https://openapistack.co But point taken, will make sure code examples are visible on the overview page
16.
by anttiviljami 3y ago
This project is precisely for devs who dislike codegen and want to just ship products fast. 1. Design your API in yaml 2. Run a mock API 3. Develop the App, iterate mock API 4. Implement backend and ship No code generation needed. Generate
17.
by anttiviljami 3y ago
Thanks for the encouraging words! So far it’s already nice to see these libraries being adopted slowly by more and more companies. Not nearly as big as graphql and trpc of course.
18.
by anttiviljami 3y ago
Love tRPC! For full stack typescript teams it’s the obvious way to go. Super simple and straightforward. OpenAPI or GraphQL are great though if you’re investing into APIs as a product
19.
by anttiviljami 3y ago
Agree. GraphQL is well mature by this point.
20.
by anttiviljami 3y ago
Yes! SOAP wsdl, but json
21.
by anttiviljami 3y ago
Good idea to add to the comparisons page! The openapi-typescript package is a library for generating types from openapi spec, similar to the openapicmd typegen command provided by openapi-stack. The new openapi-typescript-fetch seems simila
22.
Show HN: REST Alternative to GraphQL and tRPC(openapistack.co)
123 points by anttiviljami 3y ago|73 comments
23.
Show HN: GraphQL-like full stack typesafe development for REST(openapistack.co)
13 points by anttiviljami 4y ago|2 comments
24.
How to implement a Lambda back end based on OpenAPI(advancedweb.hu)
2 points by anttiviljami 6y ago|0 comments
25.
Whitepaper: Into-Docker, approach to reusable build environments(github.com)
2 points by anttiviljami 6y ago|0 comments
26.
ERC-20 Toilet Paper Coin(toiletpaper.website)
3 points by anttiviljami 7y ago|0 comments
27.
Replacing coordinates with MGRS(medium.com)
3 points by anttiviljami 9y ago|0 comments
28.
VR headset from ex-Nokia employees with 'human eye-resolution'(theverge.com)
1 points by anttiviljami 9y ago|1 comments
29.
Alvarcarto – Design posters with OpenStreetMaps data(alvarcarto.com)
3 points by anttiviljami 9y ago|0 comments
30.
Busting the Myths of Accessibility(foxland.fi)
1 points by anttiviljami 10y ago|0 comments

More ›