• 0 Posts
  • 50 Comments
Joined 3 years ago
cake
Cake day: June 11th, 2023

help-circle
  • This is a really great point. AI tokens are expensive for quality today, and that will continue. We’re already seeing a bit of a plateau, and this whole “let’s slow down so we don’t kill ourselves” is propaganda, I think. AI companies that leverage “price to value” are going to succeed. I see Google Gemini fitting this mold long term, GLM, Kimi did fit this mold but their later models seem to jump in price pretty fast chasing Opus capability. If you take “capable models” as the standard for price to value and then charge what it actually costs (not VC subsidized), then you’re going to see a world where Software Engineers are probably back in high demand. I think the article points out the hard part: how do you grow new Sr. Engineers if you’re replacing Jr’s with Claude. (I think the obvious answer is that we shouldn’t be replacing Jr’s with Claude)


  • I think saying “we are all product engineers” is not accurate, but this aligns with stuff I’ve been telling my teams for a while. Everyone needs to start becoming closer to product and moving away from programming as the thing they’re valued for. (e.g. I’m not valued because I know Java inheritance rules) To be honest, it always should have been this way (it’s how I’ve lived my career), but some organizations have created this weird “product does the thinking, engineering does the programming” dichotomy and it’s in those situations where this argument makes sense. At a small startup where every new hire understands the business problem and works to achieve that goal is not where this argument makes sense.

    My first job was “Analyst/Programmer I” - somewhere along the line it turned into “Programmer” and then “Software Engineer” – pushing the role farther into a technical silo and farther away from the product “because the product managers know best and the nerds need to make it happen by next quarter /s”. The success of individuals on the product side are going to be with folks who can shift to leverage AI for technical chops, and vice versa for Engineers shifting to put on their “Product Hat” more often. With any career, there’s going to be a spectrum of what skills fit into the role (e.g. some positions may be more or less technical or more or less business analyst), but I see the shift happening as a way to preserve ones career in an ever changing world. Those that do not adapt will find themselves on the outside looking in and wondering why (or as an alpaca farmer in northern Idaho because they noped out).






  • I bounced around a bit after Storj decided to hate consumers and institute massive minimums.

    I’ve landed on Backblaze B2, S3 compatible. Add others have mentioned, doing a shared NAS 2 NAS hookup with a friend or family member is a nice ideal way to do it without monthly fees.

    I use Borg backup from my PCs to a NAS (QNAP), and from there using the built in backup software to go off-site. My self hosted PCs will mount NAS drives directly (like immich and audiobookshelf) and those are also in the NAS off-site job.












  • What are you using for a reverse proxy? There’s some nginx websocket settings I had to do before things worked properly. I use cloudflare, but just for the DNS/cdn stuff, not their zero trust things.

    server {
      server_name my.domain.com;
      client_max_body_size 2048M;
    
      location / {
        proxy_set_header X-Forwarded-Proto $scheme;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header Host $host;
        proxy_set_header X-Forwarded-Host $host;
        proxy_pass http://10.10.10.30:13378/;  # My Wireguard Tunnel up to the VPS
        # proxy_cache_bypass  $http_upgrade; # This was added by Certbot
        # WebSocket support
        proxy_http_version 1.1;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection $connection_upgrade;
      }
    
        listen 443 ssl; # managed by Certbot
        ssl_certificate /etc/letsencrypt/live/my.domain.com/fullchain.pem; # managed by Certbot
        ssl_certificate_key /etc/letsencrypt/live/my.domain.com/privkey.pem; # managed by Certbot
        include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot
        ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot
    
    }
    server {
        if ($host = my.domain.com) {
            return 301 https://$host$request_uri;
        } # managed by Certbot
    
      listen 80;
      listen [::]:80;
    
      server_name my.domain.com;
        return 404; # managed by Certbot
    }