Aussie living in the San Francisco Bay Area.
Coding since 1998.
.NET Foundation member. C# fan
https://d.sb/
Mastodon: @dan@d.sb

  • 8 Posts
  • 2.48K Comments
Joined 3 years ago
cake
Cake day: June 14th, 2023

help-circle
  • As someone who’s worked in Silicon Valley for 13 years… A lot of senior developers that work at big tech companies can earn over $500k total compensation (salary, bonus, and stock) per year. A higher level, like L7 at Google or E7 at Meta, can earn over a million per year. You can end up with $5-10 million net worth after 10-15 years.

    Some people end up saving enough and having enough investments to retire early and mostly live off the returns. This strategy is often referred to as FIRE (Financial Independence, Retire Early).

    Of course, people still want something to keep them busy, so they tend to end up doing something they always wanted to do but never had the time or money to do it. They don’t need the money, so can spend time just enjoying it rather than focusing so much on working. I know someone who retired in their 40s and started doing woodworking full time.


  • You don’t absolutely need a central repository for Git. It’s decentralized. You can learn the basics (committing, branching, rebasing, amending, merging, resolving merge conflicts) entirely on your computer.

    My advice would be to get familiar with using Git locally first. Simulate things like merge conflicts - have two branches that both change the same line in a text file, then merge them together and resolve the conflict.

    Once you’re more comfortable with using it locally, learn about code forges like Github or Forgejo.








  • Are there any actual issues in those commits though? I spot checked a few and they look pretty benign, and don’t really look vibe coded to me.

    Just because someone uses an AI tool doesn’t mean their work is vibe-coded slop. An experienced developer that knows what they’re doing can use AI as a tool to take care of boring/mundane parts and write a rough plan for their work, while still paying attention to the business logic and system design, and still fully reviewing everything themselves.

    A lot of the recent commits are in the test suite, and building test suites, fixtures and harnesses is something AI is fairly decent at if you give it a good prompt (give it the input, expected output, and expected side effects).






  • That’s an interesting idea that I didn’t consider. .NET does seem to have some support for WebAssembly.

    Many of the current systems were provided by various hosts for free though, which is how I expanded to so many locations. The 256MB RAM systems are only a few dollars per year, so those hosts were happy to provide a few for free.


  • In my case it needs to be a VM rather than a container (because that’s what the hosting company offers), but Alpine is looking promising so far. No issues with booting from the ISO and installing it on a system with 256MB.

    I got my app running on Alpine too. Now I just need to update my Ansible playbook to handle Alpine, and do more thorough testing. Will look into it later in the week.



  • That’s what I was thinking. I might try the cloud kernel (linux-image-cloud-amd64). It only has drivers required for VM platforms, so maybe the initramfs might be smaller? Otherwise I could build a custom one with just the things I need (only ext4 and swap, only drivers for KVM, etc).

    I’m trying Alpine as well, which looks promising.