Matcha is a meticulously designed decentralized exchange that makes it safe and easy for anyone in the world to access crypto assets on the Ethereum blockchain. We provide users with the best prices by aggregating liquidity from all of the major decentralized exchanges and splitting/routing orders intelligently.
We're looking for a Frontend developer with TypeScript/JavaScript and React experience.
One of the best engineering and design teams in the space. We're setting the bar for decentralized exchange. Explosive month-over-month growth for our product, in an exciting and nascent domain. High-trust, high-ownership environment.
...a stablecoin not tied to any major fiat currency with over $600MM of value locked in the contract. That's an extremely successful product by any definition.
value locked inside is not a metric of success. By that metric Bank of America is thousands of times more successful, with 1.081 trillion dollars locked in.
Does Bank of America have a stablecoin not tied to any major fiat currency with over $600MM of value locked in the contract? (Hint: no, no they do not.)
Horribly written article -- doesn't go into any detail about the proposal, uses anecdotal data, and author is extremely biased. Seems like the author has an axe to grind. The proposal from Peirce is novel and much superior to the current SAFT framework; The SEC proposal is definitely worth a read.
That’s all fair because crypto is a solution in search of a problem space. When all you’ve got is a bicycle you’re going to try and ride that bad boy everywhere even if it’s not at all appropriate. Blockchain folks are enamored by the technology and have no concept of the problems they’re trying to solve with it so naturally fail.
This is awesome for the DeFi community. Glad to have a trusted source to aggregate liquidity from. Seems like liquidity aggregation will be commoditized on a long enough time horizon (think in terms of Plaid/Stripe positioning in legacy finance) and 0x is the first one to position themselves at the top of the funnel.
Selected as Washington's #1 Place to work! At Textio, we're changing the way people write. We predict how your writing will perform based on previous real-world results from similar documents. We have some of the largest companies in the world as customers, and we're hiring engineers across the board to help us solve difficult problems. We have a tight-knit, friendly, and experienced team, an incredible product, and a bright future.
Buzzwords for Keyword Searchers: AI, NLP, Machine Learning, ReactJS, SaaS
Telling people what they should or should not do is generally absurd. Every situation is unique and you can't possibly know another project's requirements or acceptable trade-offs.
A better approach, in my opinion, is "Here's what we did and why". The author clearly has experience in the area. Great! Tell me about your problems. Tell me about your attempted solutions and what did or did not work. Tell me what you wish you had done! I'd love to use knowledge of your situation to inform my own decision making.
But don't be surprised if my circumstances are different and lead me to prefer different trade-offs and choose a different solution. That doesn't make me a zealot or an idiot.
The irony wasn't lost on me. It's a fine line. Let me try a slightly different approach.
When I blog I've had much better luck telling people "here's what I did and why". I don't know your circumstances and can't tell you how to solve your problems. You may need to choose different trade-offs than I did. With that said, here is my problem, how I solved it, and what I learned along the way. Hopefully you can learn from my experiences and make a more informed decision for how to handle problems you may encounter.
I disagree. The thesis statement repeated several times throughout is "Monorepos don't scale in exactly the same ways that polyrepos don't scale, the tools to solve the scaling problems are the exact same except monorepos need more of them and encourage bad habits along the way."
You may disagree with that thesis, but it definitely seems to cover more than one use case.
