• 0 Posts
  • 42 Comments
Joined 1 year ago
cake
Cake day: June 10th, 2023

help-circle


  • Years and years ago I built my own 16 bit computer from the nand gates up. ALU, etc, all built from scratch. Wrote the assembler, then wrote a compiler for a lightweight object oriented language. Built the OS, network stack, etc. At the end of the day I had a really neat, absolutely useless computer. The knowledge was what I wanted, not a usable computer.

    Building something actually useful, and modern takes so much more work. I could never even make a dent in the hour, max, I have a day outside of work and family. Plus, I worked in technology for 25 years, ended as director of engineering before fully leaving tech behind and taking a leadership position.

    I’ve done so much tech work. I’m ready to spend my down time in nature, and watching birds, and skiing.



  • The article says that steam showing a notice on snap installs that it isn’t an official package and to report errors to snap would be extreme. But that seems pretty reasonable to me, especially since the small package doesn’t include that in its own description. Is there any reason why that would be considered extreme, in the face of higher than normal error rates with the package, and lack of appropriate package description?




  • I use a terminal whenever I’m doing work that I want to automate, is the only way to do something such as certain parameters being cli only, or when using a GUI would require additional software I don’t otherwise want.

    I play games and generally do rec time in a GUI, but I do all my git and docker work from the cli.


  • Right. Which gets us full circle, to never give investment advice, lol. That being said, at some point someone may sincerely look too you for guidance and you need to make a call as to whether you want to take that risk, what advice you give, and are you sure it is good advice.

    I used to mentor student employees years ago, and when they wanted advice I always told them to max out workplace matches first, and then after that if they can save more, put it in tax advantaged savings programs that let you buy into indexed funds and never sell. In those cases you usually can’t even sell unless certain conditions are met and you sign disclosures, unlike most brokerages. Now, students you are giving them advice for the rest of there life and they likely don’t have $40k to panic sell/buy/sell to zero.




  • Yes, times a thousand. But I would go even further.

    Never give investment advice. You might explain what investments you have made and why you made them, but never give advice and never urge or prompt someone to invest. You should also end every conversation with “but that’s not advice and I’m not an expert.” It is too easy for either the investment to not work out, or for them to do it wrong (wrong timing, panic sale, misunderstood the options, etc).

    The last thing you want on your conscience is someone investing a life changing amount of money just for it to go down in flames. I might invest $1000 in something that I think might pay off, tell someone they should invest, and next thing you know they drop in $40k and panic sell on a dip in two weeks, when I was planning to hold for five years. You never know.




  • So you just asked the most confusing thing about AWS service names due to how names changed over time.

    Before S3 had an archival tier, there existed a separate service that AWS named AWS Glacier Storage, and then renamed to AWS S3 Glacier.

    Around 2012 AWS started adding tiers to S3 which made the standalone service redundant. I received you look at S3 proper unless you have something like a Synology that can directly integrate with the older job based API used by the original glacier service.

    So, let’s say I have a 1TB archival file, single tarball, and I upload it to a brand new S3 bucket, without version, special features, etc, except it has a life cycle policy to move objects from S3 standard to S3 Glacier instant access after 0 days. So effectively, I upload the file and it moves to Glacier class storage.

    The S3 standard is ~$24/tb/month, and lets say worst case scenario our data sits on standard for one whole day before moving.

    $0.77+$0.005 (API cost of the put)

    Then there is the lifecycle charge to move the data from standard to glacier, with one request per object each way. Since we only have one object the cost is

    $0.004 out of standard
    $0.02 into glacier

    The cost of glacier instant tier is $4.1/tb/month. Since we would be there all but one day, the cost on the first bill would be:

    $3.95

    The second month onwards you would pay just the $4.1/month unless you are constantly adding or removing.

    Let’s say six months later you download your 1tb archive file. That would incur a cost of up to $30.

    Now I know that seems complicated and expensive. It is, because it is providing services to me in my former role as director of engineering, with complex needs and budgets to pay for stuff. It doesn’t make sense as a large-scale backup of personal data, unless you also want to leverage other AWS services, or you are truly just dumping the data away and will likely never need to retrieve it.

    S3 is great for complying with HIPAA, feeding data into a cdn, and generally dumping data around in performant way. I’ve literally dropped a petabyte off data into S3 and it just took it and did its thing.

    In my personal AWS account I use S3 as a place to dump cache contents built by lambda functions and served up by API gateway. Doing stuff like that is super cheap. I also use private git repos (code commit), private container registry (ecr), and container host (ECS), and it is nice have all of that stuff just click together.

    For backing up my personal computer, I use iDrive personal and OneDrive, where I don’t have to worry about the cost per object, etc. iDrive (not an Apple service) let’s you backup multiple devices to their platform and keeps them versioned.

    Anyway, happy to help answer questions. Have a great day.



  • It’s complicated. I gave the most expensive pricing, which is their fastest tier and includes stripping across three availability zones and guarantees 11 nines of data durability. Additionally, the easy integration with all other AWS services and the feature richness of S3 buckets makes it hard to do a fair apple to apple comparison unless you really have well defined needs. So I gave the highest price to keep it simple, and for someone who says they just have a few GB, any cost should be trivial.



  • I run a lot of tech, containerized workloads in AWS, home firewalls running on protectli boxes for all my family around the country, wireless controllers to run APs for my family around the country, but as I got older one thing I stopped rolling my own instance of was data backups. My data backs up to OneDrive and iDrive, so two copies of my data. My wife has access to both via shared credentials in a 1password folder that she knows how to access and uses regularly.

    As I got older and I had a family, the pictures of our kids, wills, financial records, insurance documents are all just too important. Every service that holds my data is paid annually for less than $200/year total and auto renews. She could call either company and prove ownership if she ever did need help getting access. Also, I can easily share folders to her.

    It’s funny how getting older makes you think of the sorts of issues enterprise teams have. Don’t implement solutions where you will be one deep, have a succession plan, and complexity is the enemy. All the tech I run now is fun and helpful, but can be replaced with a trip to BestBuy. The data and pictures however must be easy to retrieve for her.

    So I don’t have a good self hosted solution for you other than to say that at some point it’s ok to change your strategy. And if you are worried about privacy, you can encrypt subsets of your data locally before it is backed up.


  • Because they are referring to engineering disciplines that predate all of the stuff you mention. When mechanical, structural, civic, etc engineers sign off on a design (stamp it) the incur personal liability if there is a defect in the design that kills someone or causes damage. There are certifications for telecom design and processes that require them to stamp designs, but otherwise most of what is lumped together as technology doesn’t constitute engineering from a legal or historical perspective. However the titles sort of took off and created two sets of meanings.

    If software engineering was treated as engineering in the way that mechanical or others forms are, you would get a degree, get an entry level job at a firm as a junior, and after a few years, study and get certified to stamp designs/code systems, etc.

    Now, outside of places like code for flight systems, medical devices, power plants, etc there isn’t a need for that kind of rigor, but those are the areas that would require licensing if it was available.