24 Hours (daringfireball.net)

You may have heard that Delicious stops (or not?). A person on Twitter suggested that a group of engineers should gather on weekends and build a Delicious clone. In anticipation of this group of mystery people sitting and in doing so, I thought that I would like to make a quick todo list for them.

System account - you will need to adopt the standard model that are typical of a web application: accounts.Register hold and installing an SSL cert to appease the security database-oriented. Also: where you host it? What database? MySQL? Good. InnoDB? If you are deploying with another engineer, the typical conversation 30 minutes on the deployment of databases have all two hours.Decide on the ORM or simply write some lightweight classes that are tedious shit. We hope that you have selected a frame has some support for all otherwise… vérificationMéthodes to check email, length and force password user account template options, a good idea of the names of account that you want to hold back so that you can still do as /admin /static on.Lost password flow paths later. You want to generate a key and store the defeat for when someone asks to reset their password. This is another email which must go out.Sign flow.Sign flows. (Be sure and use POST method to sign.) See why here<- signs="" you="" out="" of="" delicious)sign="" up,="" display="" errors.update="" your="" settings,="" name,="" password,="" email—doh!="" you'll="" have="" to="" verify="" the="" email="" again.="" an="" account="" verification="" system="" done="" through="" email="" so="" you="" can="" verify="" people="" have="" given="" the="" correct="" information.scheduled="" backups="" of="" your="" database="" being="" pushed="" to="" a="" separate="" location.="" binlogs?="" mysqldump?="" you'll="" have="" to="" write="" a="" script="" or="" configure="" your="" off-site="" db="" slave.="" you="" might="" also="" want="" to="" test="" that="" it="" works.oh="" hey,="" you="" can="" delete="" your="" account="" on="" delicious?="" what="" does="" this="" mean="" for="" the="" bookmarks,="" favorites,="" and="" friend="" relationship="" interfaces="" you="" haven't="" even="" written="" yet?="" save="" that="" one="" for="" later="" i="" guess.following="" and="" being="" followed="" flow.="" this="" includes:="" a="" database="" for="" holding="" friend="" relationships.="" an="" interface="" for="" looking="" at="" everyone="" you="" follow.an="" interface="" for="" looking="" at="" everyone="" who="" follows="" you.ability="" on="" each="" of="" the="" above="" pages="" to="" follow="" (or="" unfollow),="" probably="" using="" ajax="" because="" people="" don't="" want="" to="" leave="" the="" page.="" also="" you're="" going="" to="" want="" to="" paginate="" that,="" some="" people="" are="" popular.blocking="" followers="" and="" the="" processes="" that="" recognize="" a="" follower="" has="" been="" blocked="" when="" displaying="" content.the="" required="" database="" indexes="" for="" extracting="" and="" displaying="" follower="" counts.so="" before="" we="" get="" to="" bookmarks,="" what="" about="" import="" tools?="" why="" would="" anyone="" move="" to="" your="" system="" without="" import="" tools?="" you="" will="" need:="" a="" task="" queue.="" hopefully="" distributed="" so="" you="" can="" pass="" importing="" off="" to="" your="" workers="" on="" other="" boxes="" when="" things="" get="" overloaded.some="" sense="" of="" the="" different="" formats="" you'll="" need="" to="" process.="" delicious="" being="" the="" big="" one,="" but="" there's="" google's="" product,="" diigo,="" xmarks="" and="" pinboard.="" also="" people="" are="" going="" to="" want="" to="" import="" from="" their="" browsers.="" i'm="" not="" even="" talking="" about="" actually="" processing="" these="" things,="" just="" understanding="" and="" researching="" the="" formats="" and="" pitfalls="" is="" going="" to="" take="" some="" time.actually="" doing="" the="" processing.="" what="" happens="" when="" something="" fails?="" do="" you="" offer="" a="" report?="" there's="" a="" new="" page.="" can="" they="" retry="" without="" duplicating="" inserts?="" i'm="" really="" only="" scratching="" the="" surface="" here,="" this="" is="" tedious="" shit.tags.="" related="" tags.="" searching="" tags.="" recent="" tags.="" explore="" tags.="" you="" gotta="" use="" that="" task="" queue="" for="" offloading="" a="" lot="" of="" this.="" when="" does="" it="" run?="" what="" happens="" when="" it="" fails?="" seriously,="" i="" don't="" even="" want="" to="" think="" about="" tags="" right="" now.="" there="" has="" to="" be="" a="" module="" out="" there="" that="" will="" do="" it.="" go="" read="" the="" docs="" to="" that.three="" letters:="" a="" p="" &="" i.you="" are="" going="" to="" write="" unit="" tests="" for="" all="" this,="">

You still do not fully inspected all your problems XSS, implemented research content, thinking about the design and UI, documentation and errors, different methods for storing links as bookmarklets (tested in all browsers) or, you know, actually record in a database for the presentation to you and other bookmarks.

Then there is a pattern in the URL which can be problematic (http://xyz.com/ versus http://www.xyz.com versus https://xyz.com/ versus http://xyz.com/index.html), I never really thought about this problem, I am certain that it will take only a few minutes. We deal with later.

(Thanks to usernameguy and Anil for some inspiration.)