601 karma · joined March 6, 2018
veeralpatel4@gmail.com
http://veeral-patel.com/
I would highly recommend downloading it if you sometimes take a look at GitHub repos when on your phone, which I think is most programmers.
Unfortunately I didn't use it for about fourteen days or something so my beta access was taken away :(
Is the latter worth buying and playing?
Also: if there's a design doc out there for Plague Inc or a similar game, I'd love to see it.
I'd be happy to discuss this topic with anyone; my email address is in my profile.
But they are time-consuming to write in mainstream languages, so developers often won't do it if that's their only choice.
https://www.destroyallsoftware.com/screencasts/catalog/funct...
But also, a developer may not even write it if he or she feels pressured to do this.
Here's a thought experiment: say you're seeding data into your local database server using the `mysql` CLI.
- Would you write and check in shell script to do this, so coworkers can use it? Probably yes.
- Would you write a Python script to do this? Probably no.
- Would you write a Java or C program to do this? No way.
For me, if I was part of a small team, I would choose a hosted service everytime so I don't need to do any ops work.
I deploy my React apps and landing pages there and don't need to worry about the underlying compute, or load balancing, or anything else. Thankfully I didn't do any frontend work before Netlify was available!
I don't really get all the hype around the Jamstack (https://jamstack.org/), though.
Netlify's hypothesis seems to be that if you deploy websites on CDNs, instead of on web servers, then you'll get better performance.
Also, because it's just a static site, there's no backend or database, so you get better security.
I accept this hypothesis, but it seems like you still need a backend. Netlify is promoting functions as a service [1] so you can avoid having web servers for the backend too, but I'm a little skeptical you get the flexibility to build applications with dependencies or non-trivial business logic or design with this approach.
If anyone's tried a FaaS and this is incorrect, please describe your experience!
Yes, Y Combinator (ycombinator.com) is a top startup accelerator (and the owner of the site you are currently on).
They fund batches of 150+ startups twice a year. W20 means they were in the first batch of this year.
I went ahead and read all your posts in the series:
https://posthog.com/blog/before-the-yc-application/
https://posthog.com/blog/the-yc-interview/
https://posthog.com/blog/moving-to-sf/
https://posthog.com/blog/pivot-to-posthog/
https://posthog.com/blog/after-the-hn-launch/
I'd recommend them to anyone who liked the linked post.
This doesn't factor in the ongoing PR cost of headlines like "FCC weighing fining ISP X", "FCC fines ISP X", "ISP X appeals fine", "ISP X loses appeal", etc.
Still, I agree the fine could have been harsher.
When you think you've thought of a great idea, by definition, you're biased toward it.
If you then start building it, the sunk cost makes you even more resistant to abandoning it.
In my experience, just "building the product" can take a lot longer than you expect. I've spent several months building out what were mostly CRUD apps.
Why? I didn't realize it at the time, but I was working part time, I had to figure out how to do many things for the first time, I had to keep myself motivated, and I had to do development but also design and PM work.
If I was working on something new, I probably would:
1. think of a problem to work on
2. talk to a lot of users following the Mom Test (keeping in mind your product has many personas of users) to validate the problem
3. think of a lot of ideas to solve the problem
4. somehow identify what idea to prototype first and what the feature set should be
5. prototype it in Figma, show it to users, improve the prototype until customers are asking "when can I buy this?"
I haven't done this yet. If anyone has any suggestions for getting from set of ideas -> a prototype users want, I would love to hear them!
In your specific customer interview, I would probe deeper. For most real problems people have, they've hacked together a makeshift solution. It may work, but it doesn't mean it works well. It doesn't mean the problem is solved.
I would ask "how is it like working with this larger company?". If you have any specific pain points working with larger companies that you've seen, I'd ask "how do you deal with pain point X?"
I doubt someone would say something is their biggest problem if they have a great solution for it!
The name seems to imply something the tech does something that it's not, though in all fairness to Tesla, they are very clear about the fact that Autopilot does require an attentive human at the wheel.
One question: How well do languages like Haskell work for code with side effects, though? Say I want to write a CRUD web API. How easy is it to work with network requests and database operations, for example, in Haskell?
I have to disagree. The execution is what really matters, not the idea.
- Could BBC have hired the talent to build and scale a credible competitor?
- Could BBC have popularized the model of on-demand, subscription based TV?
- Could BBC have acquired and created content people want to watch?
If the answer to these questions is yes (and the regulations in question aren't a problem), I would highly encourage BBC to launch a video streaming service today!
Today's code will become tomorrow's legacy.
And thanks for open sourcing your tech! I see some legitimate critiques in the comments here - "it's not production-ready but you claim it is", "you shouldn't have built your own e-commerce solution" -- but even if no one uses your open source project, people can learn from it.
Can confirm that it's back up now.
Reading this HN thread, I got the impression GitHub actually did just copy/paste Issues into a new tab, as a commenter mentioned, a belief that was backed up by a cursory look at Next.js's Discussions.
Now I see that's not fully the case.
https://spectrum.chat/spectrum/general/spectrum-is-joining-g...
But I would caution against integrating too many tools into GitHub. As a user, I like that GitHub errors on the side of saying no. You don't want to end up with a bloated product.