#sqa — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #sqa, aggregated by home.social.
-
- customer asks "Ein Bier bitte."
- the bar has not been initiatlized
- two customers walk into the bar in quick succession. Then four thousand customers walk into the bar all at once.
- a blind customer literally walks into the bar and bangs their knee; asks what beers are on tap because the color scheme for the menu has insufficient contrast -
- customer asks "Ein Bier bitte."
- the bar has not been initiatlized
- two customers walk into the bar in quick succession. Then four thousand customers walk into the bar all at once.
- a blind customer literally walks into the bar and bangs their knee; asks what beers are on tap because the color scheme for the menu has insufficient contrast -
- customer asks "Ein Bier bitte."
- the bar has not been initiatlized
- two customers walk into the bar in quick succession. Then four thousand customers walk into the bar all at once.
- a blind customer literally walks into the bar and bangs their knee; asks what beers are on tap because the color scheme for the menu has insufficient contrast -
- customer asks "Ein Bier bitte."
- the bar has not been initiatlized
- two customers walk into the bar in quick succession. Then four thousand customers walk into the bar all at once.
- a blind customer literally walks into the bar and bangs their knee; asks what beers are on tap because the color scheme for the menu has insufficient contrast -
I frequently see this pop up and I chuckle:
A #SQA person walks into a bar and orders:
* a pint of beer
* 2 pints of beer
* 0 pints of beer
* 999999999 pints of beer
* a lizard
* -1 pints of beer
* qwertyuip pints of beerThe first real customer walks into the bar and asks where the restrooom is. The bar bursts into flames and everyone dies.
---
What other "walks into a bar" #software #testcases are we missing? #qa #development -
I frequently see this pop up and I chuckle:
A #SQA person walks into a bar and orders:
* a pint of beer
* 2 pints of beer
* 0 pints of beer
* 999999999 pints of beer
* a lizard
* -1 pints of beer
* qwertyuip pints of beerThe first real customer walks into the bar and asks where the restrooom is. The bar bursts into flames and everyone dies.
---
What other "walks into a bar" #software #testcases are we missing? #qa #development -
I frequently see this pop up and I chuckle:
A #SQA person walks into a bar and orders:
* a pint of beer
* 2 pints of beer
* 0 pints of beer
* 999999999 pints of beer
* a lizard
* -1 pints of beer
* qwertyuip pints of beerThe first real customer walks into the bar and asks where the restrooom is. The bar bursts into flames and everyone dies.
---
What other "walks into a bar" #software #testcases are we missing? #qa #development -
I frequently see this pop up and I chuckle:
A #SQA person walks into a bar and orders:
* a pint of beer
* 2 pints of beer
* 0 pints of beer
* 999999999 pints of beer
* a lizard
* -1 pints of beer
* qwertyuip pints of beerThe first real customer walks into the bar and asks where the restrooom is. The bar bursts into flames and everyone dies.
---
What other "walks into a bar" #software #testcases are we missing? #qa #development -
If you’re considering AI-driven functional UI testing: -Start by stabilizing your environments and strategy -Don’t over-automate or blindly trust AI results -Avoid tools that can’t evolve with your application (and also there’s an ad) #SQA www.functionize.com/blog/you-wan...
So You Want to Implement AI-Dr... -
The New Software Testing Paradigm: From Scripts to Agents
Ah, so the AI-Everywhere Mantra comes to #SQA.
"Organizations still allocate 30-50% of their engineering budgets to QA but still suffer from fragile, script-heavy testing approaches. They are operating under a model that AI has already made obsolete."
https://www.functionize.com/blog/the-death-of-traditional-qa -
The New Software Testing Paradigm: From Scripts to Agents
Ah, so the AI-Everywhere Mantra comes to #SQA.
"Organizations still allocate 30-50% of their engineering budgets to QA but still suffer from fragile, script-heavy testing approaches. They are operating under a model that AI has already made obsolete."
https://www.functionize.com/blog/the-death-of-traditional-qa -
The New Software Testing Paradigm: From Scripts to Agents
Ah, so the AI-Everywhere Mantra comes to #SQA.
"Organizations still allocate 30-50% of their engineering budgets to QA but still suffer from fragile, script-heavy testing approaches. They are operating under a model that AI has already made obsolete."
https://www.functionize.com/blog/the-death-of-traditional-qa -
The New Software Testing Paradigm: From Scripts to Agents
Ah, so the AI-Everywhere Mantra comes to #SQA.
"Organizations still allocate 30-50% of their engineering budgets to QA but still suffer from fragile, script-heavy testing approaches. They are operating under a model that AI has already made obsolete."
https://www.functionize.com/blog/the-death-of-traditional-qa -
Aviation weather for Santa Ynez airport (USA) is “KIZA 031655Z AUTO 30009G14KT 10SM CLR 19/12 A3004 RMK AO2” : See what it means on https://www.bigorre.org/aero/meteo/kiza/en #santaynez #usa #santaynezairport #kiza #sqa #metar #aviation #aviationweather #avgeek #airport vl
-
Aviation weather for Santa Ynez airport (USA) is “KIZA 031655Z AUTO 30009G14KT 10SM CLR 19/12 A3004 RMK AO2” : See what it means on https://www.bigorre.org/aero/meteo/kiza/en #santaynez #usa #santaynezairport #kiza #sqa #metar #aviation #aviationweather #avgeek #airport vl
-
Aviation weather for Santa Ynez airport (USA) is “KIZA 031655Z AUTO 30009G14KT 10SM CLR 19/12 A3004 RMK AO2” : See what it means on https://www.bigorre.org/aero/meteo/kiza/en #santaynez #usa #santaynezairport #kiza #sqa #metar #aviation #aviationweather #avgeek #airport vl
-
Aviation weather for Santa Ynez airport (USA) is “KIZA 031655Z AUTO 30009G14KT 10SM CLR 19/12 A3004 RMK AO2” : See what it means on https://www.bigorre.org/aero/meteo/kiza/en #santaynez #usa #santaynezairport #kiza #sqa #metar #aviation #aviationweather #avgeek #airport vl
-
Aviation weather for Santa Ynez airport (USA) is “KIZA 031655Z AUTO 30009G14KT 10SM CLR 19/12 A3004 RMK AO2” : See what it means on https://www.bigorre.org/aero/meteo/kiza/en #santaynez #usa #santaynezairport #kiza #sqa #metar #aviation #aviationweather #avgeek #airport vii3
-
Aviation weather for Santa Ynez airport (USA) is “KIZA 031655Z AUTO 30009G14KT 10SM CLR 19/12 A3004 RMK AO2” : See what it means on https://www.bigorre.org/aero/meteo/kiza/en #santaynez #usa #santaynezairport #kiza #sqa #metar #aviation #aviationweather #avgeek #airport vii3
-
Aviation weather for Santa Ynez airport (USA) is “KIZA 031655Z AUTO 30009G14KT 10SM CLR 19/12 A3004 RMK AO2” : See what it means on https://www.bigorre.org/aero/meteo/kiza/en #santaynez #usa #santaynezairport #kiza #sqa #metar #aviation #aviationweather #avgeek #airport vii3
-
Aviation weather for Santa Ynez airport (USA) is “KIZA 031655Z AUTO 30009G14KT 10SM CLR 19/12 A3004 RMK AO2” : See what it means on https://www.bigorre.org/aero/meteo/kiza/en #santaynez #usa #santaynezairport #kiza #sqa #metar #aviation #aviationweather #avgeek #airport vii3
-
Aviation weather for Santa Ynez airport (USA) is “KIZA 301635Z AUTO 00000KT 10SM CLR 20/15 A2998 RMK AO2” : See what it means on https://www.bigorre.org/aero/meteo/kiza/en #santaynez #usa #santaynezairport #kiza #sqa #metar #aviation #aviationweather #avgeek #airport vl
-
Aviation weather for Santa Ynez airport (USA) is “KIZA 301635Z AUTO 00000KT 10SM CLR 20/15 A2998 RMK AO2” : See what it means on https://www.bigorre.org/aero/meteo/kiza/en #santaynez #usa #santaynezairport #kiza #sqa #metar #aviation #aviationweather #avgeek #airport vl
-
Aviation weather for Santa Ynez airport (USA) is “KIZA 301635Z AUTO 00000KT 10SM CLR 20/15 A2998 RMK AO2” : See what it means on https://www.bigorre.org/aero/meteo/kiza/en #santaynez #usa #santaynezairport #kiza #sqa #metar #aviation #aviationweather #avgeek #airport vl
-
Aviation weather for Santa Ynez airport (USA) is “KIZA 301635Z AUTO 00000KT 10SM CLR 20/15 A2998 RMK AO2” : See what it means on https://www.bigorre.org/aero/meteo/kiza/en #santaynez #usa #santaynezairport #kiza #sqa #metar #aviation #aviationweather #avgeek #airport vl
-
Making the jump from development → software testing.
It’s kinda tough at times, but also exciting to learn a new mindset.
I’ve even written a few articles on SQA automation to share what I’m learning along the way.Check it out and do follow me : https://medium.com/@safuraja7
If you’ve made a similar transition, how was it for you? 💭
#SQA #Testing #Automation #LearningInPublic -
Call For Industry Expertise: SQA And Skills Development Scotland to Develop New HNC in Esports
Skills Development Scotland (SDS) and the Scottish Qualifications Authority (SQA) have announced that they are developing a new HNC qualification in Esports and are seeking support from sector experts to help shape its creation.
This is a significant and welcome development for the rapidly growing esports ecosystem in Scotland. The creation of a formal Higher National Certificate will provide a clear and credible pathway for students looking to build a career in the competitive gaming sector, covering the wide range of skills required beyond playing, to include event management, broadcasting, coaching, business and community development, and more.
For any new qualification to be successful and relevant, it must be developed in close collaboration with the sector it aims to serve. A robust consultation process, informed by the real-world experience of players and professionals working in the field, is essential to ensure that the course content is fit for purpose and meets the needs of employers.
This is a vital opportunity for the Scottish esports community to lend its expertise and help build a qualification that will nurture the next generation of talent. By validating the course content, industry professionals can ensure that future graduates enter the workforce with the practical skills and knowledge required to succeed.
The Scottish Games Network strongly encourages all individuals and organisations involved in the Scottish esports scene to get involved in this important process.
Anyone interested in contributing their expertise to help validate the new HNC in Esports should get in touch directly with the key contact at the SQA.
Contact: Bobby Elliott
Email: [email protected]
-
Normally with tech issues I think aw, poor devops, but today I think come ON you bastards. #sqa #blank_results
-
Normally with tech issues I think aw, poor devops, but today I think come ON you bastards. #sqa #blank_results
-
Normally with tech issues I think aw, poor devops, but today I think come ON you bastards. #sqa #blank_results
-
Normally with tech issues I think aw, poor devops, but today I think come ON you bastards. #sqa #blank_results
-
There’s one thing that consistently showed up in my work as a software engineer over the decades. Spaghetti.
Spaghetti code is easier to write than maintain, and in doing software archaeology (yes, it’s a thing), I’ve encountered numerous reasons for it. Requirements creep is one of the largest reasons.
In fact, the first real software archaeology I did was explained, proudly, as being a product of someone walking in and telling the developer, “Wouldn’t it be nice if…”. Of course, nobody wrote anything down, and by the time I got to it the software was 25 years old and didn’t even have a brochure. People were still walking in and saying, “Wouldn’t it be nice if…”. Meanwhile, the company was required to follow standard software processes because it was required for contracts.
So I learned, from good teachers and a few bad ones, about Software Configuration Management, Software Quality Assurance, and Software Testing. There were reasons we did things a certain way. Our project configuration management contained everything needed to rewrite the software from scratch, including every single tool. I’d actually done a backup of a development pc after writing down the hardware specifications of the system and handed that in because quality assurance had to be able to take the same stuff and rebuild the same software so that it could be tested.
From scratch. And it had to pass the same tests. From scratch.
What I saw in other companies after that was never at that level, and on the surface it seemed ridiculous. However, any software engineer worth their weight in skittles has been screwed over by a platform changing underneath the code. Windows was infamous for it, though I did encounter it in an Apple shop as well. Your code hasn’t changed, but some update suddenly had you in the middle of bug city without even a flip flop. Microsoft has been notorious about that, with their version back in the day called DLL Hell. It’s just their (old) version of dependency hell.
I never had the problem with *nix systems, though when open source became popular and everyone started using that in their code, *nix systems started to get it too. People blamed the open source, but it was really 2 things that caused the problem.
(1) Bad Configuration Management (if it even existed!) and
(2) Taking the open source project for granted.Open Source projects that are done voluntarily are completely outside the control of a company, but having an open dialog and even sending some money for pizzas and beer can avoid issues. Even with all of that, volunteers are fickle, so having in house expertise on projects becomes as important as how important the projects are to a company’s software. A company doesn’t really know this, though, when they don’t have software configuration management for their projects – so you end up with spaghetti projects, or as I call it, “Spaghetti Configuration Management”.
Toss in the developers that are copying and pasting from Stack Overflow, or now GPT, dash in employee turnover, where expertise is lost, and you get software entropy. Talking about software entropy causes the eyes of pointy haired bosses to roll to the back of their heads, so instead we talk about technical debt, because one thing businesses understand is debt.
Over the years, companies I worked for were at various stages of technical debt. It’s a real thing, and the startups that survived long enough to get to the point of technical debt were the worst because of the culture shift needed: Documenting things, tracking things, and making sure that the knowledge stayed within the company. I can say with good conscience that I left every company better off than when I left it, sometimes because of the company, sometimes despite the company.
So we get to the article, “Hidden Tech Debt: The Importance Of Better Updates For Commercial Software“, which I came across through the author on Mastodon. It tackles the one thing I didn’t write about here: commercial software dependencies and lack of accountability in that, which is a bigger problem than we might think.
https://knowprose.com/2024/04/20/spaghetti-source-spaghetti-dependencies/
#dependencyHell #SCM #softwareArchaeology #softwareEngineering #softwareEntropy #softwareRot #spaghettiCode #SQA #technicalDebt #Technology
-
There’s one thing that consistently showed up in my work as a software engineer over the decades. Spaghetti.
Spaghetti code is easier to write than maintain, and in doing software archaeology (yes, it’s a thing), I’ve encountered numerous reasons for it. Requirements creep is one of the largest reasons.
In fact, the first real software archaeology I did was explained, proudly, as being a product of someone walking in and telling the developer, “Wouldn’t it be nice if…”. Of course, nobody wrote anything down, and by the time I got to it the software was 25 years old and didn’t even have a brochure. People were still walking in and saying, “Wouldn’t it be nice if…”. Meanwhile, the company was required to follow standard software processes because it was required for contracts.
So I learned, from good teachers and a few bad ones, about Software Configuration Management, Software Quality Assurance, and Software Testing. There were reasons we did things a certain way. Our project configuration management contained everything needed to rewrite the software from scratch, including every single tool. I’d actually done a backup of a development pc after writing down the hardware specifications of the system and handed that in because quality assurance had to be able to take the same stuff and rebuild the same software so that it could be tested.
From scratch. And it had to pass the same tests. From scratch.
What I saw in other companies after that was never at that level, and on the surface it seemed ridiculous. However, any software engineer worth their weight in skittles has been screwed over by a platform changing underneath the code. Windows was infamous for it, though I did encounter it in an Apple shop as well. Your code hasn’t changed, but some update suddenly had you in the middle of bug city without even a flip flop. Microsoft has been notorious about that, with their version back in the day called DLL Hell. It’s just their (old) version of dependency hell.
I never had the problem with *nix systems, though when open source became popular and everyone started using that in their code, *nix systems started to get it too. People blamed the open source, but it was really 2 things that caused the problem.
(1) Bad Configuration Management (if it even existed!) and
(2) Taking the open source project for granted.Open Source projects that are done voluntarily are completely outside the control of a company, but having an open dialog and even sending some money for pizzas and beer can avoid issues. Even with all of that, volunteers are fickle, so having in house expertise on projects becomes as important as how important the projects are to a company’s software. A company doesn’t really know this, though, when they don’t have software configuration management for their projects – so you end up with spaghetti projects, or as I call it, “Spaghetti Configuration Management”.
Toss in the developers that are copying and pasting from Stack Overflow, or now GPT, dash in employee turnover, where expertise is lost, and you get software entropy. Talking about software entropy causes the eyes of pointy haired bosses to roll to the back of their heads, so instead we talk about technical debt, because one thing businesses understand is debt.
Over the years, companies I worked for were at various stages of technical debt. It’s a real thing, and the startups that survived long enough to get to the point of technical debt were the worst because of the culture shift needed: Documenting things, tracking things, and making sure that the knowledge stayed within the company. I can say with good conscience that I left every company better off than when I left it, sometimes because of the company, sometimes despite the company.
So we get to the article, “Hidden Tech Debt: The Importance Of Better Updates For Commercial Software“, which I came across through the author on Mastodon. It tackles the one thing I didn’t write about here: commercial software dependencies and lack of accountability in that, which is a bigger problem than we might think.
https://knowprose.com/2024/04/20/spaghetti-source-spaghetti-dependencies/
#dependencyHell #SCM #softwareArchaeology #softwareEngineering #softwareEntropy #softwareRot #spaghettiCode #SQA #technicalDebt #Technology
-
There’s one thing that consistently showed up in my work as a software engineer over the decades. Spaghetti.
Spaghetti code is easier to write than maintain, and in doing software archaeology (yes, it’s a thing), I’ve encountered numerous reasons for it. Requirements creep is one of the largest reasons.
In fact, the first real software archaeology I did was explained, proudly, as being a product of someone walking in and telling the developer, “Wouldn’t it be nice if…”. Of course, nobody wrote anything down, and by the time I got to it the software was 25 years old and didn’t even have a brochure. People were still walking in and saying, “Wouldn’t it be nice if…”. Meanwhile, the company was required to follow standard software processes because it was required for contracts.
So I learned, from good teachers and a few bad ones, about Software Configuration Management, Software Quality Assurance, and Software Testing. There were reasons we did things a certain way. Our project configuration management contained everything needed to rewrite the software from scratch, including every single tool. I’d actually done a backup of a development pc after writing down the hardware specifications of the system and handed that in because quality assurance had to be able to take the same stuff and rebuild the same software so that it could be tested.
From scratch. And it had to pass the same tests. From scratch.
What I saw in other companies after that was never at that level, and on the surface it seemed ridiculous. However, any software engineer worth their weight in skittles has been screwed over by a platform changing underneath the code. Windows was infamous for it, though I did encounter it in an Apple shop as well. Your code hasn’t changed, but some update suddenly had you in the middle of bug city without even a flip flop. Microsoft has been notorious about that, with their version back in the day called DLL Hell. It’s just their (old) version of dependency hell.
I never had the problem with *nix systems, though when open source became popular and everyone started using that in their code, *nix systems started to get it too. People blamed the open source, but it was really 2 things that caused the problem.
(1) Bad Configuration Management (if it even existed!) and
(2) Taking the open source project for granted.Open Source projects that are done voluntarily are completely outside the control of a company, but having an open dialog and even sending some money for pizzas and beer can avoid issues. Even with all of that, volunteers are fickle, so having in house expertise on projects becomes as important as how important the projects are to a company’s software. A company doesn’t really know this, though, when they don’t have software configuration management for their projects – so you end up with spaghetti projects, or as I call it, “Spaghetti Configuration Management”.
Toss in the developers that are copying and pasting from Stack Overflow, or now GPT, dash in employee turnover, where expertise is lost, and you get software entropy. Talking about software entropy causes the eyes of pointy haired bosses to roll to the back of their heads, so instead we talk about technical debt, because one thing businesses understand is debt.
Over the years, companies I worked for were at various stages of technical debt. It’s a real thing, and the startups that survived long enough to get to the point of technical debt were the worst because of the culture shift needed: Documenting things, tracking things, and making sure that the knowledge stayed within the company. I can say with good conscience that I left every company better off than when I left it, sometimes because of the company, sometimes despite the company.
So we get to the article, “Hidden Tech Debt: The Importance Of Better Updates For Commercial Software“, which I came across through the author on Mastodon. It tackles the one thing I didn’t write about here: commercial software dependencies and lack of accountability in that, which is a bigger problem than we might think.
https://knowprose.com/2024/04/20/spaghetti-source-spaghetti-dependencies/
#dependencyHell #SCM #softwareArchaeology #softwareEngineering #softwareEntropy #softwareRot #spaghettiCode #SQA #technicalDebt #Technology
-
There’s one thing that consistently showed up in my work as a software engineer over the decades. Spaghetti.
Spaghetti code is easier to write than maintain, and in doing software archaeology (yes, it’s a thing), I’ve encountered numerous reasons for it. Requirements creep is one of the largest reasons.
In fact, the first real software archaeology I did was explained, proudly, as being a product of someone walking in and telling the developer, “Wouldn’t it be nice if…”. Of course, nobody wrote anything down, and by the time I got to it the software was 25 years old and didn’t even have a brochure. People were still walking in and saying, “Wouldn’t it be nice if…”. Meanwhile, the company was required to follow standard software processes because it was required for contracts.
So I learned, from good teachers and a few bad ones, about Software Configuration Management, Software Quality Assurance, and Software Testing. There were reasons we did things a certain way. Our project configuration management contained everything needed to rewrite the software from scratch, including every single tool. I’d actually done a backup of a development pc after writing down the hardware specifications of the system and handed that in because quality assurance had to be able to take the same stuff and rebuild the same software so that it could be tested.
From scratch. And it had to pass the same tests. From scratch.
What I saw in other companies after that was never at that level, and on the surface it seemed ridiculous. However, any software engineer worth their weight in skittles has been screwed over by a platform changing underneath the code. Windows was infamous for it, though I did encounter it in an Apple shop as well. Your code hasn’t changed, but some update suddenly had you in the middle of bug city without even a flip flop. Microsoft has been notorious about that, with their version back in the day called DLL Hell. It’s just their (old) version of dependency hell.
I never had the problem with *nix systems, though when open source became popular and everyone started using that in their code, *nix systems started to get it too. People blamed the open source, but it was really 2 things that caused the problem.
(1) Bad Configuration Management (if it even existed!) and
(2) Taking the open source project for granted.Open Source projects that are done voluntarily are completely outside the control of a company, but having an open dialog and even sending some money for pizzas and beer can avoid issues. Even with all of that, volunteers are fickle, so having in house expertise on projects becomes as important as how important the projects are to a company’s software. A company doesn’t really know this, though, when they don’t have software configuration management for their projects – so you end up with spaghetti projects, or as I call it, “Spaghetti Configuration Management”.
Toss in the developers that are copying and pasting from Stack Overflow, or now GPT, dash in employee turnover, where expertise is lost, and you get software entropy. Talking about software entropy causes the eyes of pointy haired bosses to roll to the back of their heads, so instead we talk about technical debt, because one thing businesses understand is debt.
Over the years, companies I worked for were at various stages of technical debt. It’s a real thing, and the startups that survived long enough to get to the point of technical debt were the worst because of the culture shift needed: Documenting things, tracking things, and making sure that the knowledge stayed within the company. I can say with good conscience that I left every company better off than when I left it, sometimes because of the company, sometimes despite the company.
So we get to the article, “Hidden Tech Debt: The Importance Of Better Updates For Commercial Software“, which I came across through the author on Mastodon. It tackles the one thing I didn’t write about here: commercial software dependencies and lack of accountability in that, which is a bigger problem than we might think.
https://knowprose.com/2024/04/20/spaghetti-source-spaghetti-dependencies/
#dependencyHell #SCM #softwareArchaeology #softwareEngineering #softwareEntropy #softwareRot #spaghettiCode #SQA #technicalDebt #Technology
-
To all Tech Founder out there active on Twitter
You can’t build your software fast if your developers are the one who test your product.
Let them focus on Development and at least Unit Testing.
--
Let us test your Software -> @weQAsoftware
-
To all Tech Founder out there active on Twitter
You can’t build your software fast if your developers are the one who test your product.
Let them focus on Development and at least Unit Testing.
--
Let us test your Software -> @weQAsoftware
-
So chuffed. Got my first formal education certificate in a few decades.
I'm certified noo😜
Thank you yet again to all the staff at #CodeClan who went above and beyond the call of duty teaching and supporting students especially after the liquidation and transfer to #CodeBase
#DataScience #SQA -
So chuffed. Got my first formal education certificate in a few decades.
I'm certified noo😜
Thank you yet again to all the staff at #CodeClan who went above and beyond the call of duty teaching and supporting students especially after the liquidation and transfer to #CodeBase
#DataScience #SQA -
So chuffed. Got my first formal education certificate in a few decades.
I'm certified noo😜
Thank you yet again to all the staff at #CodeClan who went above and beyond the call of duty teaching and supporting students especially after the liquidation and transfer to #CodeBase
#DataScience #SQA -
So chuffed. Got my first formal education certificate in a few decades.
I'm certified noo😜
Thank you yet again to all the staff at #CodeClan who went above and beyond the call of duty teaching and supporting students especially after the liquidation and transfer to #CodeBase
#DataScience #SQA -
SQA exams: Schools blamed for high number of unsuccessful appeals | Tes
Of course, the #SQA could never be to blame for anything!! https://www.tes.com/magazine/analysis/secondary/sqa-exam-appeals-fail-schools-blamed?utm_campaign=1476579_20230915%20The%20Week%20In%20Scotland&utm_medium=email&utm_source=dotdigital&utm_content=1476579_20230915%20The%20Week%20In%20Scotland&dm_i=5NNY,VNC3,KX4MN,3W09N,1
-
SQA exams: Schools blamed for high number of unsuccessful appeals | Tes
Of course, the #SQA could never be to blame for anything!! https://www.tes.com/magazine/analysis/secondary/sqa-exam-appeals-fail-schools-blamed?utm_campaign=1476579_20230915%20The%20Week%20In%20Scotland&utm_medium=email&utm_source=dotdigital&utm_content=1476579_20230915%20The%20Week%20In%20Scotland&dm_i=5NNY,VNC3,KX4MN,3W09N,1
-
SQA exams: Schools blamed for high number of unsuccessful appeals | Tes
Of course, the #SQA could never be to blame for anything!! https://www.tes.com/magazine/analysis/secondary/sqa-exam-appeals-fail-schools-blamed?utm_campaign=1476579_20230915%20The%20Week%20In%20Scotland&utm_medium=email&utm_source=dotdigital&utm_content=1476579_20230915%20The%20Week%20In%20Scotland&dm_i=5NNY,VNC3,KX4MN,3W09N,1
-
You know you're old when...a course asks for your #SQA Scottish Candidate Number and ...er...your exams date back to the #ScottishExaminationBoard #Antediluvian 🎓😂
-
You know you're old when...a course asks for your #SQA Scottish Candidate Number and ...er...your exams date back to the #ScottishExaminationBoard #Antediluvian 🎓😂
-
You know you're old when...a course asks for your #SQA Scottish Candidate Number and ...er...your exams date back to the #ScottishExaminationBoard #Antediluvian 🎓😂
-
You know you're old when...a course asks for your #SQA Scottish Candidate Number and ...er...your exams date back to the #ScottishExaminationBoard #Antediluvian 🎓😂
-
Passing unit tests is good but not sufficient. You actually have to look at the tests to see if they demonstrate a requirement is met. What do the tests show and are the tests even adequate? #CodeQualification #SQA
-
Passing unit tests is good but not sufficient. You actually have to look at the tests to see if they demonstrate a requirement is met. What do the tests show and are the tests even adequate? #CodeQualification #SQA