Great post btw!
245 karma · joined February 26, 2012
Great post btw!
> The INGRES relational database management system (DBMS) was implemented during 1975-1977 at the Univerisity of California. Since 1978 various prototype extensions have been made to support distributed databases [STON83a], ordered relations [STON83b], abstract data types [STON83c], and QUEL as a data type [STON84a]. In addition, we proposed but never prototyped a new application program interface [STON84b]. The University of California version of INGRES has been ‘‘hacked up enough’’ to make the inclusion of substantial new function extremely difficult. Another problem with continuing to extend the existing system is that many of our proposed ideas would be difficult to integrate into that system because of earlier design decisions. Consequently, we are building a new database system, called POSTGRES (POSTinGRES).
Feel free to reach out to me over email as well: niji@ngrok.com
https://ngrok.com/docs/guides/how-to-round-robin-load-balanc...
There is literally a hotkey for everything in linear.
Insomnia is building API tools to help organizations and developers build better APIs. Our tools are used by companies around the world, to deliver quality experiences to their customer base and partners on a daily basis. Come join us in helping others deliver quality API experiences.
You'll get to work directly on our flagship products, in our open source repositories, with a fully distributed remote team to build out core functionality and features impacting hundreds of customers and thousands of individuals on a daily basis.
Tech Stack:
- Electron, React, GraphQL, Go, Postgres
We are looking for:
- Experience with React, Redux
Nice to have
- Experience working on a remote-first, distributed team
- Experience with distributed sync
- Go Experience
Senior Full-stack Engineer - https://jobs.lever.co/kong/b325b381-42af-48e1-8050-895a28b45...
Insomnia is building API tools to help organizations and developers build better APIs. Our tools are used by companies around the world, to deliver quality experiences to their customer base and partners on a daily basis. Come join us in helping others deliver quality API experiences.
You'll get to work directly on our flagship products, in our open source repositories, with a fully distributed remote team to build out core functionality and features impacting hundreds of customers and thousands of individuals on a daily basis.
Tech Stack:
- Electron, React, GraphQL, Go, Postgres
We are looking for:
- Experience with Electron (IPC and networking a huge plus)
- Experience with React
- Understanding of web communication layers (eg.: REST, GRPC, GraphQL)
Nice to have
- Experience working on a remote-first, distributed team
- Experience with distributed sync
Sr. Full-stack Engineer - https://jobs.lever.co/kong/b325b381-42af-48e1-8050-895a28b45...
Insomnia is building API tools to help organizations and developers build better APIs. Our tools are used by companies around the world, to deliver quality experiences to their customer base and partners on a daily basis. Come join us in helping others deliver quality API experiences.
You'll get to work directly on our flagship products, in our open source repositories, with a fully distributed remote team to build out core functionality and features impacting hundreds of customers and thousands of individuals on a daily basis.
Stack:
- Electron, React, GraphQL, Go, Postgres
We are looking for:
- Experience with Electron (IPC and networking a huge plus)
- Experience with React
- Understanding of web communication layers (eg.: REST, GRPC, GraphQL)
Nice to have
- Experience working on a remote-first, distributed team
- Experience with distributed sync
Sr. Full-stack Engineer - https://jobs.lever.co/kong/b325b381-42af-48e1-8050-895a28b45...
foo[bar]=x&foo[bar]=y
We do believe in Design First Development, where the idea is designed out with the key party members as a part of that group. In this case, it could be the Lead Architect, or Team Lead, or Individual Contributor starting the specification and working closely in source control / pair programming to define that first draft to prevent things tech debt, refactoring, recoding, etc.
Once it's agree'd upon and merged into the codebase, we believe from there, should you setup a pipeline to have it be updated from the codebase, which commits to the repository, that should be allowed as long as the process is kept. So you still have tests against your specification that ensure your implementation works as described, and your specification is validated and enforced with the right policies.
We have some known gaps around policy enforcement and placement that we intend to correct soon. But, this is our belief.
As far as UI driven design, or Text driven design, I personally believe that both can be achieved. Not everyone knows these specifications and having an interface can on-board those individuals and get them ramped up quickly to service the needs and demands of the business.
Where the text form is useful for advanced users, quick changes, automation pipelines, testing frameworks, diff checking, and so forth. So we don't want to ultimately get rid of that layer either.
I think the best approach will be some form of a balancing act. Would love to hear feedback on this.
We have a big sidebar update coming up soon, keep an eye on the github issues for more info, and your comments contain some good insights us to think about.
This way the workflow can be specialized for your needs.