-
7 votes
-
DIY Blu-Ray laser scanning microscope
3 votes -
About political messages on the Rust blog
8 votes -
How to approach and evaluate programming languages for a project
2 votes -
Rust takes a major step forward as Linux's second official language
19 votes -
Automatic pool cue vs. strangers
6 votes -
What I learned in two years of moving government forms online
9 votes -
Guido van Rossum, the Python language's founder, joins Microsoft
13 votes -
Developer Resume Review
I am currently a junior in college and in search of summer internship for next year. I am not seeing much response and starting to wonder if it is an issue with my resume. Is there any chance one...
I am currently a junior in college and in search of summer internship for next year. I am not seeing much response and starting to wonder if it is an issue with my resume. Is there any chance one of you would be willing to take a look at it? Open to any and all feedback.
Thank you for your time.
12 votes -
How to improve your debugging strategies
6 votes -
Oh! The things we had to do to debug software!
9 votes -
The pros and cons of software crowdtesting
3 votes -
Negotiating the developer-to-tester ratio. Turns out that 3:1 is just the beginning
4 votes -
C++20 approved, C++23 meetings and schedule update
11 votes -
Interview with extreme programming creator Kent Beck
4 votes -
Six ways to improve your debugging skills
5 votes -
Four lessons software teams can learn from rock bands
4 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 -
Quickref is an experimental search engine for developers
18 votes -
It's called artificial intelligence—but what *is* intelligence?
4 votes -
Michael Reeves builds a surgery robot
19 votes -
Not a 'math person'? You may be better at learning to code than you think
20 votes -
Five things QA testers wish programmers understood
6 votes -
"Herein, a collection of more or less recent, decidedly epic software disasters. May they spark conversation that helps your shop to avoid more of the same."
8 votes -
So you want to become a software QA professional?
6 votes -
The architect of modern algorithms
5 votes -
If PHP were British
25 votes -
Eleven great mechanical keyboards for coders — updated for 2019
9 votes -
Programming Sucks
25 votes -
Choosing the right coding summer camp for your kid: 9 questions to ask
3 votes -
Nine APIs for the geekiest of programmers
7 votes -
An error message in Windows 10 is a mistake from 1974
@foone🏳️⚧️: It is 2018 and this error message is a mistake from 1974.This limitation, which is still found in the very latest Windows 10, dates back to BEFORE STAR WARS. This bug is as old as Watergate. pic.twitter.com/pPbkZiE57t
32 votes -
Create-React-App 2 is live
8 votes -
The coders of Kentucky
7 votes -
The Bullshit Web
8 votes -
Hard-won lessons: Five years with Node.js
4 votes -
Sphero spin-off Misty Robotics releases new sensor packed robot dev kit programmable in JavaScript
3 votes -
GitLab Ultimate and Gold now free for education and open source
26 votes -
Chat with Rob Walling, founder of Drip, serial entrepreneur
5 votes -
What is the most sophisticated piece of software code every written?
34 votes -
Fully Automated Luxury Communism Newsletter
5 votes -
Man is charged with hacking West Point and government websites
6 votes