[1] http://www.incompleteideas.net/IncIdeas/BitterLesson.html

The problem of feature parity is becoming increasingly obvious. We tend to release new features for the few important SDKs that we are more familiar with, while the remaining trail behind.

Also, there are concerns like bundle size and bug prevention that we consider important for our users yet we have no control over when it comes to community SDKs.

Has anyone faced this issue before? Any existing solutions out there?

Comments URL: https://news.ycombinator.com/item?id=36394048

Points: 2

# Comments: 3

You can start using k8s right away, and just have 3 replicas running to start. As you scale, just up the number of replicas (and nodes as you need them) as you go.

Your real bottleneck becomes the database at that point (in addition to any blocking 3rd party APIs you may be using), which I would not host in k8s but use a managed service such as AWS RDS. This bottleneck will make itself apparent later on, depending on your application and the scale you reach. But you should definitely have the resources to cross that bridge once you, if ever, reach it, because you should be dealing with a large number of customers at that point.

The goal was to provide a hardened boilerplate app with no distinct featureset but at a minimum have things like ORM, user authentication, migrations, as well as a frontend web UI set up so that it could be used as a head-start for any web app projects in the future.

It's built for fast developer experience, while decoupled enough (a la containers) so that it can easily be taken into a kubernetes cluster for scale. (Still a monolith though.)

The project is private now, but happy share it on request. Also happy to answer any questions.

> Years later I ran into Phil at the symphony. I asked him I how he was able to come up with such a great script. He blushed and said he had worked on it for nine years. I know spending a long time writing something doesn’t guarantee success. But not giving up on a good idea almost always does.

Making time for deep focus

Prioritizing important work (whether its learning or executing on tasks) for the morning right after waking up

Healthy sleeping and eating habits

There are a plethora of tools out there to optimize your workflow, but I think that is more a matter of preference.

Videos can be hit or miss. The right videos can jam pack a ton of information and get you learning complex topics very quickly. Books and articles have their place too, though I tend to read later in the day into the evening when I'm more keen to winding down.

One common thing I tend to do: I may end my day working on something that leads me to a new pillar of information or complicated topic that I need to grok. In those situations, I stop the day there, and plan to wake up the next morning to research the topic (over coffee), and absorb any videos, articles, material I can get my hands on. Your brain can do amazing things with a little bit of caffeine and deep focus after a good night's sleep.

Comments URL: https://news.ycombinator.com/item?id=25882884

Points: 2

# Comments: 0

I built this simple web app to help me keep track of what I learn, and later opened it up to the general public. I've gotten good feedback so far - interested to hear more: https://wyl.today

The idea is one day folks could publicly share their learnings, and that one could participate in 'follower' paradigm similar to that of Twitter