u/JohnnyByte64

I’m not sure where to comment and this is probably off main topic of Sis but I just had to say something…. It was said multiple times, “Follow the money” or “Is all about money”. So, Bob the dick can’t seem to be arrested But….

It seems to me that where it hurts the most for these guys, is their cash. With the amount of evidence, Civil suits are easier to prosecute. With the number if children affected, an I’m not exaggerating, you could bring a class action suit, and I would get them for 100billion. They would never be able to pay and it would take a long time but it would be part of record.

And even if there was 1% awarded, that’s 1b and would put those ass holes back to dirt poor where they came from.

Simple math…. If you want all of your prints, gcode, images of your prints, and tons of logs with user, app, and your IP data sent to China, even though you think you opt out, and then try a support call… then buy anything from Bamboo. If you want a 24x7 reliable, open source hardware solution where you have total control of your data then you can’t go wrong with Prusa MK4. Not playing fanboy but it’s just common sense.

It's not that it's 'hard' to build, it's that the documentation is incorrect, lacking - or - recent updates to stl's or the table itself make the Prusa Blog documentation, what I've been using, no longer accurate. So, for example, when you purchase 12x2 screws, as it states, it's too thin and you can't get it even finger tight. 14x2 works but a three year old could strip it. So, it's a combination of poor materials, poor engineering, and poor documentation.

You are so right on about this. I was looking to post a comment myself as I'm just finishing mine. Docs are very outdated, #12 screws are just wrong, they should be #14x2. Door hinges are very loose so the doors are cockeyed, door slots are too big so the doors just fall out (thinking about super-gluing them), not a single screw is tight due to the cardboard build quality. Lighting instructions are very poor.

I guess I just expected better engineering/better tolerances/fit-finish for something Prusa is sponsoring. I wasn't expecting to fix their models for a really basic cabinet.

This is a major pet peeve of mine, especially if you already have work experience. In my point of view, companies do this because they do t know how to interview and don’t understand technology. This a their way of turning interviews into a True/False objective interview rather than subjective where they would need to understand what they’re hiring for.

Engineering is all about problem solving. If I actually have a need to reverse the order of the alphabet, I’ll look it up, but if you’re going to test me on this or any other “leetcode” challenges, I’ll go somewhere else where they know how to interview.

