Nicholas Rougeux
Werner’s Nomenclature of Colours
A Website by Nicholas RougeuxA recreation of the original 1821 color guidebook with new cross references, photographic examples, and posters designed by Nicholas Rougeux.
Title Cities
An Artwork by Nicholas RougeuxA book’s title page contains more than its namesake—including its author, contributors, publisher, and release date, and. Antiquarian books are known for having lengthy titles, especially those of a scientific nature. These books’ frequently unassuming title pages are gateways to a wealth of knowledge and the focal point of this project.
Title pages of antique influential scientific books covering a variety of subjects were coded and reimagined as colorful cityscapes based solely on their words to illustrate the unique body of knowledge readers would find within.
Boxes were drawn around each word of a title page and color-coded by its first letter (words beginning with “A” are one color, “B” another, and so on). Each title page has its own palette. Those boxes were then upended and arranged to form an abstract cityscape while maintaining their original sizes relative to each other.
British & Exotic Mineralogy
A Website by Nicholas Rougeux
Software that nobody wants
Finding value is the result of enabling individual and group-level discovery attempts. It's not the result of everyone following one leader's gut.
What just happened is a new software product/feature was created that no customer wanted. This happens way too often. In fact, most hyper important software projects that must be done by date certain or else, have deep flaws that cause some variation of this phenomenon, flaws that include:
- Not wanted - Company specified a solution to a problem that customers don't actually have
- No Rarity - Company is pursuing an iKnockoff of existing products. The market already has two scaled competitors with working solutions, customers naturally spend budget on products that are already successful to avoid risk
- Incorrect Packaging - Customers need a website, but the company created an iOS app instead
- Incorrect Pricing - Customers need SaaS pricing, but the company created a shrink wrapped, on-premise solution with CapEx and maintenance agreements instead
The 'date scrum' anti-pattern
Date Scrum is an R&D pattern where developers are asked to estimate software project requirements upfront for the entirety of the project. After the project is green lighted and the budget is set based on the final estimates, the team then holds daily scrums to status and manage risk as they “iterate” the solution toward the release date. To some, this approach is described as doing Waterfall in sprints.
The fundamental problem with Date Scrum is that the team is de-focused from discovering the best solution. Instead they are heavily focused on delivering Something™ by the Date™. Engineers are problem solvers, and if the primary problem becomes delivering Something™ that will pass QA by the Date™, they will, with enough pressure, solve that exact problem.