pksunkara

I am building a new code forge at https://juju.bi

It's not agent-first, but I can't think of any features that are needed for agents other than scalability.

Let me start off (assuming all code forges have PRs)

  1. Branch protection rules
  2. CI
  3. Terraform provider (API)

I would love to know the need behind pushing over HTTPS. Is the SSH protocol not good?

I think the CLI is useful for pushing. What do you use to push all the rebased child branches?

I am still curious why they stopped offering their original service. What was the feedback from users? Why did developers not want to use it?

Thanks, missed that part. I would still be interested in knowing how much additional storage that adds, if the OP is interested in updating the article.

I think a stored generated column allows you to create an index on it directly. Isn't it better approach?

I am working on something for that at https://automa.app. Let me know if you are interested in trying it out.

Actually,

1. `color` feature and thus the `anstream` dep is optional.

2. Even if you use it, it handles all the behaviour correctly regarding the piping and no color support, which is why it is a dependency in the first place.

Source: I am clap maintainer

This ulid Postgres extension doesn't have any performance issues compared to native uuidv7 in Postgres. https://github.com/pksunkara/pgx_ulid. Just wanted to bring it up since it looks like the author didn't come across it when looking for ulid generators in postgres.

Disclaimer: I built it.

Where can I learn more about this? You guys don't seem to have any docs available.

How do you guys differ against https://www.speakeasyapi.dev and https://www.buildwithfern.com and https://liblab.com?

Implementing support for UUIDv7 does not equal implementing support for ULID. ULID needs to be treated as a first class citizen (type, read format, storage format, converters) instead of being an afterthought result from UUIDv7.

I have built a postgres extension for adding ULID support which does what I described. https://github.com/pksunkara/pgx_ulid

Hey, thanks for posting this. :)

We reduced our service server costs to 1/6th by moving from Heroku to Lambda. And that's not even considering the main benefit of a big computational request not blocking other requests (which is why we moved to it in the first place).

I have written a webpack plugin which generates `.vue` files automatically and you just keep writing `js`, `css` and `html`.

https://github.com/pksunkara/vue-builder-webpack-plugin

What do you think about API Blueprint [1]? It is based on Markdown.

[1] https://apiblueprint.org

Can I suggest API Blueprint [1]? It is much more human friendly and easier to work on API design. Apiary has tools for complete API lifecycle management.

Disclaimer: I work on making API Blueprint better.

[1] https://apiblueprint.org

You can but I didn't like it and wanted to use react.js

This is such a cool move from google. Doing material design in HTML/CSS/JS is pure win.

I am working on React.js components for this. I have already did half of them. Check out https://github.com/pksunkara/react-mdl. I welcome any contributions.

EDIT: Components can be seen at https://github.com/pksunkara/react-mdl/tree/master/src

Apiary (http://apiary.io) - FULL TIME - San Fransisco, CA or Prague, Czech Republic

TECHNOLOGY: Node.js, Backbone, Coffeescript

Visit https://apiary.io/company#jobs for more details on the jobs.

==========================================

Fullstack Developer (Core Application Team)

===========================================

As a member of the Application team, you are going to be responsible for crafting, delivering and maintaining the main apiary.io application (including the Apiary for Teams feature set).

In this vertical team, you are going to collaborate with your fellow team members on providing the best tooling and platform for designing, developing, and maintaining APIs worldwide.

Building great APIs is all about effective collaboration, be the one building the tools (teams, managing a team, user roles, access control, ...).

You'll be developing one of the most-used API Documentation worldwide. Documentation including interactive Console, documentation that has to run smoothly on mobile and touch-based devices, has to support plenty of customization options, and on top of that has to be super fast.

Don't forget about Mock Server and Debugging Proxy. Mock Server is all about speed and pairing responses defined in an API blueprint (choosing what response is the best fit). Debugging Proxy is a tough one. (...). Don't leave out payments (trials, subscriptions, ...).

You'll be responsible for the most visible part of our product suite that defines how Apiary is perceived.

You can try using API Blueprint (https://apiblueprint.org) which is based on Markdown can host your API docs at http://apiary.io

Disclaimer: I work at Apiary

Better golang package management.

Disclaimer: I work for Apiary.

API Blueprint [1] is an open source API description format which can be used to intuitively describe an API.

MSON [2] is a recent addition to the above format which makes it easy to describe all kinds of complex requests and responses in the spec.

You can email me at pavan [at] apiary [dot] io if you have any more questions.

[1] http://apiblueprint.org

[2] http://github.com/apiaryio/mson