Live data from Hacker News

The first 18 months of a startup

twitter.com

21–30 of 92 posts

Re: The first 18 months of a startup

#21
post #19

> Rolling out of bed in my pajamas and getting back to work with things precisely as I left them was the most underestimated superpower that brought me joy, focus, and speed—I had forgotten how much goes into getting ready for work. There will be so much resistance to going back to the office.

While there is some benefit to a physical office space, I can't imagine the 9-6, 5 days a week grind will ever be back for most knowledge workers.

Re: The first 18 months of a startup

#22

Earlier quoted context omitted.

“It’s like Stadia but for Chrome”

Showerthoughts: why not stream the entire OS at this point, with a dedicated storage? Like an EC2 with a desktop environment that you can access in a VNC-like way but with the resolution, FPS and input responsiveness similar to what Stadia/Mighty offers. Which will allow you to play Cyberpunk (Stadia) + browsing the web (Mighty) + do whatever else you want, like using After Effects (?).

Anyone remember Thin Clients?

Re: The first 18 months of a startup

#23
post #19

> Rolling out of bed in my pajamas and getting back to work with things precisely as I left them was the most underestimated superpower that brought me joy, focus, and speed—I had forgotten how much goes into getting ready for work. There will be so much resistance to going back to the office.

Linux TTYs is how I do it. If you press Ctrl+Alt+2, you can open a new terminal and run a new graphical interface. If you use a tiling Window Manager, you can have different "desktops" for every project. By switching you TTY, you move to that work environment where you have left your editor, tabs open, database editor, servers, etc...

It gets you in the zone almost instantly.

Re: The first 18 months of a startup

#24
/21 dont listen to these advice because that only worked one time for one person (myself)

I'm wondering if startup gurus know their advice won't help anyone but still give them because that's what people want to read. Or if they don't know this won't help anyone

Re: The first 18 months of a startup

#25

There are some useful nuggets here, but every company and founder are different. Having run three different accelerator programs I have learned to STOP assuming what makes a good or bad idea. Some of the companies I thought were certain for failure have raised multiple rounds, found product market fit, and are growing just fine. The first 18 months of a startup should include one thing, "GET SOMEONE TO PAY FOR YOUR P…

It’s obvious that a promising startup can fail, eg great idea but bad execution. It’s really not obvious that an unpromising startup could succeed, though. What were the main factors in those unpromising startups doing well?

Good execution on a weak idea can rapidly be redirected to a better idea. If you can't execute, the ideas don't really matter.

I guess it depends a bit on what you mean by "unpromising". One person might see the product idea and think "those guys are gone is 6 mo", while another might see the team coming together well and think "that team is going to do something interesting"

Also, in my experience most people are bad at evaluating these things early on.

Re: The first 18 months of a startup

#26
post #22

Earlier quoted context omitted.

Showerthoughts: why not stream the entire OS at this point, with a dedicated storage? Like an EC2 with a desktop environment that you can access in a VNC-like way but with the resolution, FPS and input responsiveness similar to what Stadia/Mighty offers. Which will allow you to play Cyberpunk (Stadia) + browsing the web (Mighty) + do whatever else you want, like using After Effects (?).

Anyone remember Thin Clients?

Which iteration?

Re: The first 18 months of a startup

#27
post #3

No opinion on the thread, but his current startup involves streaming a chrome instance from the cloud, which feels very "Internet in 2021"

Yeah...I'm skeptical to be honest. If you're running Chrome on a server, you have to fetch the website to the server, then send back to the client. Now I suppose the server could be in some datacenter with really fast internet and include some aggressive caching, but that's still two trips instead of one.

I suppose if you're running major web apps in the browser, this could be a good idea. With the rise of WebAssembly, you could end up with something like a video editor or photoshop in the browser. And yeah, if big apps in the browser becomes a thing, people will want to run the big app on slower computers. But it'd have to be one beefy server to make the latency of streaming worth the performance speed up. Maybe if you keep common sites hot in the browser JIT and share it across users it'll be really fast but holy security issues Batman.

I'm not super pessimistic about the idea. If there's one thing I'd bet on it's internet speeds increasing while compute speeds plateauing. But I'm not sure I'd bet my own money or 5-10 years of my life on the idea.

Re: The first 18 months of a startup

#28

Earlier quoted context omitted.

“It’s like Stadia but for Chrome”

Showerthoughts: why not stream the entire OS at this point, with a dedicated storage? Like an EC2 with a desktop environment that you can access in a VNC-like way but with the resolution, FPS and input responsiveness similar to what Stadia/Mighty offers. Which will allow you to play Cyberpunk (Stadia) + browsing the web (Mighty) + do whatever else you want, like using After Effects (?).

I'm working with a number of clients that are doing this. Either an outsourced vmware horizon deployment or Windows Virtual Desktop. Local hardware is only thin clients. No servers in-house, no desktops, no laptops. It isn't as good as local hardware, but it's good enough for most business applications and even video conferencing.

Re: The first 18 months of a startup

#29
post #24

/21 dont listen to these advice because that only worked one time for one person (myself) I'm wondering if startup gurus know their advice won't help anyone but still give them because that's what people want to read. Or if they don't know this won't help anyone

My optimistic view is that I think it's more that they are providing a data point rather than a conclusion. If every founder writes their experience, then maybe readers will have a large enough sample to find some signal from the noise (luck of individual founders).

Re: The first 18 months of a startup

#30

Earlier quoted context omitted.

“It’s like Stadia but for Chrome”

Showerthoughts: why not stream the entire OS at this point, with a dedicated storage? Like an EC2 with a desktop environment that you can access in a VNC-like way but with the resolution, FPS and input responsiveness similar to what Stadia/Mighty offers. Which will allow you to play Cyberpunk (Stadia) + browsing the web (Mighty) + do whatever else you want, like using After Effects (?).

At least a few banks have been running like this since 5+ years ago, and at least one collaborated with AWS which led to this: https://aws.amazon.com/blogs/aws/amazon-workspaces-desktop-c....
Post reply on HN