51–60 of 72 posts
How did we as an industry go from "create a blog in 10 minutes" with rails to a "create a twitter clone in 7 days"? It seems we have gone backwards in terms of speed of getting things done in the last decade.
The page is empty. Blocked by uBlock Origin.
Lurker here. Someone mentioned this the other day here too. Too bad Twitters dying, but you get the idea. https://news.ycombinator.com/item?id=13157254
Lurker here. Someone mentioned this the other day here too. Too bad Twitters dying, but you get the idea. https://news.ycombinator.com/item?id=13157254
Twitter dying is a huge opportunity, they've certainly proven the demand for it. It's a surprise there aren't thousands of VC-backed wannabes popping up already. Would be really interested if FB or Google bought them out and sought to integrate.
How did we as an industry go from "create a blog in 10 minutes" with rails to a "create a twitter clone in 7 days"? It seems we have gone backwards in terms of speed of getting things done in the last decade.
On a one-machine scale, Twitter can be a single Postgres table, or a single ElasticSearch index. At the scale they actually are, it's really a whole lot more.
I'd really love a tutorial—or possibly a whole book—that instead took you through setting up the sort of distributed system that is required to make a Twitter clone run at a Twitter-like scale. Either through IaaS APIs, or on your own with something like OpenStack DevStack.
It could probably start where this tutorial ends—with a one-node system running a Twitter-backend-alike monolith. And then each chapter would increase the scale, introduce a problem the scale causes, and then walk you through adding in an additional component: a message queue; a fragment cache; app-level health checks; a search indexing cluster; distributed logging + request tracing; geographic sharding; multi-master DB replication—in order to solve that scaling problem.
There would also be scale-points that would require changes in the business logic: making IDs globally unique and sortable ala https://github.com/twitter/snowflake; deprecating but keeping around old APIs as new ones are added; "Ball of Mud" refactorings; isolated Enterprise clusters of the app; etc.
Bonus points if later chapters actually go back and rip out solutions that were introduced in earlier chapters—not because they were mistakes, but just because they were right for 10^3/s but not 10^6/s. And bonus bonus points if they assume an SLA that requires that such switchovers occur without downtime.
How did we as an industry go from "create a blog in 10 minutes" with rails to a "create a twitter clone in 7 days"? It seems we have gone backwards in terms of speed of getting things done in the last decade.
Not really creating a blog in 10 minutes using a framework is very different from learning to build a twitter clone with without one is not comparable in my view.
Is there anything like this for heavier topics like AI,ML etc?
Earlier quoted context omitted.
Yeah long story on how I ended up here. I was using http://teachable.com , but then I decided it would be easier to use jekyll since it's good for code highlighting. I already had the homepage built in leadpages, so I used their snippet to include it on the page. I don't like it, but I haven't had time to rewrite the page.
Ouch - I'm the CTO of teachable, had syntax highlighting on the todo list forever - it just got bumped up on the list.
The code highlighting was a big one, but I also had issues when updating raw HTML. I would create a code block in raw HTML and then go to update it later. When I updated it, the elements that were there previously would be escaped after updating. So any time I needed to update raw HTML, I had to recopy the entire snippet since saving it would mess up what was there.
Other than that, I would've liked a little more detail for stats. I think I was trying to segment users by how much of the course they completed, but didn't find an easy way to do that.
I like the Teachable platform and I'll be making other courses in the future. I'll more than likely switch back to Teachable when the syntax highlighting gets done.
If you have any questions, feel free to reach out at shane at trysparkschool.com. Thanks!