Board

Board

2272 bookmarks
Custom sorting
How to Build a Product Loved by Millions and Get Acquired by Google: The Firebase Story | HackerNoon
How to Build a Product Loved by Millions and Get Acquired by Google: The Firebase Story | HackerNoon
Firebase is an astounding tool. Hundreds of millions of people use Firebase -powered apps. The company started as backend-as-a-service for app developers that made real-time functionality simple for Shazam, NPR, SeatGeek, and hundreds of thousands of other apps. Since being acquired by Google in 2014, Firebase has expanded to become Google’s app development platform and an indispensable developer tool. The company that does so much to simplify developer’s lives began its life as something completely different.
·hackernoon.com·
How to Build a Product Loved by Millions and Get Acquired by Google: The Firebase Story | HackerNoon
Feedly – More signal, less noise
Feedly – More signal, less noise
Keep up with the topics and trends you care about, without the overwhelm. Make your research workflow efficient and enjoyable. Experience the power of RSS.
·feedly.com·
Feedly – More signal, less noise
Companies
Companies
Keep up with the topics and trends you care about, without the overwhelm. Make your research workflow efficient and enjoyable. Experience the power of RSS.
·feedly.com·
Companies
Report: Zapier Business Breakdown & Founding Story
Report: Zapier Business Breakdown & Founding Story
A report from Contrary Research. Discover Zapier's founding story, product, business model, and an in-depth analysis of their business.
The average business today will use 88 applications across their organizations, and business professionals use 9.4 applications per day to complete their work. The application interplay is typically a repetitive chain of actions following an initial trigger. As one example, someone fills out an Airtable interest form, which triggers an email being sent out. That email triggers a meeting being booked, and that meeting populates a set of fields in a CRM.
In a 2021 survey, 88% of SMBs said business automation allows them to compete with larger companies, and 9 out of 10 knowledge workers claim automation improves productivity. Knowledge workers are the majority of the labor force, representing over 100 million workers in the United States, and 82% use or are planning to use automation software.
Wade Foster (CEO), Bryan Helmig (CTO), and Mike Knoop (President) founded Zapier right out of college. Over two days at a Startup Weekend event in Missouri, the trio built a product prototype that would later become Zapier. Their idea was rejected by Y Combinator, but the team continued to build the Zapier on nights and weekends.
Zapier was an early pioneer of the product-led growth sales motion. They made it free for any prosumer to get started without approval from their IT teams. That allowed the company to save on having a large sales team and helped them reach profitability two years after its founding. At their core, Zapier is positioned to make money only when users save time. The more time users save with zaps, the more likely they are to build other connections. The more number of connections, the more money Zapier makes.
Some of the most commonly connected tools on Zapier, like Slack, Salesforce, Google, and even Calendly, have announced workflow integrations products within their existing platforms to upsell their customers and capture the value of their integrations directly. Instead of having to rely on Zapier to connect Calendly to any other application you can build that same integration natively without having to leave Calendly’s platform.
Transfer by Zapier enables customers to process batches of data too large for the traditional Zapier pipeline to process. Transfer strengthens Zapier’s infrastructure to handle larger loads. The more data-centric every company becomes the more they need systems to manage that data. Zapier’s expansion into Transfer places them in the data pipeline market along with companies like Fivetran.
With the 2020 announcement of Google Workspace and Microsoft bundling their productivity suite into Teams, Zapier faces platform risk from these two major productivity suites. Zapier’s top 2 integrations are Google Sheets and Gmail.
Zapier skewed from the traditional way of building a large technology company by focusing on remote work (even paying employees $10,000 to move out of the Bay Area), not taking significant venture funding, building a product-led engine without a traditional sales team (only really adding people to the sales team in 2021), and pursuing profitability rather than growth.
·research.contrary.com·
Report: Zapier Business Breakdown & Founding Story
Prometheus: The Documentary
Prometheus: The Documentary
Watch and witness the journey of open-source monitoring system, Prometheus. Before Kubernetes existed—even before Docker—the team at Soundcloud already knew their monitoring system deserved a complete, fundamental revamp. Of course, as with anything in development, this was no easy task. Join us as we explore the story of Prometheus, from inception to adoption as told by the story’s key players including Julian Volz, Matthias Rampke, Björn Rabenstein, and more. In the end, you’ll see how a “problem to be solved” eventually led the industry to a completely new understanding of monitoring. We hope you’re ready to be inspired. 🔥 Check out the home for untold developer stories around open source, careers and all the other cool stuff developers are doing at cult.honeypot.io. Honeypot is a developer-focused job platform, on a mission to get developers great jobs. Wanna see what we're all about? Visit honeypot.io to find a job you love. To learn more about Honeypot: http://www.honeypot.io/?utm_source=youtube Follow us: Twitter: https://twitter.com/honeypotio Facebook: https://www.facebook.com/Honeypotio/ LinkedIn: https://www.linkedin.com/company/honeypotio/ Instagram: https://www.instagram.com/honeypot.cult/
·youtube.com·
Prometheus: The Documentary
10x (engineer, context) pairs
10x (engineer, context) pairs
Your actual output depends on a lot more than just how quickly you finish a given programming task. Everything besides the literal coding depends deeply on the way you interact with the organization around you.
For those who work inside Google, it’s well worth it to look at Jeff & Sanjay’s commit history and code review dashboard. They aren’t actually all that much more productive in terms of code written than a decent SWE3 who knows his codebase. The reason they have a reputation as rockstars is that they can apply this productivity to things that really matter; they’re able to pick out the really important parts of the problem and then focus their efforts there, so that the end result ends up being much more impactful than what the SWE3 wrote.
·benkuhn.net·
10x (engineer, context) pairs
Be impatient
Be impatient
Impatience is the best way to get faster at things. And across a surprising number of domains, being really fast correlates strongly with being effective.
Being impatient is the best way to get faster at things. And across a surprising number of domains, being really fast correlates strongly with being effective.
the most famous, interesting, powerful people all read their own email they’re almost universally good at responding to it quickly they’re always very, very curious. they have very little time. Anything with friction gets done “later”
people tend to be either slow movers or fast movers and that seems harder to change. Being a fast mover is a big thing; a somewhat trivial example is that I have almost never made money investing in founders who do not respond quickly to important emails.
And what you actually need is this bias towards action. The best founders work on things that seem small but they move really quickly. But they get things done really quickly. Every time you talk to the best founders they’ve gotten new things done. In fact, this is the one thing that we learned best predicts a success of founders in YC. If every time we talk to a team they’ve gotten new things done, that’s the best predictor we have that a company will be successful.
That means that moving quickly is an advantage that compounds. Being twice as fast doesn’t just double your output; it doubles the growth rate of your output. Over time, that makes an enormous difference.
·benkuhn.net·
Be impatient
Think real hard
Think real hard
The Feynman Algorithm for problem solving: Write down the problem; Think real hard; Write down the solution.
In retrospect, I wish those people had just told me “think real hard.” I was looking for an easy way out—One Weird Trick to Programming Better—but programming is too hard for that. That’s my preferred reading of the Feynman Algorithm: there is no one weird trick.
But 99% of the “secret”—the thing that separates me from Gell-Mann, or Jeff Dean—is tacit knowledge. It often can’t be articulated any better than “think real hard.” But, believe it or not, thinking real hard, for real long, does work.
·benkuhn.net·
Think real hard
No one can teach you to have conviction
No one can teach you to have conviction
fast vs slow feedback • modeling people vs. modeling the problem • mentors vs. mistakes • why you should do the hard thing now
People sometimes tell me that they want to join a startup, so that they can learn how it works, and eventually start one themselves. I usually end up suggesting that they skip straight to step 2 and start one themselves. Why is that? Isn’t it better to learn from someone else’s mistakes than to have to make all of them yourself? At least for me, the answer’s been sometimes yes, but sometimes no.
I knew exactly which parts of our codebase they’d point out as the biggest problems, but that wasn’t the only decision I faced—I also needed to envision what the problem parts should ultimately look like, and then find the fastest path to get from here to there, and then spend months executing the plan. There were too many decisions, and the stakes were too high, for my 95%-accurate simulated guesses to be good enough.
Overall, I probably did a pretty bad job. But, importantly, I was able to see my mistakes play out in the real world. Instead of modeling what other people would tell me to do, I built a model of the problem directly. So when I got negative feedback, it wasn’t “Mentor X thinks this plan is bad” but “the world works differently than you expected.”
You learn many more details about why it was a bad idea. If someone else tells you your plan is bad, they’ll probably list the top two or three reasons. By actually following through, you’ll also get to learn reasons 4–1,217.
This pattern repeated itself across lots of different types of hard decision. I’d start out too uncertain to act with conviction; I’d procrastinate or implement bad plans; but after enough iterations of that, I’d end up understanding a lot more about the problem space. Ultimately, I’d end up with a broad base of tacit knowledge and heuristics that were richer than anything I could get from reading books or talking to people. At that point, I’d finally be able to build the conviction I needed to make good calls.
This applies to any domain that’s open-ended and requires a lot of complex decisions with long time horizons. Take the original example of running a company. By far the most important part of the CEO’s job is the high-conviction decisions. What product should we build? What strategy should we pursue? Who should we hire? And so on.
If you join a company where someone else is already making those decisions well, you’ll never get the type of practice that you need in order to build your own models and heuristics. You’ll end up with a good, but not perfect, model of “what would my boss do?"—a model that can make the 95% of easy decisions, but not the 5% of hard ones that add the most value.
·benkuhn.net·
No one can teach you to have conviction
Geoffrey Litt on Twitter
Geoffrey Litt on Twitter
I'm super impressed by the approach @craftdocsapp is taking to data ownership.At the same time, I think they're hitting the limits of modern data storage platforms, and hinting at precisely why we need a new kind of "collaborative filesystem".Quick thread to explain:— Geoffrey Litt (@geoffreylitt) March 22, 2021
·twitter.com·
Geoffrey Litt on Twitter
The Rule of Three
The Rule of Three
Every programmer ever born thinks whatever idea just popped out of their head into their editor is the most generalized, most flexible, most one-size-fits all solution that has ever been conceived. We think we've built software that is a general purpose solution to some set of problems, but we are
·blog.codinghorror.com·
The Rule of Three
Crypto data, where and when you need it.
Crypto data, where and when you need it.
We build products that make crypto data more accessible. Use our dashboard to explore, or pull data directly into your spreadsheet with our sheets product.
·artemis.xyz·
Crypto data, where and when you need it.
Neat – Supercharge your GitHub workflow
Neat – Supercharge your GitHub workflow
GitHub notifications on your macOS desktop. Streamline your code review and ship with ease. Alternative to Slack GitHub, DevHub, Octobox, and Notifier.
·neat.run·
Neat – Supercharge your GitHub workflow
Watch "EP000: Operation Aurora | HACKING GOOGLE" on YouTube
Watch "EP000: Operation Aurora | HACKING GOOGLE" on YouTube
What happens when a country attacks a company? In 2009, Google found out and cybersecurity was never the same again. // EP000 of the HACKING GOOGLE series → https://g.co/safety/HACKINGGOOGLE An inside look at the historic attack where Google’s network was breached by a foreign government trying to access the Gmail accounts of human rights activists. In the wake of the breach, Google revolutionized its approach to security - overhauling everything and developing highly specialized teams of elite experts to stay ahead of the ever-evolving threat landscape. Subscribe to our Channel: https://www.youtube.com/google Tweet with us on Twitter: https://twitter.com/google Follow us on Instagram: https://www.instagram.com/google Join us on Facebook: https://www.facebook.com/Google
·youtu.be·
Watch "EP000: Operation Aurora | HACKING GOOGLE" on YouTube
Being thoughtful in the Information Age, demo’ing the Muse App with Adam Wiggins - Events - Fission Talk
Being thoughtful in the Information Age, demo’ing the Muse App with Adam Wiggins - Events - Fission Talk
Muse is an iPad app built as a “tool for thought in the Information Age”. It’s officially launching out of beta at the end of August. Muse is a spatial canvas for your research notes, reading material, sketches, screenshots, and bookmarks. Arrange, scribble, find patterns and insights, make sense of your world. Creator Adam Wiggins @hirodusk is joining us to demo the app, but more importantly to cover the philosophies and ways of working behind Muse—how to approach problems thoughtfully, h...
·talk.fission.codes·
Being thoughtful in the Information Age, demo’ing the Muse App with Adam Wiggins - Events - Fission Talk
New Pioneers of Computing
New Pioneers of Computing
I compile and write dispatches from the frontiers of computing. These include links and summaries of interesting writings, discoveries of new people and projects who are working on the frontier, and updates on my personal work.
·buttondown.email·
New Pioneers of Computing
Have you tried rubbing a database on it?
Have you tried rubbing a database on it?
HYTRADBOI is about turning a data-centric lens onto familar problems to yield strange new solutions (and maybe exciting new problems). Talks range from wild ideas and unlikely experiments to cutting-edge research and production war stories. The day will alternate between blocks of back-to-back 10-minute prerecorded talks, followed by time to chat and ask questions.
·hytradboi.com·
Have you tried rubbing a database on it?