u/SeniorIdiot

Microservice =/= docker container.

You can have one logical service subdivided into multiple processes that shares the same database schema.

Also, a shared database server is different from shared schema.

Because vendors have spend two decades commoditizing "CI/CD, DevOps" and convinced entire generations of engineers to think that CI/CD/DevOps are about tools.

Also agile specific: "Rolling rocks downhill" by Clarke Ching

Ja, med bra SDS+ borrar så kommer du igenom 20cm hårdbetong. Har kört 20mm borr genom 25cm hårdbetong från 70-talet med en borrhammare på 1000kr från Clas Ohlson.

Är det lättbetong ("lekablock" eller tegel) så räcker det med en vanlig borr med slag.

• 1, 10: outliers - drop
• even numbers: not "random" - drop
• 3, 9: too small/large - drop
• 5: in the middle, yuck - drop
• 7: perfection

Why are you using a self-hosted runner if just experimenting? Just curious...

A GitHub Pro/Team license costs $4 per month and you get 3000 minutes of actions.

Här har det stått ett 30-tal röda bussar hela sommaren.

https://maps.app.goo.gl/et9hwWBQfEkMEhgSA

Kontot är 2½ år gammalt och markerat som NSFW. 77 karma, 3 poster. Första för 5 timmar sedan av sexuell karaktär. Just den här typen av posts "namnge min katt" är klassisk karmafarming strategi.

Tror mycket skulle lösa sig med en lag att man måste gå en repetitionskurs varje gång man förnyar körkortet.

Och inte bara repetition av regler och nya regler, kanske också något mer interaktivt i form av "vad hände i den här situationen och vad borde de inblandade ha gjort istället?".

Borde också införa inkomstbaserade böter, men vem försöker jag lura - någon måste tänka på de stackars miljonärerna. 🤏

How much are you willing to spend on controls and enforcement?

1. Contract, legal (with audit).
2. On-prem license server with hardware dongle(s).
3. Phishing mails to the CEO/CTO and blackmail them.
4. Install keyloggers and audit daemons in the air-gaped network, send signed logs and heartbeats to encrypted on-prem box.
5. Become a dictator and have your secret police interrogate everyone at the company at random intervals - avoid windows.
6. Place a nuke in their server room with a dead-mans switch that has to be pressed once per week by you.

/s

For the past 40 days this account have been posting identical type of "questions" in loads of technical subreddits.

This is obviously for training LLMs.

Mörka linjer under naglarna kan vara tecken på hudcancer.

Ta ett foto i veckan med något som referens och jämför. Om de växer eller förökar sig så är det dermatolog som gäller. Du har inga tydliga mörka linjer under naglarna?

I så fall är det bara att blockera kortet och sen kontrollera köp på alla andra kort också. Skulle nog göra en reset på telefonen för om någon kommit åt din wallet så har du lite jobb framför dig. 🤔

Har du kollat ditt OpenAI konto vad du har köpt för tjänster? Kan du ha tryckt på "Add credits" när du har nått någon gräns?

NaT.

I'm sorry you had a rough day; double sorry that your manager "implied" that "manual testing is for losers".

First of all, I've commented multiple times in this (and r/softwaretesting) sub, about how "manual testing" is a self-deprecating wording. Having a human "executing a test script", as if we're machines, when a machine could do it with automated checks - that IS stupid. Having humans do actual product testing - that is incredible important work. Your manager sounds like he'd given up, or never understood what testing is about. 😕

But, one of the core issues we have in the software industry is the belief that if we just create a separate team and role that is "responsible for quality" magic will happen. It's often deeply entrenched in the organization and identity, in reporting structures and power-dynamics, and mostly acts like an alibi generator; where the rest of the team get to say "I'm done", while the people that have no authority over the work (testers), gets blamed.

A healthier model is that quality accountability is distributed according to authority.

