3,884 karma · joined March 14, 2013
building Superuser, come join :)
https://superuser.app
https://x.com/keithwhor
Truthfully, it's increasingly my opinion that design patterns (and by extension, anti-patterns) only exist in the context of focused, internally consistent systems architected by a small group of individuals and not a committee. Rails, especially early on, is a great example. Actually -- a huge chunk of programming languages are built this way. The web, however, is designed by committee.
With this framing, "avoiding margins" works for the way Max builds design systems -- and from what I know, he's very talented and the team(s) that work with him should adhere to the systems he constructs. I'd love to see an implementation of an entire framework / design system that avoids margins -- something like Tailwind CSS. I do not, however, really believe this is broadly applicable advice. Most people are just trying to ship something that looks nice, and margins can be overwritten and adjusted easily.
NOTE: I have components I've written that have margins I have to overwrite nearly universally, but can't remove because of other UIs relying on the margin behavior. So I understand where the argument comes from. It's just -- I'd have a hard time if anybody tried to pick a bone with a software engineer on the team about the use of a margin if the initial intention was good / legitimate.
> "Markdown's syntax is intended for one purpose: to be used as a format for writing for the web."
> So, I want to finish this article with the simplest conclusion ever:
> "Do not use Markdown for things it was not designed to do. For example, to write documentation."
Documentation is a form of writing on the web. Am I missing something?
This does not sound great. Can somebody clarify as to how this is a sensible move at all / what the intention is?
https://autocode.stdlib.com/new/?event=scheduler.daily&event...
This link will set up an automatically scheduled script / endpoint you can deploy in a click. Disclaimer; I built a lot of it. (Founder.) Warning is that there's a signup wall right now but it is free to use. Based on feedback we might be removing the signup wall at some point just so more people can check it out.
I'm previously the author of Nodal [1], a Node.js API framework that had quite a bit of early popularity -- we transitioned to building Standard Library [2] to focus on easily building APIs and combining them for simple backend workflows / integrations. Fits with JAMStack pretty well, generally, and our users aren't just developers; it's accessible to business users as well, provided they don't mind learning a little code. :)
To be direct, I don’t really understand your criticism — we’re a small team working like crazy to create value for folks. I get that you don’t like the way we’ve implemented our own specifications, and that’s okay, but to be honest I’m a little offput that you’re accusing me of bullshitting when I believe I’ve been straightforward with you.
If you’d like to use the product / platform and work with us to make things better, we’d love the support!
On top of that, Companies that were considering OAS now have GraphQL APIs instead — or even JSONAPI. When we need to respond to the needs of one of these companies, we need to move quickly.
I think we’re just comparing apples and oranges. We’re working on solving API integration issues in a real way, which means we build the tool for the job. OAS is an idealized, democratic position that — while absolutely a best -in-market solution — does not directly and meaningfully incentivize companies to rely upon it.
We considered an open approach, but we then watched numerous small companies die trying to convince standards bodies to adopt their innovations. Like, raised money, convinced nobody, stagnated or died, and highly paid engineers at BigCos that were unintentionally unempathetic to the excitable new founders — whose dreams just evaporated in smoke — kept attending open spec design-by-committee meetings with little forward progress.
So we decided to work directly with API companies — not standards bodies — and figure out how to deliver the right product(s) to solve real customer needs.
That’s all there is to it. We stand on the shoulders of giants and we certainly love working with companies that adhere to existing standards — as mentioned, the things we’ve contributed are completely compatible! We don’t have an ego about our specifications, we just have a desire to deliver value and not die — and waste the most productive years of our lives — waiting on standards bodies.
If it helps clarify, Autocode is for people looking to solve integration problems (A to B) for businesses easily. We can talk all day about which specification we use, but that argument is adjacent to the fact that the combination of tools we offer are faster by one — if not two — orders of magnitude at just delivering business value — a finished software product that connects A to B (to C to D).
We’ve spent years of work developing this tooling and thousands of hours talking directly to both API companies and end-users about what they need. This is the result, and we’ve worked at making sure the tools we use — even if bespoke — are open source for others to learn from [1].
P.S. If this is your jam, reach out! We are hiring :)
[0] https://github.com/keithwhor/nodal
Coming soon!
Standard Library is the platform / registry and Autocode is the IDE. We’ll keep these two. Outside of legal docs and filings you probably won’t see Polybit that much at all :).
Thanks, we’ll look into communicating this more clearly. :)
The way 99.99% of developers have used us to date is starting with our in-browser or CLI tooling which installs / requires the correct package automatically. So I think that removes some of the risk you're talking about. :)
You can hold on to the NPM package for now if you'd like! That's a good one. If we do find typosquatting becomes an issue, do you mind if I reach out?
The reason `result.ppm` didn't autocomplete was because I didn't specify a return schema when I built the service. It's up to the developer who builds the API to specify nested object schemas via the FunctionScript specification [0] and I hadn't. It was a long day and I didn't feel like re-recording the entire video. :) Long way of saying -- it'll work if you want it to.
TS could be neat, it's conceptually not difficult, the question of implementation is ultimately: where does our team's time go as we continue to roll out features for business users? About half of our users are not professional developers so balancing between pro / not-pro is part of what makes our roadmap planning interesting.
Ooh! Right click / context menu. I gotta fix that. D'oh.
I think there are different schools of thought re: providing a playground. We certainly have done that before with smaller launches. Our experience (anecdotally, I haven't measured exactly) is that while "playground" type experiences can sometimes increase signup volume, they tend to result in lower engagement rates overall.
I believe the basic underlying hypothesis is that if you can solve a problem somebody is having and they know that, they don't care how it works: they'll sign up and figure it out. However, if you provide a playground, you artificially select for a much higher proportion of folks who enjoy the novelty of new technology / products and aren't necessarily likely to stick around.
Food for thought, anyway. Don't have raw numbers here.
Let's say BIGCO pays you $X00k to build big, awesome production systems. There are 10x as many professional developers as you building small, hacky transient code within enterprise cos and SMBs and 100x as many tinkerers, creatives, admins, product managers and more just slapping together Airtable and Zapier as fast as possible to automate their jobs.
Autocode isn't designed for the top of the pyramid. I mean, all the features can (and should!) certainly be used by folks at the top. You'll find that for a huge # of simple tasks -- tasks that don't matter where they live, like one-off daily crons -- Autocode is just plain faster. But the important thing to think about is the folks a bit downstream of the "top", the ones implementing solutions less focused on architecture and more focused on solving immediate business problems... that's where Autocode is designed to play well.
Hope that helps!
I expect the easy way to get around this is for folks to refer to us, when speaking technically, as "stdlib.com" ("standard lib dot com").
(2) I actually think this can be fixed with a few HTML attribute changes but I won't know for sure until I dig in. If you can imagine, we have a laundry list of items piling up to take care of :)
So we roll our own components for a lot of this stuff. We don't have problems with every password manager; the raw HTML input element is still there. I think it's probably an easy fix, we just gotta look into it.
We have businesses that run on top of us today that are only just beginning to automate huge chunks of their operations with us, Airtable, Slack and other tools. Previously these things were hacked together in an unmaintainable fashion. It’s a big space.
We do indeed have custom auth and pricing in the works :). Can’t give an outline on delivery because we have so much other stuff to take care of, but the API registry is already built to handle these use cases.