This is a parody of leetcode.com for designers. It's being developed live on Twitch.tv/zedashaw to demonstrate how to make a parody of a website.
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
Zed A. Shaw 7b6bcfc5cc Fixed the problem with the calendar, and font sizes in the header and the body. 1 year ago
admin Commit after Episode 2 of the show. First cuts of the landing page, problems list page, and starting off on the problem show. 1 year ago
api Fixed the problem with the calendar, and font sizes in the header and the body. 1 year ago
client Fixed the problem with the calendar, and font sizes in the header and the body. 1 year ago
commands Commit after Episode 2 of the show. First cuts of the landing page, problems list page, and starting off on the problem show. 1 year ago
emails Commit after Episode 2 of the show. First cuts of the landing page, problems list page, and starting off on the problem show. 1 year ago
lib Commit after Episode 2 of the show. First cuts of the landing page, problems list page, and starting off on the problem show. 1 year ago
migrations Commit after Episode 2 of the show. First cuts of the landing page, problems list page, and starting off on the problem show. 1 year ago
queues Commit after Episode 2 of the show. First cuts of the landing page, problems list page, and starting off on the problem show. 1 year ago
rendered Commit after Episode 2 of the show. First cuts of the landing page, problems list page, and starting off on the problem show. 1 year ago
scripts Commit after Episode 2 of the show. First cuts of the landing page, problems list page, and starting off on the problem show. 1 year ago
socket Commit after Episode 2 of the show. First cuts of the landing page, problems list page, and starting off on the problem show. 1 year ago
static Fix the font-size problem. 1 year ago
tests Commit after Episode 2 of the show. First cuts of the landing page, problems list page, and starting off on the problem show. 1 year ago
.eslintrc.json Commit after Episode 2 of the show. First cuts of the landing page, problems list page, and starting off on the problem show. 1 year ago
.gitignore Commit after Episode 2 of the show. First cuts of the landing page, problems list page, and starting off on the problem show. 1 year ago
LICENSE Commit after Episode 2 of the show. First cuts of the landing page, problems list page, and starting off on the problem show. 1 year ago
README.md Commit after Episode 2 of the show. First cuts of the landing page, problems list page, and starting off on the problem show. 1 year ago
bando.js Commit after Episode 2 of the show. First cuts of the landing page, problems list page, and starting off on the problem show. 1 year ago
bando.ps1 Commit after Episode 2 of the show. First cuts of the landing page, problems list page, and starting off on the problem show. 1 year ago
build.json Commit after Episode 2 of the show. First cuts of the landing page, problems list page, and starting off on the problem show. 1 year ago
build.prod.json Commit after Episode 2 of the show. First cuts of the landing page, problems list page, and starting off on the problem show. 1 year ago
knexfile.cjs Commit after Episode 2 of the show. First cuts of the landing page, problems list page, and starting off on the problem show. 1 year ago
nodemon.json Commit after Episode 2 of the show. First cuts of the landing page, problems list page, and starting off on the problem show. 1 year ago
package-lock.json Commit after Episode 2 of the show. First cuts of the landing page, problems list page, and starting off on the problem show. 1 year ago
package.json Commit after Episode 2 of the show. First cuts of the landing page, problems list page, and starting off on the problem show. 1 year ago

README.md

Introduction

Are you a better artist than a programmer?

This is a parody of leetcode I am creating that provides designers with the same bullshit "tests" that programmers have to go through to get a job. I'm building this website live on Twitch at zedashaw so if you want to join in the fun, throw out ideas for ridiculous "leetcode style" tests for designers, or heckle me, then come watch!

You're no Designer!

You're right, I'm a programmer. But if you're annoyed that people with absolutely no qualifications in testing your skills are somehow allowed to write tests that determine if you get a job then this website has proven its point.

The Rules

The rules for these tests are as follows:

  1. Every test I write for a designer has to be something I could do. If you don't know, I'm actually a fairly capable painter that can work in many different mediums and styles. If a lowly "programmer" can pull off these challenges but you can't, then no job for you.
  2. Tests other people write have to be in the same bullshit style as leetcode tests. They should be written by people who know next to nothing about testing designers, be fairly ambiguous, and have next to no validity in actually confirming someone can make a design.
  3. The site has to feature Comic Sans somewhere, because that'll piss off all the right people.

Tech Stack

All of the code will use my Bandolier Educational Web Framework so anybody--even a designer--can follow along and probably understand what's going on.