HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
unclebob
fitnesse
Java2009–2026
unclebob / fitnesse

fitnesse

FitNesse -- The Acceptance Test Wiki

19Distinct people
20Mentions
0Explicit recommenders
2.2KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

FitNesse -- The Acceptance Test Wiki

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 9:01:12 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year20 dated mentions

Observed mentions: 2009-02-12 04:36:24 UTC to 2026-08-24 13:07:26 UTC.

0123452009-01-01 00:00:00 UTC to 2010-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments20092010-01-01 00:00:00 UTC to 2011-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2011-01-01 00:00:00 UTC to 2012-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2012-01-01 00:00:00 UTC to 2013-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-01-01 00:00:00 UTC to 2014-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2014-01-01 00:00:00 UTC to 2015-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2015-01-01 00:00:00 UTC to 2016-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments20172018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 5 mentions; 0 submissions, 5 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 4 mentions; 0 submissions, 4 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments. Incomplete calendar period.2026*

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20092009-01-01 00:00:00 UTC2010-01-01 00:00:00 UTC202
20102010-01-01 00:00:00 UTC2011-01-01 00:00:00 UTC000
20112011-01-01 00:00:00 UTC2012-01-01 00:00:00 UTC101
20122012-01-01 00:00:00 UTC2013-01-01 00:00:00 UTC000
20132013-01-01 00:00:00 UTC2014-01-01 00:00:00 UTC000
20142014-01-01 00:00:00 UTC2015-01-01 00:00:00 UTC101
20152015-01-01 00:00:00 UTC2016-01-01 00:00:00 UTC000
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC000
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC000
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC000
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC000
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC101
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC505
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC303
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC101
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC101
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC404
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC101

What Hacker News says

2 sources
"Check out his code: http://github.com/unclebob/fitnesse/tree/master It's really clean. " It is decent certainly, but nothing very ground breaking (imo) which is what "wizard" would imply. In no field of endeavor I know do we call people "wizards" for mere competence. The term is (imho) reserved for people who do ground breaking things / display astounding levels of competence/performance. Iow, someone isn't a "wizard" musician just because he knows his scales. You express this much better as "their code accomplished really new things, as opposed to finding better ways to do old things"). May be we just understand "wizard" differently, which is completely all right. "Norvig wrote some good books, but I never really got the sense of how he approaches a problem from them, although I did like the AI stuff quite a bit. " I learned quite a
Read the rest
bit from his python code, specifically some of the AIMA code, and also his spelling corrector (http://norvig.com/spell-correct.html) and sudoku solver (http://norvig.com/sudoku.html). How I learn from such examples is (1) I read the writeup to get a basic idea (2) I write my own version (in python for the spelling corrector example) and (3) see what differs between my version and the "wizard"'s. Specifically to answer your "I never got an idea of how he approaches a problem from them" Firstly, I wasn't speaking of Norvig's books but his code. But let us speak of books- Have you read Norvig's "Paradigms Of Artificial Intelligence Programming"?. The whole book is essentially Norvig programming "blow by blow" finding mistakes and reversing design decisions and so on. I found it very useful to get some insight about his thinking and programming style. Also Norvig does have some interesting thoughts on how to code in http://norvig.com/luv-slides.ps [postscript] where he talsk about how he iterates between an english description of an algorithm and (lisp) code till he gets it right. All the people I mentioned (PG, Norvig, Carmack, Torvalds) are top level programmers (vs being people who make living from selling - in one form or another - programming methodologies telling other people how to code)and have publicly available "wizard level" code to learn from. Robert Martin does write publicly available code - as does Kent Beck with Junit- so all due credit to them but most other agile "gurus" know jack all about coding at least as evidenced by their publicly available code. That said, I don't find Martin's code to be particularly inspiring as compared to the other people I mentioned. I find Martin's code to be competent but not "wizard level". I agree that this is largely a subjective judgment. YMMV. As I said in my earlier post, I largely agree with your original point.
In Jeff Atwood Finally Jumps the Shark
"I've noticed that most of these people have no "wizard level" code or achievements." I agree in general, but I was talking about Robert Martin in particular. Check out his code: http://github.com/unclebob/fitnesse/tree/master It's really clean. While the guys you mention have been very effective and productive programmers (maybe by having better ideas and writing more useful applications), their code accomplished really new things, as opposed to finding better ways to do old things. Norvig wrote some good books, but I never really got the sense of how he approaches a problem from them, although I did like the AI stuff quite a bit. Martin's "agile software development" is really good. I don't know why I benefit more from a little analysis on top of the code reading, but I think it helps me put a mental framework around stuff more quickly.
Read the rest
Anyway, you've got to love a guy who writes a book called "UML for Java Programmers" that simply trashes UML...
In Jeff Atwood Finally Jumps the Shark

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.