• Product should own whether the thing is desirable, appropriate, coherent, brand-consistent, and worth shipping from a business (risk) perspective.
• Engineering should own whether the technical implementation is sound, maintainable, observable, operable, secure enough, and behaves as intended.
• Testing should provide information about risks, inconsistencies, unknowns, failures, edge cases, and gaps in understanding.
• Quality Assurance is a governance function and processes around all these things; not a department, team, role, or phase.

None of those groups should be able to say "quality is somebody else’s job", and none of them should be made accountable for things they lack the authority to change. Yet here we are.

Michael Bolton have been talking about this for almost two decades... maybe one day we will learn.
https://developsense.com/blog/2010/05/testers-get-out-of-the-quality-assurance-business
https://developsense.com/blog/2024/01/quality-assurance-and-testing
https://developsense.com/blog/2024/10/testing-is-not-quality-quality-is-not-testing

Testers are very much needed and quality always was everyone's responsibility.

The simple truth is that "QA" stopped meaning "Quality Assurance" decades ago and gradually became a job title for people who mostly perform testing. Once that happened, the original meaning of the words became detached from the work.

• Quality Assurance: preventive and systemic. “How do we establish confidence that our way of producing software produces acceptable results?” (governance process, accountability, product feedback)
• Quality Control: evaluative. “Does this particular artifact satisfy its acceptance criteria?” (checking, mostly automated, process feedback, objective)
• Software Testing: an investigative activity. “What can we learn about the behavior and properties of this software by exercising or analyzing it?” (risk, informative, subjective)

Don't forget about the LMAX Disruptor with further optimizations for latency.

Looks like he just reinvented distributed tracing and metrics aggregation, minus the parent/child correlation, the sampling strategies, and the ecosystem of backends built for exactly this. Look into OTel with tail-based sampling and spanmetrics connector instead of building this in-house.

:shrug:

Not much in this post makes any sense! Well, it's written by a marketeer at a software testing company ChatGPT so what did I really expect!? I'm sorry, but "testing houses" need to go the same way as leaded gasoline.

The only thing that makes sense is "Here are the releases we stopped, the customer-impacting issues we caught, and the risks we identified before they reached production". That was always the job - however the interpretation makes all the difference! "We" is the entire team of engineers, testers, UX and designers working towards a common goal and outcome.

The simple truth is that "QA" stopped meaning "Quality Assurance" decades ago and gradually became a job title for people who mostly perform testing. Once that happened, the original meaning of the words became detached from the work.

Deming, Crosby, and ISO 9000 all treat quality assurance as primarily a process and management responsibility, not an inspection role.

• Quality Assurance: preventive and systemic. “How do we establish confidence that our way of producing software produces acceptable results?” (governance process, accountability, product feedback)
• Quality Control: evaluative. “Does this particular artifact satisfy its acceptance criteria?” (checking, mostly automated, process feedback)
• Software Testing: an investigative activity. “What can we learn about the behavior and properties of this software by exercising or analyzing it?” (risk management, informative)

Hasty generalization + guilt by association + loaded language + category error + false equivalence.

Du lyckades med alla på en enda rad.

You are right - and wrong.

It was never about getting paid to do our hobby (writing code), it was always about communication, tradeoffs, decisions, understanding the business, and interactions. We have just gotten so used to being privileged, getting paid to do our hobby, that we are now panicking and feeling a loss of identity when reality hits.

Software engineering always was a social endeavour - embrace your promotion and look forward to the coming age of dark debt.

I know. They tried several times on me but it was so painful they aborted every time (I fainted the first time) and settled for cytology. Turned out I had T1HG CIS - so every scan, CT, MRI, etc missed it. Did two TURBT and then RC+RP.

Why would testers be gone if devs do a better job?

Only way that would be a conflict of interest is if the organizations culture and broken; where testers have been given accountability for "quality", but no authority over the work, and developers are measured by issues closed, PRs merged, etc.

You got it because you made it.