I just moved back to Fargo/Moorhead from Shakopee MN (Moorhead class of '85). I was in the cities for about 25 years and Shakopee has a large Amazon Distribution center there that was built about 5 years ago and here's what I've noticed:

Forget any Tax benefit. Amazon is brutal in their negotiations. Cities think they're going to get this huge tax windfall and tons of new jobs but in the end, the city always comes up the loser. They use their size to bully cities to give them tax credits and if they don't get what they want, they go somewhere else - offering jobs to the next victim. It's not unusual to see them not pay any taxes for the length of their stay. It's cheaper for them to back out of a contract after 10 years than to pay taxes.

All the jobs are minimum wage jobs for people to box items. The warehouses are highly automated so there's very few people who make more than the minimum. This doesn't mean anything but yes, the large majority of people working at the Shakopee Distribution center are Somali. Every few months, they walk out because Amazon doesn't give them enough time to pray 5 times a day. Hey, if that's what they want to do, fine, as long as it doesn't add work to others.

My daughter worked there for a short time. Usually 4 x 10 hour days but burnout is high. Same gig day after day. You never leave your post - they have "runners" to get you things: They run from station to station all day filling your cardboard, labels, etc. Run out of tape? You hit a button that turns on a light and the runner comes a running to give you more. You are judged by the number of boxes you fill based on the size. Large boxes = 'x' amount of time, book boxes you have to do more. It is a fire-able offense to not make your numbers.

It's good for the consumer as you can get same day delivery - works great for groceries but don't expect your property taxes to drop or a bunch of high paying jobs to open up. It's not going to happen.

Exactly. This looks like an awesome learning tool for songs. But TabRider just disappeared. There's no source code on GitHub and I can't find anything that does the same thing. It sounds like a no-brainer to me that it would be a hit.

THIS IS WHAT I WANT! But I want it for GP7+. It's called TabRider and it looks like it's a dead app/project but it's exactly what I'm looking for. I'll keep looking but GP folks - Please make this happen!

https://www.youtube.com/watch?v=-P0rvFopFQg

I wasn't aware. I'll play around with that. Thanks for the heads up!!

I'll upvote you for sure. I've been playing since beta, logged in over a thousand hours and the devs have consistently ignored every issue thrown at them. They've tried PR scams where they've said "We know we've had a problem with communications but we're fixing that, expect xxx" and that's the last you hear of it.

The basis for the game is good. A triple A company shouldn't have to buy them out to make it playable. They made a Billion just in game sales in the first year and that's been their only motivation - not to improve the game but to make as few changes as possible that doesn't require developer help - only the designers who make costumes. From their perspective, who gives a shit about what the player base is asking for - even if it's reports of broken game issues.

I'm going to assume you're on a PC and not a console. If you're on a console, stop reading and go buy/build one like a big boy.

First, as a 53 year old man, yes, you do slow down a bit but you can make that up in higher quality equipment that the younger folks can't afford and use your experience to gain an advantage. PUBG is one of those games where a casual hour played just isn't enough and you might be confusing reaction time with deep learning of the game.

I'm no 'top of the leader board' guy but I've won my share of matches and I've lost a bunch to some pre-teen staying up past bedtime but it's been medically proven that gaming, especially FPS type games, heighten mental capacities and are very beneficial to your overall health so keep it up

Honestly, I've set aside PUBG for a while until the devs figure out what they're going to do. I probably won't jump back in until they upgrade their engine. Unreal 5 maybe out of reach but at least upgrade to the newest Unreal 4 engine. Until they do something at the engine layer (and get off of AWS servers IMO), they'll always have performance issues.

That brings me to proof in the pudding. I've switched to the game I've hated for a long time, at least for now - COD (Warzone is ok but I like the small map action so buy the full package). BattleField 5 was having problems of their own and there really wasn't anything else. I hate the cartoony action of Fortnight, Apex or Valorant. I still can't stand the 'unhuman-like' movements of COD but it keeps me interested and it will test your reaction time.

Not tooting my horn here but I generally finish first or second with the occasional last place while I'm trying to kit a new weapon but it shows that I can keep up with the kiddies and their X-Box crap.

I was playing in one of the COD Tournaments they have every now and then and I got paired up with a kid who couldn't be more than 10 or 11 years old. Every team we kicked out of the tourney, I had to tell them that they go beat by an old man with a pacemaker and a kid who couldn't even drive yet. The reactions were priceless.

Sorry for the long rant... Just wanted you to know there's more of your type out there and we're still kicking ass.

Yeah, sorry about that. I'll get to a supported layout and if I have any questions, I'll forward them. Thanks for the help.

Guess I assumed the PiPiggies build with ROMS would work (no, i'm not posting links to roms only sharing by RetroPie build I"m using).

I'll blow away this image and grab the authoritative build from RetroPie and match the ROMS.

https://www.ultimarc.com/ Gold Leaf Switches and IPAC Ultimate IO. Their documentation is junk but quality control boards and switches with RGB lighting.

Couple of big issues we deal with: Biggest thing: Since you're on-prem, you'll no longer have a master control plane taken care of automatically. So, make certain you have at least 3 Master nodes (and add one for ~ every 200 workers) on fast disk (SSD's), have and test ETCd backups/restores (critical), and make sure they are all on high speed networks (dedicated back end works best).

The problem with K8s is ETCd is that it's not the greatest replicated file system and if it's slow, the whole cluster will be impacted. If it's gone, you're DOA. No backups? Rebuild entire cluster.

DNS always seems to be an issue with on-prem k8s. KubeDNS, CoreDNS, both tend to have issues regardless of size of cluster and utilization. This is just an on-going issue. Worked with many paid K8s support groups to try an figure it out. No one has yet. Thinking it's something coded within Kubernetes that's messed up.

Fabric choice. Several to chose from and all are in various stages of stability. I'd probably go with Calico. They seem to be the most deployed and stable.

And, as others have stated, MetalLB and storage will need to be factored in.

Rancher is expensive and you end up with vendor lock-in issues.

What kind of time-frame are you looking at? Actually, it doesn't really matter. Bottom line... you can't buy DevOps. $100K? You'll blow through that in one FTE who can support your new environment and/or support costs.

My recommendation... Use Terraform to build push button deployments of your infrastructure to PCI specs in any cloud provider you chose, use Ansible to deploy and configure your apps to PCI compliance specs. Then you'll need some automation bit like Jenkins or Bamboo. That'll get you started.

BTW... Going the route I proposed will avoid vendor lock-in. Once you get into Heroku, you're pretty much locked in. They have you and moving from them at a later date will cost a lot more than when you started with them.

Expect this to take a 1 to 2 years to complete. This is an honest estimate not knowing a thing about how big or complicated your environments are but few companies can get it done any quicker unless you're a startup with zero investment in systems.

Finally, if you're looking at going the DevOps route, DevOps is a culture, not a technology so you need to invest in DevOps which means investing in people, skills and commitment in backing a cultural change in your organization.

Good luck. I'm in the market if you need help - But $100k isn't going to cover it :-)

I used to get shit all the time riding my Harley with a full face helmet and jacket. My response: Chicks don't dig brain damage and skin graphs.

We are using Azure today. They were/are really late to the K8s service. Up until a couple of months ago, they had problems with their Nginx load balancing. So, they're still having problems the other guys figured out long ago but because of "business relationships" we had to go with Azure.

Yeah, we do have autoscaling on. We have some CI jobs that will do several thousand curl commands and after a handful, it seems DNS just checks out. Even this week, I've had to restart coreDNS pods as it just goes into la la land.

I don't believe we've tried that. I'll have to look into it. Thanks for the hint!

DNS failures are still an issue going back to 1.09. I've tried everything - Upgrading k8s, going from KubeDNS to CoreDNS, dnsmasq, switching from bare metal K8s to azure and AWS, even tried host files on both host and inside pods. If there's a high amount of DNS calls, DNS will just fail with cannot resolve xxx messages. Our internal DNS servers run fine with high traffic testing.

Your article is fairly accurate. Technology is not DevOps and you can't buy DevOps. It's a culture shift. Startups have a luxury to start small and with a fresh culture. My company has over 500 developers in 40 different groups developing a single product. Implementing proper DevOps here has been a 2+ year process and we're still a ways away.

What I've seen is so many managers, VP's and CIO's read some article and think to themselves: "I'll just tell everyone we're going to do DevOps and if they don't, they're outta here."

IMO, management needs to organize resources, people, and money. Leave technology to the experts, support a "blameless" culture and support the culture change against those who fear change.

You have a company do this and DevOps would spread even faster than today.

I'm an Ansible fan rather than Chef but each gig is different. Learn GIT really well - not just the commands but tagging/branching best practices, etc. Python for sure, Bash for sure, Jenkins/Bamboo (Jenkins is the leader by far), AWS S3/Storage/Networking, Artifactory or some artifact management tool/process, RPM/Deb package management, and look for development methodologies. Understanding the development workflow will really help in defining devops pipelines.

I work on mostly on-prem hardware. I think understanding on-prem hardware helps you understand the virtual world much better/faster because you have an understanding of the underlying fundamentals of all things compute.

As far as DevOps on Bare Metal, thats mostly what I do. With the addition of a PXE service like MaaS or Cobbler, you still use all the tools you would in AWS. However, in cases like Kubernetes, you'll become a lot more intimate with it because Bare Metal K8s isn't just installing a service. There's Kubeadm and Kubespray (basically K8s via Ansible) but you'll need to understand network overlays, storage and physical networking as well as other hardware technologies.

By the time you get to AWS, you'll really appreciate all that AWS does for you but you'll know and understand a lot more than someone who just does AWS.

Oh, and by the way, the "saving money with AWS/Azure/GCP" is a crock of @#$%^. If you're small, like <50 servers, sure, it's less expensive than building a datacenter and stocking it with hardware. But if you're talking hundreds of servers, AWS/Azure/GCP can be a lot more expensive and less flexible. I'm all for virtualization and cloud based technologies, where they fit, but don't fool anyone in telling them it's way cheaper.

I gotta be honest... A large part of devops - or any IT position, is finding answers to questions. A simple Google search will present a large number of learning resources. The problem is that devops is a subject all its own so maybe the more appropriate question is, what is the most popular technologies to learn for devops. Then take the initiative to learn those things.

• AWS/Azure/GCP are all good (AWS being the top right now) but also know bare metal (this will help in the virtual world more than most people know). Storage, networking, etc.
• Then there's Jenkins/Bamboo or some other automation toolkit.
• Understand GIT - Get to know this well. Branching strategies, tagging, versioning, resolving conflicts.
• BASH and Python scripting at a minimum. This is the workhorse of devops.
• Docker/LXC, Dockerfiles, (I don't think K8s is a requirement but very good to know basic commands)
• Misc stuff: Know Linux pretty well, Artifact management (Artifactory, or tagging/branch management), Firewalld/iptables, Nginx, and general database knowledge
• Understand package management - RPM's, Debs, tar, etc.
• I'm going to add this in here as well. Understand development methodologies. How do 10 developers all work on separate pieces of a project and bring it all together in one distribution package - how about 200 developers? CD is all about combining separate artifacts into an installable package.

One additional thing... You don't have to be an expert in all of these. Just familiarization is enough to start. Like I said, a large part of devops is understanding a problem enough to search for an answer then implement that answer. A big one is the willingness to jump in and grow your skillset. I've been doing IT for ~30 years and I still take classes monthly so don't ever get comfortable with what you know.