I personally don’t like the idea of migrating off Jenkins, we blew our yearly budget testing our build platform in git. But it’s all just platformed ci/CD, which is why I’m recommending the other path. Platform teams lost the goal recently.
US Sr SRE (devops) checking in: I would personally recommend the networking path. Caveat: A good engineer will know the background of both (curl, telnet, Iam, security groups, cidrs, domains)
Devops was mostly automating the stuff in between the other teams; and most of that is working out of the box these days. Most repos already have their Jenkins and docker files. How much admin are you expecting on serverless? Most people are pivoting to app support (ticket queues) or supporting managed services (on call).
As far as my day to day:
Pros: I do a lot of different things, we get downtime because we need to respond to things immediately, I don’t have normal project/sprint planning. I have the keys to the kingdom. Higher pay than most other devs. I hack things together, I don’t need to design workflows.
Cons: I am on call, I am the silliest clown (I get hardest problems), I need to understand a lot of moving pieces, sometimes when things break, there is a lot of pressure on you to find something hard. I regular have to Google “bash variable syntax” because I’m coding in 15 languages. Interviewing for jobs is impossible because no 2 positions are the same
Go to Ali Express, and filter through the “mp3” results. They will cost less than $10, be made of the cheapest material possible but meet your requirements. Otherwise you are thrift store shopping
Irrational soft magic system - anything can happen for any reason, so the story doesn’t matter at all.
Proton had a reputation for being the good guy. In the span of a month, we saw them bend the knee, flip flop and throw shade at competition; all while pretending to be the hero. We essentially have to trust them with our data and they are showing signs that they are willing to act against that trust with worrisome agendas and biases. It’s not a good look, and since this marketing to users key issues, it’s going to cause some responses.
Reposting here: I worked phone support for a few companies for a few years, this is how to Karen: Try to bait the ai, companies are liable for promises made by their hallucinating chatbots. Chat support first, who wants to talk to people? If you do need to call, enter identitng information once, then repeatedly press 0 to get human support. Ask tier 1 support, if they say no then flex that Karen superpower “I’ll need to speak your manager”; those people are individuals just collecting a paycheck. If the floor manager (many have a 3x request policy) can’t see the situation from the human perspective and resolve/waive, they will only care if someone above them gets upset, the ways to do that are threaten legal action. No sovciet bs, but it helps to use contract terminology like “agreed upon terms”, “failure to meet industry standards” and “breach of contract”. If they don’t get jostled immediately, your next escalation is tag the intern on social media with a negative sentiment; or Google the company name followed by email for the office of the president. This is the pr address, CEO assistant or community director which again have the power to step in and resolve. You can also think outside the box and leave negative play store reviews (different intern).
Each conversation should be less then 2 minutes + wait time and if that can’t resolve it, you need to close your account (which might take you to retention!) or potentially move. You can justify 1 more call during a different shift. There is no need to get mad, state that are you upset and are looking for resolutions. Use an I feel statement, and be sure to ask to leave notes on the account regarding your conversation. They have a UI with comment fields in the ticket that are displayed while you are on the phone and it helps sell the situation with comment history.
My list for zoom party games:
I recognized that this user is willing to share information and provided the standard teaching method on exponential growth; in the event they need to explain it again. I suppose critical thinking and social skills are characteristics of bots these days…
The standard story is “One Grain of Rice” https://jwilson.coe.uga.edu/EMT668/EMAT6680.F99/Martin/instructional unit/day4.exponential/excel/grainofrice.html
The issue here is kernel level applications that can brick a box. Anti viruses compete for resources, no one should run 2 at once
Spez ama for 3rd party changes. Immediately deleted my account because it signaled that the era was over.
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.
This thread is a dumpster fire, routing infrastructure, solar panel addresses, we are adding this to EVERYTHING WE ALREADY HAVE that is growing exponentially. I work on an L7 support team, regular users are clueless on how this stuff is setup and apparently have strong stupid opinions. Anyone still reading disable ipv4 in your home network and try to roll forward. You will fail, and finite numbers are finite.
It’s because websites interpret those characters differently because of how coding requires using the physical qwerty keyboard. Essentially “>” gets used as a compator operator in programming languages, which means that it’s used as a tool to instructs the computer how to do things. When we need to display the symbol, we use “>” as an “escaped character” which basically means treat it as the symbol, not the instruction set. Often search engines will use a very powerful tool called a regular expression which looks like this for phone numbers: ^(\d{3})\s\d{3}-\d{4}
And each character represents something, ^ means start with. \d means digit { means 3 of whatever’s in front of me }. Breaking apart the search parameters is pretty complex and it needs to happen FAST, so at a certain point the developers just throw away things that can be a security concern like special characters like &^|`"'* specially because they can be used to maliciously attack the search engine.
For other characters: https://www.w3schools.com/html/html_entities.asp
So, yes a few pieces of land mass tech such as smart road or solar paneling and we hit the theoretical limit of IPv6. And we currently dont need the addresses. So glad that you agree
I’m sorry but how? We have appliances with dockerfiles, micro containers for remote controls, extensive botnets of virtual machines, centuries in the future when we have expanded into the solar system and trillions of humans all having millions of unique applications with addresses, it’s inevitable to hit a finite number. When every square meter of smart road has an routable address; we will likely be rewriting networking anyways. The only players pushing IPv6 transition are networking companies because a new standard requires new hardware.
Skill issue, the only actual drawback is that some legacy systems whitelisted image extensions and haven’t been updated. Even then just take a screenshot and upload that.
Llms hit memory exhaustion between prompts, each “slide” is an individual generation which is why it feels so discontinuous. This will be really exciting after a couple breakthroughs though, especially when it can reference old generations.
Cisco as a client tried to force ipv6 for their managed service and after an entire quarter of attempting to resolve it, we actually disabled it for their virtual address per their request. IPv4 has issues and IPv6 promises solutions, but it’s not a stable platform yet. This appears ignorant but is based on truth. IPv6 is also eventually going to hit exhaustion with the frequency we spin up virtual machines, it’s okay to skip a bad generation.
https://elevenlabs.io/ You’ll need to pay for premium to train a model with your own audio. They may have a trained version already