• 0 Posts
  • 24 Comments
Joined 1 year ago
cake
Cake day: July 6th, 2023

help-circle
  • Modeling: YouTube is helpful here search for AutoCAD (computer aided design), mid journey actually has an unreal render I hope to export soon and ai is getting better and better at generation.

    Buying a printer: 2 main categories plastic and resin. Plastic is easier, larger scale, generally printed in pla petg or abs each with their own qualities. Resin is generally smaller and more precise(read jewelery minis), and requires requires UV treatment/chemicals to cure.

    Early recommended printers: (plastic) ender or prusa. Ender will be more maintenance and give you better tuning/control, prusa will be more expensive and work a bit better out of the box.

    Material: highly recommend just starting with pla and when you figure out the basics, you can change materials. The other ones will last longer and survive longer, but 3d printing has a learning curve. PLA is a good introduction

    First print: download the STL or model of a benchy, it may be tempting to print something cool first, but this is a tool that needs calibration. Benchies have specific dimensions to print angles, rings, platforms, bridges ect). Go download software of choice, 3 years ago that was Cura. Load the STL file and you can click around, but I don’t recommend changing much. PLA prints well around 200*, I liked to add 2-4 extra layers of “shell” for durability, hollow support TREES are fantastic for overhanging ledges - NO COLUMNS!!, 20% infill means it will be mostly hollow but print quick and have some structure. Cura would default to the most geometrically sound pattern (honeycomb). A raft will put a grid down first to stabilize, it helped day 1, but got in the way later. infill.

    Follow a youtube guide on leveling your specific printer, when the print fails, lookup what went wrong here: https://www.simplify3d.com/resources/print-quality-troubleshooting/

    3d printing is a lot of work, plastic deteriorates over time, but you can do a ton of cool stuff. I recommend finger surfboards, organization kits to start and the replica jet engine is a right of passage.


  • You can prevent downtime by mirroring your container repository and keeping a cold stack in a different cloud service. We wrote an loe, decided the extra maintenance wasn’t worth the effort to plan for provider failures. But then providers only sign contracts if you are in their cloud and you end up doing it anyways.

    Unfortunately most victims aren’t using best practices let alone industry standards. The author definitely learned the wrong lesson though.



  • My rhcsa expired and I only have experience beyond that. Your task right now is to find a job and the easiest way to do that is to leverage your network. If you don’t have a network, you need to prove that you can commit to a long term plan and learn a skill. Most people do that with degrees. Unfortunately a lot of people have degrees and technology is getting more competitive. That’s where you see school competitions and certifications. If you don’t want to do that, you’ll need to be able to speak competently to the role.

    Unfortunately right now I do not recommend platform/devops/sre for anyone breaking into the field. If I create an application today, it’s server less or bring your own dockerfile on a provided machine image. So what are you administrating? Legacy shops will be around for decades, but the future here is layered architecture not os tasks.






  • Depends on your end goal, don’t pay for yourself. Tech is hard to break into, certificates can help elevate your resume when you do not have a network to leverage. It’s often good to “top off” your resume when market trends shift and you are lacking experience. For instance right now AWS certificates are likely strong additions if you don’t have any cloud background. My rhcsa helped get my first job and is a positive for legacy LAMP and java shops. Trending forward: you will primarily be using it to support Linux based docker containers and a lot of the networking and hardware configuration will be obfuscated away. There is a non-zero amount of file ownership and user groups; but existing organizations will have figured that out already.



  • It’s a play by monopolys. They create a large platform (often free to start), integrate it with a bunch of other stuff, then charge you to use it. They can use the invested cost to leverage anyone on the platform, because it’s often an expensive lengthy process to halt processes. The ruling is essentially stating that Microsoft either needs to allow non Microsoft accounts to chat on teams or allow you to remove your word subscription without affecting your email. Both of those are good things for consumers, but Microsoft wants to hold all of the cards on all sides, and start offering bundles like cable companies. All just to limit your options and squeeze you when they want more.









  • Unfortunately most large organizations are running on enterprise releases that only lay down minimal software. Plus IT depts have heavily maintained images that immediately shuts off anything that sneaks in. Help desk is just going to disable the feature before slapping the company background image and VPN on it and giving it to standard users. They will make a ton of money in the short term and EOL the operating system when it’s no longer profitable and Linux is the default (decades from now). AOL is still out there


  • Microsoft has been building the O365 platform to lock out competitors and locking users into an ecosystem that is difficult to leave. They systematically eliminate competition and have pushed to create laws that make competition harder. In embrace extend extinguish, they are in phase 3, which is a massive red flag. They also started putting out spyware and malware into their software and have proven they can’t maintain security; making them a bad actor in a position of power. Scale is debatable, but Microsoft is undeniably evil in 2024.