In other news today...
-
Zombie apocalypse in three, two, one....
Man hospitalized after being rescued from 6-foot hole in North Valley
On Thursday morning, emergency crews were called to the area of 47300 North 9th Avenue, north of the Valley.
-
@loopback0 said in In other news today...:
Apple Releases iOS 17.1.1 With Bug Fixes for BMW Wireless Charging and Weather Widget
Apple today released iOS 17.1.1 and iPadOS 17.1.1, minor updates to the iOS 17 and iPadOS 17 operating systems that first came out in September. iOS...
- In rare circumstances, Apple Pay and other NFC features may become unavailable on iPhone 15 models after wireless charging in certain cars
You're charging it wrong.
Does wireless charging cost extra or does it come with the seat heater subscription?
-
@topspin Yes
-
New report claims Amazon may ditch Android for future Fire TV and Echo Show devices
A new report claims that Amazon is working on a new Linux-based OS for future Fire TV and Echo Show devices, which means it may ditch the current Fire TV OS that's based on Google Android.
Oh great, a new ad infested OS.
-
Something that's never been seen before.
Presently, the transplanted eye is not communicating with the brain through the optic nerve.
To encourage healing of the connection between the donor and recipient optic nerves, surgeons harvested adult stem cells from the donor’s bone marrow and injected them into the optic nerve during the transplant, hoping they would replace damaged cells and protect the nerve.
I do hope he regains at least light sensitivity.
-
It Took Just 16 Months To Develop 'DLC' MW3
It took 16 months to develop MW3 - it was also confirmed that it WAS supposed to just be DLC for MW2. Read the full story here.
It took two weeks to do resident evil one and we still talk about it almost thirty years later.
-
@loopback0 said in In other news today...:
Apple today released iOS 17.1.1 and iPadOS 17.1.1, minor updates to the iOS 17 and iPadOS 17 operating systems that first came out in September. iOS...
- In rare circumstances, Apple Pay and other NFC features may become unavailable on iPhone 15 models after wireless charging in certain cars
You're charging it wrong.
Did they confuse the two meaning of the word charging? If so, shall the owners expect some legal trouble next time?
-
Want a handsomely paid job in tech? Here's what you do
At KubeCon, the need to bridge the skills gap was clearer than ever
Probably more money and less overtime in enterprise development.
cloud engineers make $132,060-$185,380; DevOps engineers $140,740-$210,800; and software developers $130,200-$186,930. That's not chicken feed.
That has to be silly valley money, either that or companies are pissing away money on people that seem to be universially terrible and are costing them more than their inhouse infrastructure.
Understand Core Cloud Concepts: Proficiency in the basics of cloud computing, including IaaS, PaaS, and SaaS service models, as well as public, private, and hybrid cloud architectures, is fundamental.
Experience with one or more Major Cloud Providers: Building expertise in services provided by hypercloud providers such as Amazon Web Services (AWS), Microsoft Azure, and Google Cloud Platform (GCP).
Master Containerization: Knowledge of containerization tools such as Docker and container orchestration with Kubernetes is crucial.
Learn Infrastructure as Code (IaC): Familiarity with IaC tools like Terraform and Ansible that enable the provisioning and management of infrastructure through code.
Cultivate DevOps Practices: Understanding the principles of Continuous Integration and Continuous Deployment (CI/CD) and experience with DevOps tools.
If your job description contains all that I wonder where you find time to sleep.
If you can show you're a master of say AWS and Identity and Access Management, it's not a matter of if you'll get a job, it's when.
I would be surprised if anyone working at AWS was a master of aws. Its be known for a while that half them don’t know what the rest of them are doing.
She said: "It's ever more essential to get everybody up to speed. 55 percent of respondents to our surveys have said cloud-native specific training and certification have helped them land a job." Unfortunately, it's easier to say "get a certification" than it is to do it.
55% of people can read job postings and jump on a bandwagon! I’m watching the fallout from this shit in motion. I’ll probably be charging through the nose in a decade to fix one of these messes.
-
@DogsB said in In other news today...:
If your job description contains all that I wonder where you find time to sleep.
All of that job description put me to sleep.
-
@DogsB if I would be doing all of that crap, I’d have no time left to do my actual job.
-
@DogsB said in In other news today...:
Understand Core Cloud Concepts: Proficiency in the basics of cloud computing, including IaaS, PaaS, and SaaS service models, as well as public, private, and hybrid cloud architectures, is fundamental.
Experience with one or more Major Cloud Providers: Building expertise in services provided by hypercloud providers such as Amazon Web Services (AWS), Microsoft Azure, and Google Cloud Platform (GCP).
Master Containerization: Knowledge of containerization tools such as Docker and container orchestration with Kubernetes is crucial.
Learn Infrastructure as Code (IaC): Familiarity with IaC tools like Terraform and Ansible that enable the provisioning and management of infrastructure through code.
Cultivate DevOps Practices: Understanding the principles of Continuous Integration and Continuous Deployment (CI/CD) and experience with DevOps tools.
If your job description contains all that I wonder where you find time to sleep.
My job description does contain all that (caveats below) and I can still let my warthog kneel most of the time. It's not really that hard. It's a buzzword-rich environment, but the concepts are not complicated and repeat a lot—IP networks still work like they always did, VMs still run the same operating systems, containers are just fancier chroots, and the platforms are also just the servers we've know for some time.
The main qualification needed are the willingness to dig through documentation and deal with shit, because the tools are poorly thought out and break often as they try to keep up with the constantly shifting targets—because you can't keep using older Azure when you just don't have time for upgrades.
Caveats:
-
As I said the other dread, terms like IaaS, PaaS and SaaS are just buzzwords with little practical usefulness. The thing you really should understand is that VMs still run the same operating systems we've used for decades, IP network principles didn't change either, containers are just fancier chroot, and the ‘platforms’ are just the application servers we've also used for a while that someone sets up for you.
-
Terraform is a good thing, except it's slow as molasses. Or rather like a bunch of snails in tugging war. With Ansible I was very disappointed, but that's a tool for classic servers, not cloud; you shouldn't be using that with clouds.
-
The other day, while idly browsing SE.SE, I learned what CI and CD originally mean, and I'm calling it a
, not a best practice. Because continuous integration means that changes are merged to master at least every day and continuous delivery means everything that passes test suite is pushed to production. So now you know why so much modern web apps suck donkey balls.We merge when a feature is done, however long that takes, and deploy when the QA and PO approves. Which means we use CI/CD tools, but it's not actually CI+CD.
-
-
@Bulb If the test suite were thorough, dare I suggest, complete and actually verified things, you should be able to merge and deploy frequently.
I remember one tech interview I had where the velocity of the team was measured in deployments to production per week and it was in the low 30s and the CTO wanted that to be 70+, ideally 100.
I remain convinced I dodged multiple bullets there, not least 'how the hell can you keep track of what's going on with a codebase when there is something moving to production every 30 minutes or less?'
-
@topspin said in In other news today...:
@DogsB if I would be doing all of that crap, I’d have no time left to do my actual job.
You'd have a lot of time for office chair fencing though. Because doing this crap always means that you start a task (docker build, terraform apply, helm install, build on a build server … all of them have the same problem), it takes two minutes to start, then runs for a couple more minutes and fails due to some stupid error. So you fix the error, do the git commit & git push & start that task again dance and wait another ten minutes for the next stupid error.
-
@Arantor said in In other news today...:
@Bulb If the test suite were thorough, dare I suggest, complete and actually verified things, you should be able to merge and deploy frequently.
You don't want to leave features on branches to dry, but how frequently makes sense depends on the project a lot. For the kind of projects I tend to see a comprehensive integration test suite might take the whole night.
I remember one tech interview I had where the velocity of the team was measured in deployments to production per week and it was in the low 30s and the CTO wanted that to be 70+, ideally 100.
I remain convinced I dodged multiple bullets there, not least 'how the hell can you keep track of what's going on with a codebase when there is something moving to production every 30 minutes or less?'
Yeah. Also the change requests must have been extremely trivial if they got, and done, 100 of them each week.
-
@Arantor said in In other news today...:
I remember one tech interview I had where the velocity of the team was measured in deployments to production per week and it was in the low 30s and the CTO wanted that to be 70+, ideally 100.
I remain convinced I dodged multiple bullets there, not least 'how the hell can you keep track of what's going on with a codebase when there is something moving to production every 30 minutes or less?'
JFC. Changes that often must be minor but it sounds like it's also a support nightmare.
-
@Arantor that sounds like break early, break often.
-
@Bulb said in In other news today...:
Yeah. Also the change requests must have been extremely trivial if they got, and done, 100 of them each week.
: <deploy>
: Fix spelling msitake <deploy>
: Fix speling mistake <deploy>
: Fx spelling mistake <deploy>
: Fix spelling mistake <deploy>
: Fix bug <deploy>
: Fix speling mistake in bug<deploy>See! I can push 100 changes!
-
@dcon We call them tyops around here.
-
@dcon this wasn't what the guy meant with 100 changes per week.
-
@Arantor I mean, we have some guy here who’s apparently a wizard with CPUs or something, who aims for like 6 commits an hour.
I’m not sure if that’s some MIB “looking for the best of the best of the best, sir” scenario and he only hires actual wizards us mere mortals can’t compete with, or if I have a very different idea of what goes into a commit.
-
@topspin said in In other news today...:
@Arantor I mean, we have some guy here who’s apparently a wizard with CPUs or something, who aims for like 6 commits an hour.
I’m not sure if that’s some MIB “looking for the best of the best of the best, sir” scenario and he only hires actual wizards us mere mortals can’t compete with, or if I have a very different idea of what goes into a commit.
Maybe it's the same as what we mere mortals would normally consider ctrl+S (yes, I save fairly often before even trying to compile)
-
@topspin Commits is one of those units of measurement that, by itself, doesn't mean a whole lot.
-
@jinpa said in In other news today...:
@topspin Commits is one of those units of measurement that, by itself, doesn't mean a whole lot.
Agreed. But you have to assume a commit contains something, or even better something meaningful. That alone sets an upper limit to the number of commits.
If I’m busy thinking for an hour or two, I’m not going to make 10 commits during that time.
-
For context, the thing I've been working on for the last two weeks might merit a total of 8 or 9 commits for that period.
It's also more comments than code because of the hellspawn of what it's doing.
-
@topspin said in In other news today...:
who aims for like 6 commits an hour.
# commit -m "Fixed a typo" # commit -m "Fixed a typo in last typo fix" # commit -m "Forgot to save before last commit" # commit -m "Changed function name" # commit -m "Damned autocarrot, typos everywhere" # commit -m "Commit all changes before going home"
-
-
@TimeBandit said in In other news today...:
# commit -m "Fixed a typo" # commit -m "Fixed a typo in last typo fix" # commit -m "Forgot to save before last commit" # commit -m "Changed function name" # commit -m "Damned autocarrot, typos everywhere" # commit -m "Commit all changes before going home"It would be amusing to feed the diff for each to a LLM and get it to generate the commit message.
-
@dcon said in In other news today...:
@topspin said in In other news today...:
@Arantor I mean, we have some guy here who’s apparently a wizard with CPUs or something, who aims for like 6 commits an hour.
I’m not sure if that’s some MIB “looking for the best of the best of the best, sir” scenario and he only hires actual wizards us mere mortals can’t compete with, or if I have a very different idea of what goes into a commit.
Maybe it's the same as what we mere mortals would normally consider ctrl+S (yes, I save fairly often before even trying to compile)
Yeah, I tend to use topic branches as multi file undo stacks before squashing them back. If they count as commits I could probably get north of 150 a week when I’m writing code.
-
@DogsB I've hit over 300 commits in a week. I was trying to debug the CI workflows at that pont; they were intermittently failing. I wouldn't describe that as my most productive time.
-
@dkf said in In other news today...:
@DogsB I've hit over 300 commits in a week. I was trying to debug the CI workflows at that pont; they were intermittently failing. I wouldn't describe that as my most productive time.
You poor dear.
I wonder how many could be clocked up with css hackery.
-
-
@dcon said in In other news today...:
@Bulb said in In other news today...:
Yeah. Also the change requests must have been extremely trivial if they got, and done, 100 of them each week.
: <deploy>
: Fix spelling msitake <deploy>
: Fix speling mistake <deploy>
: Fx spelling mistake <deploy>
: Fix spelling mistake <deploy>
: Fix bug <deploy>
: Fix speling mistake in bug<deploy>See! I can push 100 changes!
I was told by a friend who worked at Sun that something similar happened there when they were bought by Oracle. Their new overlords decreed that everybody doing maintenance must close at least 36 tickets a year (but they can still report bugs themselves…)
-
@Bulb Reminds me of a Dilbert (
to find it) in which PHB decided to pay a bonus for every bug fixed. People started planning expensive purchases, like yachts. Even Wally became very enthusiastic about working.
-
@HardwareGeek said in In other news today...:
@Bulb Reminds me of a Dilbert (
to find it) in which PHB decided to pay a bonus for every bug fixed. People started planning expensive purchases, like yachts. Even Wally became very enthusiastic about working.And there was a front page article about it too,
even before that dilbert, and I believe before the Oracle anecdote.
-
@HardwareGeek said in In other news today...:
@Bulb Reminds me of a Dilbert (
to find it) in which PHB decided to pay a bonus for every bug fixed. People started planning expensive purchases, like yachts. Even Wally became very enthusiastic about working.
-
@Bulb said in In other news today...:
And there was a front page article about it too, even before that dilbert
TDWTF front page wasn't around in 1995 though.
-
@DogsB said in In other news today...:
Watch: Bear steals family's takeaway from their porch
The brazen animal made off with the goods moments after it was delivered
People keep telling me they're harmless but they keep doing this.
I showed that before (
ing myself...):
-
@dkf said in In other news today...:
It would be amusing to feed the diff for each to a LLM and get it to generate the commit message.
Huh. People are apparently doing that with Copilot.
-
-
@Bulb said in In other news today...:
- As I said the other dread, terms like IaaS, PaaS and SaaS are just buzzwords with little practical usefulness.
I must disagree here - the
aaSpart is actually very important, because it changes who does what and who is paid for what. Which is very relevant and useful
!Of course, the first letter can be anything, really. Some popular examples are MaaS (aka "Banking") or FaaS (well, you can connect the dots here). And of course they can be combined, I am pretty sure some FaaS Orchestration Specialists also provide MaaS services on side (but my knowledge is limited to TV series, videogames and tabloid press).
- The other day, while idly browsing SE.SE, I learned what CI and CD originally mean, and I'm calling it a , not a best practice. Because continuous integration means that changes are merged to master at least every day and continuous delivery means everything that passes test suite is pushed to production. So now you know why so much modern web apps suck donkey balls.
I remember when the terms started to gain popularity (circa 2010) and CI definitely meant that all the branches are built and tested merged together, but not necessarily merged in master(quite the contrary, the rule always was "build and test, then merge").
-
@Kamil-Podlesak I blame the “we have to go faster” mentality that the profusion of Agile has produced, where we measure our “velocity” and seek to increase that regularly. Any metric that can be gamed will be.
-
@Kamil-Podlesak we CI. They’re always broken. We usually ignore them until we need a deploy.
@Arantor I worked with an tech lead who proposed we just create random tasks to bump up the points. He used to start arguments with other teams on the validity of their pointing. He also asked a business manager outright how they were supposed to do anything with the points when it was obvious everyone was making it up on the spot.
He was a legend.
-
@Kamil-Podlesak said in In other news today...:
the aaS part is actually very important, because it changes who does what and who is paid for what
Well, yes, it's a hosting service, and that has a bunch of implications, but it's not like services is anything new. And you need to evaluate the specific offer anyway, so the classification is basically useless.
@Kamil-Podlesak said in In other news today...:
@Bulb said in In other news today...:
- As I said the other dread, terms like IaaS, PaaS and SaaS are just buzzwords with little practical usefulness.
I must disagree here - the
aaSpart is actually very important, because it changes who does what and who is paid for what. Which is very relevant and useful !Of course, the first letter can be anything, really. Some popular examples are MaaS (aka "Banking") or FaaS (well, you can connect the dots here). And of course they can be combined, I am pretty sure some FaaS Orchestration Specialists also provide MaaS services on side (but my knowledge is limited to TV series, videogames and tabloid press).
I remember when the terms started to gain popularity (circa 2010) and CI definitely meant that all the branches are built and tested merged together, but not necessarily merged in master(quite the contrary, the rule always was "build and test, then merge").Yeah, I was just as surprised. I commented that merging things to the mainline after a day, and also deploying to production each day is kinda mutually exclusive, but apparently that's what the terms are actually supposed to mean according to some book or wherever they come from.
-
@Bulb said in In other news today...:
Well, yes, it's a hosting service, and that has a bunch of implications, but it's not like services is anything new. And you need to evaluate the specific offer anyway, so the classification is basically useless.
people were used to have a for life license for any software bought, it was needed to use a different name to make it clear you're renting it
-
@sockpuppet7 said in In other news today...:
people were used to have a for life license for any software bought
And even if you bought it that way, doesn't mean you can still install it on a new machine. I'm looking at you FileMaker! (their license servers for the old versions are gone - since it can't call home, you can't install.)
-
@sockpuppet7 said in In other news today...:
@Bulb said in In other news today...:
Well, yes, it's a hosting service, and that has a bunch of implications, but it's not like services is anything new. And you need to evaluate the specific offer anyway, so the classification is basically useless.
people were used to have a for life license for any software bought, it was needed to use a different name to make it clear you're renting it
That's for software, especially end-user software. But cloud is what used to be known as hosting, and that has always been a service.
-
@dcon said in In other news today...:
since it can't call home, you can't install
Not with that attitude 🏴☠️
-
@DogsB Why was that lead comparing points across teams? They mean nothing outside your team.
-
@Bulb said in In other news today...:
@Kamil-Podlesak said in In other news today...:
the aaS part is actually very important, because it changes who does what and who is paid for what
Well, yes, it's a hosting service, and that has a bunch of implications, but it's not like services is anything new. And you need to evaluate the specific offer anyway, so the classification is basically useless.
@Kamil-Podlesak said in In other news today...:
@Bulb said in In other news today...:
- As I said the other dread, terms like IaaS, PaaS and SaaS are just buzzwords with little practical usefulness.
I must disagree here - the
aaSpart is actually very important, because it changes who does what and who is paid for what. Which is very relevant and useful !Of course, the first letter can be anything, really. Some popular examples are MaaS (aka "Banking") or FaaS (well, you can connect the dots here). And of course they can be combined, I am pretty sure some FaaS Orchestration Specialists also provide MaaS services on side (but my knowledge is limited to TV series, videogames and tabloid press).
I remember when the terms started to gain popularity (circa 2010) and CI definitely meant that all the branches are built and tested merged together, but not necessarily merged in master(quite the contrary, the rule always was "build and test, then merge").Yeah, I was just as surprised. I commented that merging things to the mainline after a day, and also deploying to production each day is kinda mutually exclusive, but apparently that's what the terms are actually supposed to mean according to some book or wherever they come from.
Yeah, I've never heard of CI including merging.
-
@ObjectMike said in In other news today...:
@DogsB Why was that lead comparing points across teams? They mean nothing outside your team.
Can't compare epeen without slapping down your team's story points on the table.
