Back
WIP

WIP

#wip

A community of makers shipping together
Launched March 5, 2018
Load previous page…
Automatically zoom in your current location (based on IP-address) when you visit wip.co/makers/map so you can find nearby makers #wip
Fix wip.co/makers/map because I broke it a while ago #wip h/t @martinvandriel
Extract controller concern for getting user's geolocation #wip
Rename "Nomad List" to "Nomads" throughout the codebase and also accept nomads.com/@marc style URLs in addition to the old domain h/t @bjorndunkel #wip
Fix paginating applicants list #wip h/t @ericcosulea
Try composing todo with N shortcut to see if it correctly prevents double form submission #wip
Generate live burndown chart of applicants waiting for a decision (invited or "skipped") and see some progress as I actively started processing applicants myself with help of the new AI ranking where most qualified applicants are shown first and so it's way easier to invite people in batches #wip
Rescue exception when bot tries to sign up to applicant form, because we don't care that the request is malformed if it's a bot #wip
Fix caching of avatars and project logos #wip
Show Loreto how to use @wipbot #wip
Use active_job-performs everywhere #wip
Notice #wip is a lot faster after blocking crawlers from indexing the "similar todos" pages which create above-average database load
Increase number of newsfeed entries from 5 to 20 per page so you can scroll down further without require additional pageloads #wip
Ensure to use dry-initializer for all my View Components #wip
Remove stray console.log's across the codebase #wip
Invite more applicants, because now that we rank them with AI and some of the UX improvements I made it's much easier to find and invite qualified candidates #wip
Refactor the way applicants are invited which simplifies the code and prevents a bug that could happen when you opened multiple applicants in different browser tabs and tried to invite them #wip
Change how like buttons are rendered for when you've liked a todo. Todos are heavily cached so the "did you like it?"-state needs to be applied dynamically. Before, we would make an additional HTTP request for each like button to update it. But now, we use Turbo Streams to update the button in the same initial HTTP request. It reduces both the number of HTTP requests and database queries. #wip
Invite quite a few new applicants #wip
Fix bug when providing nil value to user and project auto-completion #wip
Home
Search
Messages
Notifications
More