dvnguyen

My hypothesis is a software growth, like a business or an economy, is fueled by debt. We create technical debts, both deliberately and accidentally, to write software faster. And when the software proves itself as a viable project, we could (ideally) start paying the debt.

Rust forces users pay certain kinds of debt upfront that makes Rust attractive for rewriting, but I don't think it's that much attractive for greenfield projects. You'd want to fight your problems, not your problems plus Rust. On top of my head right now I couldn't think of any famous Rust projects which aren't a rewrite.

Personally I don't think Rust is that hard to learn and some of my side projects are being written in Rust. But if I ever had a business with Rust as a main language, I'd be worry I could find enough Rust programmers. Fortunately the community is addressing its ergonomics and hopefully one day its approachability and learning curve will also gain more attention.

Having used Docker Compose/Swarm for last two years, I remember having problems with them twice. One of which was an MTU setting which I didn't really understand why, but overall I was relatively happy with them. Since Kubernetes seems to have won, I decided to learn it but got some disappointments.

The first disappointment is setting up a local development environment. I failed to get minikube running on a Macbook Air 2013 and a Ubuntu Thinkpad. Both have VTx enabled and Docker and VirtualBox running flawlessly. Their online interactive tutorial was good though, enough for the learning purpose.

Production setup is a bigger disappointment. The only easy and reliable ways to have a production grade Kubernetes cluster are to lock yourself into either a big player cloud provider, or an enterprise OS (Redhat/Ubuntu), or introduce a new layer on top of Kubernetes [1]. Locking myself into enterprise Ubuntu/Redhad is expensive, and I'm not comfortable with adding a new, moving, unreliable layer on top of Kubernestes which is built on top of Docker. One thing I like about the Docker movement is that they commoditize infrastructure and reduce lock-ins. I can design my infrastructure so it can utilize an open source based cloud product first and easily move to others or self-host if needed. With Kubernetes, things are going the other way. Even if I never moved out of the big 3 (AWS/Azure/GCloud), the migration process could be painful since their Kubernetes may introduce further lock-ins for logging, monitoring, and so on.

[1]: https://kubernetes.io/docs/setup/pick-right-solution/

Hey, cool project!

I haven't read the book. Is that possible to understand the idea without reading the book?

If what you've heard is true, it could be pretty toxic. Do you have any evidences to back up?

I'm quite happy with algolia. Can you elaborate more?

I guess that most senior engineers receive more recruiter's emails, including from startups, than they wish, so they don't need to use Triplebyte services.

I don't have any experience in Rust. From what I read, Rust is a low level / system programming language. Comparing to dynamic languages like Python, I understand that Rust is much faster. However, Python is fast enough for most web applications. So why should I use Rust in web development? Even if the library ecosystem were mature enough, could I expect my productivity could become nearly high as in Python?

What you've described is someone who follow some practices religiously. I don't see any correlation between people like that and ones with academic background.

I took one free course in Udacity about advance computer architecture, and was really impressive with their course organization:

- Lectures are divided into small chunks, often 5 minutes or less. I'm easy to be bored, but was hardly when taking the course.

- Interactive review questions are provided for every subtopic of a lesson.

I guess Mr. Musk is preparing infrastructure for his future projects. A auto driving taxi service would have some benefits from this project:

- convenient as taxi while being fast as subway trains. - less likely to crash. - easier to estimate transportation time.

Patreon is a perfect example how people are willing to support good works. Currently, the Vue's creator is receiving $10k monthly for his works [0].

I was happy recursively paying for Pycharm even sometimes I didn't use it for months. I see many people do that with Adobe products. If I had an option to pay Postgresql, Flask, VSCode developers a small amount every month , I would be happy to pay it.

One thing I would love to see is to have an option to pay the OSS developers. There works are worth not only donations but payments. In the other side, I've seen enough higher managers refuse to use OSS. Their reasons are really understandable: "Who I'm gonna call if the software has some bugs?". Contracts, and sometimes expensive prices, are what they need before invest in new softwares.

So how these contracts should work in a Patreon-like site? If I had implemented the site, I would shamelessly copy the Patreon's tiers model. The cheap tier would require the developers just keep doing whatever they are currently doing. More expensive tiers would be for support contracts. I pay this developer for that project, and I'm guaranteed that I'll receive email support within 24h. If I pay more, I may have access to phone support. What kind of supports and how much are they worth is the OSS developer's decision.

[0]: https://www.patreon.com/evanyou

Sad I am considering to use picnicss in my next project. What you would recommend besides Semantic UI?

Domestic students do pay less. Usually out of state students pay twice what in state ones do.

One thing is really strange in this thread is that almost every opinion against Google's customer support are down voted heavily. Google advocates always say that GCP support is better. Of course they have to be better because they are the underdog in the cloud war. I can't buy the logic that GCP is Google but not that Google. What would happen if they could dominate?

Don't get me wrong. GCP as a product is really awesome. I've been using GCE and Datastore for a project and they just work. I just can't trust Google enough to bring all my works to their cloud.

I doubt whether tech companies have data to backup for this type of interview, something like the correlation between people who do well in whiteboard binary inversion interview and people who do well in real world jobs. Or they just do it because that's the way Google does it.

I also prefer command line to GUI for many tools. However I've worked with some truly great programmers who always try to find a GUI application for editor, git, svn, debuggers, etc. Was my command line way the best practice? I doubt that since they still get the job done with good pace. My guess is that personal tastes define work flow. For me, it's easier to type, but for them GUI has been strongly integrated to their muscle memory.

Coincidently I've just read several chapters from the Learn you a Haskell book. I couldn't write any serious Haskell project in near future, but learning it has been so much fun. No surprised when many other programmers are touching it on weekends.

Reading this makes me realize how naive I was. I thought I could rent a cheap dedicated server from OVH and leverage Docker to build nice infrastructure without paying too much. Better staying with Google/AWS then.

I may be naive here. I hope Github/Gitlab would implement a similar feature to their platform with a option to pay the developer. I don't mind donate $500 a month to a good OSS because a good developer costs at least 20 times that amount, but it would be nice if the expense is accountable.

Could you share a bit more about public speaking? It's my fear too.