-
43 votes
-
JSHint: Watching the ship sink (A lesson on ambiguous licenses)
7 votes -
Seeking good programs for digitizing all our addresses
What's your preferred program for typing up lots and lots of addresses? My mum's got multiple address books and they'll have to be typed up eventually, a block at a time. I don't really want to go...
What's your preferred program for typing up lots and lots of addresses? My mum's got multiple address books and they'll have to be typed up eventually, a block at a time. I don't really want to go with the contacts function of Outlook/Hotmail/Live, because it requires signing in and the password could be misplaced. I also would like to use something that could ideally export the addresses to another Outlook/Hotmail/Live or Gmail account.
7 votes -
Mobilizon, a free-libre federated events and groups platform has launched v1.0
13 votes -
Meet the 24-year-old who’s tracking every broken McDonald’s ice-cream machine in the US
14 votes -
Oh! The things we had to do to debug software!
9 votes -
Five reasons NOT to grow your QA department
5 votes -
Principles for building developer products: A CTO’s perspective
4 votes -
The pros and cons of software crowdtesting
3 votes -
The badly thought-out use of Microsoft's Excel software was the reason nearly 16,000 coronavirus cases went unreported in England
28 votes -
Nvidia replaced video codecs with a neural network
18 votes -
Freetube rewrite with Newpipe-like local API released
7 votes -
Tell me about your early experiences with debugging and software QA
Are you an “old timer” in the computer industry? I’m writing a story about the things programmers (and QA people) had to do to test their software. It’s meant to be a nostalgic piece that’ll...
Are you an “old timer” in the computer industry? I’m writing a story about the things programmers (and QA people) had to do to test their software. It’s meant to be a nostalgic piece that’ll remind people about old methods — for good or ill.
For example, there was a point where the only way to insert a breakpoint in the code was to insert “printfs” that said “I got to this place in the code!” And all testing was manual testing. Nothing was automated. If you wanted a bug tracking system, you built your own.
So tell me your stories. Tell me what you had to do to test software, way back when, and compare it to today. What tools did you use -- or build? Is there anything you miss? Anything that makes you especially glad that the past is past?
C’mon, you know you wanted a “remember when”!
8 votes -
Negotiating the developer-to-tester ratio. Turns out that 3:1 is just the beginning
4 votes -
Druva introduces software as a service data protection for Kubernetes
4 votes -
People expect technology to suck because it actually sucks: so much of our usage involves dealing with a constant stream of minor annoyances
44 votes -
How open-source software transformed the business world
6 votes -
Eight ways to know that it’s time to hire a new QA tester
3 votes -
What sort of software do you want to see?
Devs make things they feel like making, or things they think the world needs. What kind of an app (web, desktop, or mobile) would you want to see? What is something you wanted or needed for a long...
Devs make things they feel like making, or things they think the world needs.
What kind of an app (web, desktop, or mobile) would you want to see? What is something you wanted or needed for a long time that simply isn't there, or there but so bad with X that you can't use it?
Alternatively, what is a common problem that could be solved with software but hasn't been yet, or at least not effectively?
Leaving this vague on purpose, to let Tilderinos express themselves.
28 votes -
Why do computers running Windows get progressively slower over time?
I promise this is a genuine question and not a Windows hit piece. Every Windows computer I've ever had has slowly gotten laggier over time until my impatience has forced me to reinstall the OS to...
I promise this is a genuine question and not a Windows hit piece.
Every Windows computer I've ever had has slowly gotten laggier over time until my impatience has forced me to reinstall the OS to get the speed boost that comes with a fresh copy. In the schools I've worked in, computer labs and carts full of Windows machines have slowly sunsetted, becoming wholly unusable over time. I think Chromebooks have taken over education in part because they have a snappiness to them that sticks around for a long time, unlike the decay demonstrated by Windows computers.
In my current job, I was issued a Windows computer and a Chromebook at the same time, when I was hired. The Chromebook is still chugging along just fine, but the once fresh and quick Windows computer is now ramping down. I know it's not because of startup or background programs latching on over time because I don't have admin rights and thus can't install anything! I'm not a power user either. I really only ever run a browser with minimal tabs, along with the very occasional instance of office software and/or PDF reader. That's it. And what used to be instant and quick is now like... trudging... through... sludge...
Is there some fundamental design flaw in Windows? Am I finding a pattern where none exists? Do I not have enough experience with other OSes to know that this is true for them too? I'd love someone's insight on this topic.
26 votes -
Gigapixel AI accidentally added Ryan Gosling’s face to this photo
5 votes -
Sometimes, developers find it hard to work with content creators, so here are some tips to help the collaboration along
4 votes -
Winamp in 2020 (Webamp Electron App)
13 votes -
Apple app review process updates
6 votes -
Estimating software testing time: a few useful guidelines
4 votes -
The Anti-Capitalist Software License has a goal of "contributing to a world beyond capitalism"
14 votes -
Why Johnny won't upgrade
12 votes -
Five rules for successful test automation
5 votes -
TietoEVRY, a software company from Finland, has developed a new font called Polite Type which uses machine learning to rewrite offensive language into more inclusive forms
10 votes -
Requiring a Facebook account for Oculus VR is bad for users, devs, and competition
17 votes -
The Eliza Effect
10 votes -
Five ways cloud-native application testing is different from testing on-premises software
4 votes -
Bitwarden review
11 votes -
What’s the difference between a good QA director and a great one? A comparison
4 votes -
Turning Lambda@Edge into a software platform
4 votes -
The rise and fall of Adobe Flash
10 votes -
Four lessons software teams can learn from rock bands
4 votes -
Google blew a ten-year lead
27 votes -
Oculus Go will no longer be sold, software maintained until 2022
8 votes -
How to design a Proof of Concept project to evaluate software
4 votes -
Retiring old service versions
3 votes -
Sexism in technology
11 votes -
Software bug in Bombardier airliner made planes turn the wrong way
6 votes -
How do you design a Proof of Concept project for a new dev/test tool?
Input wanted for an article. Let's say that your company is considering the purchase of an expensive new application to help in the company's software development. The demo looks great, and the...
Input wanted for an article.
Let's say that your company is considering the purchase of an expensive new application to help in the company's software development. The demo looks great, and the feature list makes it sound perfect for your needs. So your Management arranges for a proof of concept license to find out if the software is worth the hefty investment. The boss comes to you to ask you to be in charge of the PoC project.
I'm aiming to write an article to help developers, devops, and testers determine if a given vendor's application meets the company's needs. The only assumption I'm making is that the software is expensive; if it's cheap, the easy answer is, "Buy a copy for a small team and see what they think." And I'm thinking in terms of development software rather than enterprise tools (e.g. cloud-based backup) though I suspect many of the practices are similar.
Aside: Note that this project is beyond "Decide if we need such a thing." In this scenario, everyone agrees that purchasing a tool is a good idea, and they agree on the baseline requirements. The issue is whether this is the right software for the job.
So, how do you go about it? I'm sure that it's more than "Get a copy and poke at it randomly." How did (or would) you go about designing a PoC project? If you've been involved in such a project in the past (particularly if the purchase wasn't ideal), what advice could someone have given you to help you make a better choice? I want to create a useful guide that applies to any "enterprise-class" purchase.
For example: Do you recommend that the PoC period be based on time (N months) or workload (N transactions)? How do you decide who should be on the PoC team? What's involved in putting together a comprehensive list of requirements (e.g. integrates with OurFavoredDatabase, meets performance goals of X), creating a test suite that exercises what the software dev product does, and evaluating the results? ...and what am I not thinking of, that I should?
7 votes -
Munich is shifting back from Microsoft to open source
14 votes -
Employee monitoring software surges as companies send staff home
18 votes -
The mobile testing gotchas you need to know about
5 votes -
Gopass - The team password manager
7 votes -
It's called artificial intelligence—but what *is* intelligence?
4 votes -
The need for software testing: Neil Ferguson's unstable epidemiologic model
10 votes