suggestablog

order and share the best delivery in your neighborhood.

[suggestaurant]

getting ourselves ready for ny tech day tomorrow!

[suggestaurant]

the trusted options for dealing with a breakup...

suggestablog episode 15…starting over.

it had been almost a year since we started working on suggestaurant, and now we found ourselves almost at the beginning again…but worse.

a year ago we were fresh-faced and bushy-tailed. we had optimism galore. our bank accounts were full. and everyone was on our side.

after a year of blood and sweat and yelling and tears and sleepless nights, we were still not entirely done with the front-end (oh yes, remember our ukrainian friends? we were still going back and forth with them on a daily basis with no definitive end in sight). we had already spent a considerable amount of money on various marketing tools and more than expected on programming costs. neal and corey had quit their full time gigs to devote their total attention to the cause with the hope that we’d be well on our way by now. restaurants that we had signed up 6 to 8 months ago were getting restless. and new ones we were signing up wanted to know a launch date, which we couldn’t provide. and finally our cto, the guy that was going to bring this all home for us in the next month or two had just walked out, leaving us with a jumble of code we couldn’t understand or implement.

the first week after his departure was rough. mainly on jason and corey who had been with guy from the very first meeting and down to the house visit. jason had fought the hardest to give him another chance (or four) when things were looking bleak.

dina, watching them from the side, couldn’t help but smile (a little) at the fact that they were taking this exactly like a rom-com breakup. they would talk for hours of betrayal. of their feelings. of how they thought he was ‘the one’. if jason hadn’t been lactose intolerant, there would’ve been a ben & jerry’s shortage in nyc.

once the dust settled, and the reserves of johnny walker had run dry, it was back to the drawing board. we needed a programmer…again. we considered, and even somewhat attempted to find, another programmer for equity but we quickly gave up with no sound leads. and since both internal and external pressure for us to launch was mounting, we decided to try a different route...and instead went on a search for a programming company.

[suggestaurant]

guy’s expression (top) at seeing jason and corey (bottom) at his door.

suggestastory: episode 14…love at first site, part III.

‘are we just going to his house?’ corey asked. he wasn’t joking.

‘we might have to.’ jason replied. he wasn’t joking either.

dina looked from one to the other and nodded. we were running out of options.

it had been a solid two weeks since we last heard from guy…and it wasn’t for lack of trying. we had started out with emails. when those went unanswered, we threw in some texts. then a couple of phone calls. by this point we were getting genuinely worried. we even googled his name to see if there were any news articles on him — programmer wins millions! programmer gets hit by bus! programmer launches social food delivery company…

it wasn’t that guy was the most responsive person of all time, but he was fairly good about replying to an email within a day or two. so two weeks of total radio silence was definitely out of character and why jason and corey found themselves outside of his apartment. (we were considering going full force but decided that less people was better in this case.)

to their surprise, guy opened the door…and he looked totally fine. well, minus the complete look of shock on his face. after a few moments of silence and staring (looks that said ‘is that really you?’ from both directions), he invited them in. the conversation from there went fairly well. although guy didn’t really offer a concrete reason for his absence, neither jason nor corey pressed him on it because he reassured them that the programming was on track and that we’d have a live site by the end of the summer (which was about 5 months away). after discussing a plan of action, everyone parted on good terms and with much hope for the future.

over the following weeks guy proceeded to be at his most responsive and most active. we got updates on progress, met a few times to go over various parts of the site that needed discussing and in general went full steam ahead. then things started to slow again.

daily correspondence changed to bi-weekly, then weekly. meetings got pushed back. texts started to go unreturned. also, although we were supposed to be launching in just a little while, the backend, despite all of our many discussions, hadn’t seemed to progress much at all. we were getting fed up. and whispers of discontent began to grow louder.

we finally made the decision to have one final talk with him, give him one final chance…and depending on the outcome, cut the cord or launch (eventually…if we got the site finished).

and right when we were considering a second house call, we got an email. the email was short and to the point — he didn’t want to work on suggestaurant anymore, he was out. before signing off, he gave us a name of another programming company that he had worked with in the past that he was certain could pick up the thread and bring us home.

so there we were, in the beginning of august…almost a full year from when we started…back at pretty much square one.

[suggestaurant]

suggestastory: episode 13…settling in.

when 2013 hit, we were all in the groove. jason, corey and neal were out selling on most days. when they weren’t selling, they were entering menus. really, it was mainly neal and jason selling while corey spearheaded the menu entering. meanwhile, dina continued on battling with the front-end programmers. and guy worked on the back-end.

every so often the team would get together for meetings, go over everyone’s progress. these meetings would take place at either dina’s apartment or at the atrium.

as many new yorkers know, there are many such atriums around the city. for those of you that don’t, imagine the food court of a very expensive mall. that’s kind of what an atrium is.

our atrium was semi-conveniently located in the center of the city. we’d get there, find a table, grab some extra chairs and settle in for a few hours. there was free wifi, various coffee-type places to choose from and bathrooms for our convenience. all in all, a perfect recipe for a temporary office.

the only issue was that our office had a revolving door of visitors. some were quiet and there to work. some were there to meet a friend. and some were just hanging out. and the noise level varied accordingly.

there was one group of people that came there to play chess on occasion. not sure if they were of the kasparov variety so only minimal concentration on the game was needed or if they just came there to chat and chess was just the pretext, either way, two things were clear…one was that they really loved to chat…and two was that at least one in their number must’ve been hard of hearing cause their conversations, magnified by the acoustics in the atrium, could be heard from the bathroom…and probably from a few blocks away.

they usually arrived when our meetings were in full swing so we carried on, talking over the din…partially and inadvertently also listening to their conversation. sometimes offering advice or commentary (amongst ourselves).

and that’s how it went for a few months. everything seemed to be progressing at a somewhat steady pace until one day we emailed guy and didn’t hear back…

[suggestaurant]

[suggestaurant]

suggestastory: episode 12…when winters were cold.

while dina spent her days obsessively refreshing her email waiting for programming updates and guy contemplated the back-end, neal, jason and corey went out in search of restaurants to sign.

it was late november of 2012…the weather, unlike the springtime we’re experiencing now, was actually wintry cold. but worse than spending 8–10 hours walking the streets of new york in the sleet and snow was trying to get that first elusive sign up.

out of our little sales force, only neal had actual professional sales experience. but even so, the pitch had to be ironed out on the fly and each sale varied tremendously.

some restaurants shooed us out as soon as they heard we didn’t want a table for three. some waited long enough to hear the opening of the pitch only to tell us (oftentimes very unceremoniously) to beat it. some actually patiently listened through most of what was said only to say that they already had enough delivery sites. or that the owner wasn’t in but they’d get back to us. or that they would wait till we were live. or that we didn’t have enough restaurants signed up… (well yeah! say yes and we’ll have some!)

weeks went by and we started wondering if we’d get any signs up. and then, one day, this very day three years ago actually, suggestaurant walked into a new asian restaurant downtown. it was mid-afternoon, chilly, of course. it was jason’s turn to do the pitch and so he did. before he even officially finished it, the owner, a young guy, stopped him and said ‘let me get a pen.’ and that was that!

that very evening two more restaurants were added to the roster. and after that, they more or less started rolling in.

[suggestaurant]

suggestastory: episode 11…p(t)sd…or, our first big mistake.

we’re going to start with the moral of the story here…if you have a complex site idea with many working components, do yourself two favors…1) hire a front-end and back-end programmer (or a team of them, whatever you can afford) to work together…at the same time. and 2) spend the time and money to hire an actual programmer you can see and talk to. outsourcing of any kind (domestic or overseas) is not worth it. not the money you think you’ll save and certainly not the time you think you have.*

i wonder if we would’ve listened if someone had told us…

but anyway.

now that the team was in place, we really got to work.

one of the things that was happening behind the scenes while the search for a programmer was underway was the designing of the site. there were bi-weekly meetings in every coffee shop and gin joint around the city that would have us. we texted, we emailed, we conference called.

the general site design was more or less settled on around the time our cto joined and, with a couple of (more) meetings to hash out some back-end thoughts and ideas, we were ready to begin programming.

it quickly turned out that although guy did know some front-end, he much preferred to spend time on the back-end. and since the back-end promised to be a doozy, we took his advice to hire a firm to take care of the rest. the firm he suggested was one that he had worked with before. a european company with call centers in the u.s.

the first order of business was converting dina’s illustrator files to psds. we asked how much it would cost…’we do it for free!’ they said. how could we say no to that?

we sent over our files with extremely detailed instructions. they were complex. we got a quote and a turnaround time. things were progressing well.

it started to get complicated when we got our first batch of html/css files back. there were a lot of things to check and a lot of corrections. we went back and forth. the price was upped here and there, the timeline extended. what should’ve taken only a few months took 11. (yep, you read that right.)

the large time difference between them and us didn’t help at all. oftentimes, only one email was sent/answered before they closed down for the day. we’re not sure if they did it on purpose or if they were just working and leaving email replying to the end but we often didn’t get any emails at all until around 8am our time and by the time we read them, checked whatever was required and got back to them, they were gone. weekends were out of course. the call center in the u.s., which sounded great at first, turned out to be nothing more than the purveyor of very superficial information about the company in general with the only way of contacting people involved with the actual project being via email. also, talking to the actual programmers was out of the question. maybe they didn’t speak english. or maybe they weren’t allowed to fraternize with the clients. either way, the only person one could communicate with was the account manager, who didn’t know much (any?) programming herself and had to relay any questions we had to the actual programmers, resulting in more delays. so a simple question could easily take 24 hours to be answered.

towards the end of the project, when we were so close we could smell the fresh air wafting in but the final tweaks were taking weeks upon weeks, we were told (upon asking why a delivery date they set themselves wasn't met by over a week)  — and we quote here — ‘we have never worked on a site this complicated so we have to learn as we go.’ not exactly something you want to hear from a professional front-end company advertising their ability to handle and do everything. in actuality, what we were asking them to do was to test the code on a few different browsers and make sure that things more or less looked the same.

we would’ve vented to our cto about it but, by that point, he was long gone. but more on that later.

*the views expressed in this blog (here and to follow later) about outsourcing are based on our specific experiences. we do not believe that all outsourcing is bad. situations differ and so do outcomes.

[suggestaurant]

suggestastory: episode 10…love at first site, part deux

while the events of the past few posts unfolded, we were working behind the scenes continuing the search for a programmer.

aside from the two previously mentioned leads to nowhere, things weren’t really progressing…until they suddenly were.

the wall of radio silence broke one day to let through a reply from a man named…well, let’s call him guy. he styled himself ‘a serial entrepreneur’, having worked on a few handfuls of startups. his biggest claim to fame was being part of a pretty large work-search internet company.

he sounded perfect!

jason and corey met him in a bar. over scotch on the rocks they discussed the merits of startups, various thoughts on programming in general and specific thoughts on programming suggestaurant. guy spoke with ease and conviction. the meeting (and scotch) went well and everyone agreed that a second date was in order. this time, dina joined in.

the setting was another bar. the subjects similar, the drinks the same. dina asked if guy ‘knew front-end programming’ and got a raised eyebrow in response. was there anything this man couldn’t do?

we (suggestaurant) left the bar elated. talking over each other while we walked to the train, stopping for extended periods. a walk of 5 minutes turned into 45. he liked us and seemed very interested. we loved him!

after that, we met him a few more times to make sure it wasn’t the scotch talking. neal came along too.

finally, after a few more solid dates, we decided to make our status official. the offer was put forth and duly accepted…and by the end of november, guy rounded out the crew as the chief technology officer.

we were on top of the world! five of us going forth to launch suggestaurant and become millionaires. easy peasy.

…but if launching a startup was actually easy, then everyone would be doing it.

[suggestaurant]

suggestastory: episode 9…and then there were four.

“i’m so excited i gotta smoke a cigarette.” said neal, beaming.

neal and jason were standing outside the ainsworth after a solid meal and quite a few beers. the evening had passed in a flood of excitement and plans. jason had told neal all about suggestaurant and, pretty much from the get-go, every sentence out of jason’s mouth was met with a ‘really!?’ or a ‘wow, that’s great!’

jason had had neal in mind for an addition to the team for a while. neal was trustworthy, a good people-person and the fact that their friendship went back to the early days of high school didn’t hurt either. for his part, neal had always wanted to start his own company. he, like jason and corey, had tried his hand at his own business — a company having to do with energy sales. but things had stalled there and he was on the lookout for something new. and that's when jason called.

it had originally, of course, started with poker, the great uniter of man (in this case, boys). in plainview high school, poker was king during the jason, corey and neal years so it made perfect sense that their friendship would blossom over the hours spent playing it.

after high school, everyone parted ways for college but jason and neal stayed in touch. and when the time came to getting a sales person for suggestaurant, jason knew that neal was the right man for the job.

so a few days after that cigarette outside of the ainsworth (and a few more cigarettes i’m sure), neal officially joined the team as the chief restaurant officer.

poker set won by jason during his poker days that’s still being used at all plainview alumni poker games.

[suggestaurant]

suggestastory: episode 8…printing during a hurricane.

we bring you back to where we had left off (before we interrupted our story for a very thrilling update about our living arrangements)…the first few months of suggestaurant.

we had started to assemble our team — corey, jason and dina were all on-board. the name was set, the logo designed. we were on the constant lookout for a programmer but so far hadn’t gotten very far. however, to make sure that we were still moving forward while searching around for our future cto, we divided our time between figuring out what our site would eventually include (what features we wanted, why we wanted them and when we wanted them…aka what must go into version 1 and what could wait till version 2…3…25) and gathering a list of restaurants to approach. 

since approaching restaurants empty-handed seemed a little stingy to us, and we couldn’t afford to give out ferraris, we decided to print some sales aids. dina knew a couple of good printers in the city, corey had a connection to some merchandise vendors, so we got to work. 

on the list were suggestaurant-embellished jackets for the ‘sales team’ (aka us). some suggestaurant pens to give out. some suggestaurant blankets for our homes (cause why not, corey could get those for free!). some folders to hold the sales aids. some business cards. and some stickers to paste on the restaurants that we signed up.

as any group of super excited people with a great idea to share, we wanted all of those things yesterday. a day’s delay seemed like the end of the world! and unfortunately for us…the weather seemed to think the same — we sent our business cards and folders and sales aids to print right in time for sandy, the hurricane.

the printer where all of this was being handled was (and still is) located downtown right in the middle of the flood zone. and right around the time all of our stuff was supposed to return back to their offices, printed, packed and ready for us to hand out, sandy arrived and delayed everything.

after a delay of a few weeks and the loss of all of our finger nails in anticipation, we got the phone call! the boxes had arrived and were ready for pick-up!

dina, corey and corey’s then girlfriend (now fiancée, yay!) went to retrieve them. while corey hailed a cab, dina and the fiancée watched and then carried the 4 large boxes of folders and such and another smaller box of business cards to the trunk. corey had a gym-related arm injury. 

the cab, the elevator, dina and the fiancée transported the said boxes to corey’s apartment where they remained (and subsequently took up half of the living room) for the next month and a half before being touched again. the reason was the imminent acquisition of a 4th and then 5th member to team suggestaurant.

just goes to show that what you thought you needed yesterday you could easily live without for a few months at the least.

[suggestaurant]

*** suggestaschool: week 7 * suggestion box ***

we got somethin’ real important to tell you so just sit down and listen… you know we’ve been together such a long long time (such a long 7-week time) and now we’re ready to lay it on the line you know it’s halloween and our heart is open wide gonna give you something so you know what’s on our mind a gift real special, so take off the top take a look inside — it’s the suggestion box

it’s easy to do just follow these steps

1: after ordering, click the ‘suggest’ button above your feed. 2: choose a friend(s) that you’d like to send your suggestion to and select the radio button either for ‘someone specific’ or 'someone & everyone’. 3: press 'suggest’ to put your suggestion in their box.

[suggestaurant]

suggestastory: episode 7...clear some space, we’re moving in!

we interrupt our regularly scheduled programming to jump ahead to present time.

a lot has happened since we launched and although we’ll be getting around to discussing it in more detail later, we wanted to let you know some exciting news…mainly because we’re pretty ‘woohoo!!!’ about it and this is our place to share that. :o)

since we met (team suggestaurant, not you and i), we’ve worked everywhere —from starbucks to argo teas to panera breads to atriums and other indoor (and outdoor) spaces to each of our apartments — and, while doing so, we had been secretly (and not so secretly) wishing and dreaming about a place where we could hang a suggestaurant banner and call it home.

each of us had envisioned our own little oasis. jason wanted somewhere he could be any time of day or night without the requirement of ordering a beverage of some sort to stay an extra hour. corey wanted to have lunch with his dad in ‘our’ office. dina wanted some plants. neal wanted to sit back and drink a beer at work. …the only problem was that we wanted this place for free or as close to free as we could get.

you’re looking in manhattan? right! good luck with that! you say. no, that’s not what you say. who’s neal? ah. well, that’s the problem with skipping ahead…we hadn’t gotten to neal yet. hmm. i guess you’ll just have to tune back in to get the details on neal…but for now let’s just say that he wanted to drink beer at the office and we were all for that.

so there we were, the four of us looking to find some free office space in the most expensive city in the world. we searched the internet. we asked everyone we knew. and then everyone that they might know. and we got nowhere. you’re not surprised. we weren’t completely either. but we carried on. and after a few weeks of searching (spearheaded by corey) we came upon a solid lead. a music magazine was renting out a little nook. it wasn’t free but it wasn’t as exorbitant as we had gotten used to hearing. so corey and jason went over there to get the lay of the land and to try to negotiate it down to the lowest low. after one meeting and a week-worth of back and forth emails later, we had ourselves a little oasis!

treats for everyone!

abbott and costello.

after the furniture is arranged and all the chairs brought in, jason takes a look around and says with complete sincerity (hands on hips) …’we could probably squeeze in a fifth.’

[suggestaurant]

suggestastory: episode 6…midnight ponderings.

as dina sat and stared at the screen full of fonts she had selected, her biggest dilemma wasn’t helvetica versus arial. it was capital letters. namely, to use or not to use.

she had always been somewhat partial…maybe a tiny bit lazy…and this was her chance. but she hesitated. it’s one thing for you to do something because that’s how you’ve done it. it’s another to make it a company style because that’s how you’ve done it. but it seemed so right! capitals were formal, proper. they wore suits to the office and worked 9-5. dina had never worn a suit in her whole entire life, and she never intended to. it was almost midnight on a saturday, so clearly 9-5 was out too. but capitals were the conventional way. not using them would be somewhat ballsy. plus, if we didn’t use them, we’d have to not use them. anywhere. as a rule.

she tried one of the font selects. in all caps (convention was hard to break). it didn’t look right. she tried a different font. this went on for a while. after a hour she had a few logo options with all caps. she chose two, took a deep breath and started again. all lowercase this time. in another hour or so she had it. kind of like when jason said the name and knew that it was it. the logo just said suggestaurant…literally and figuratively.

logo colors were another story. they involved research. articles. books (the regular kind and pantone ones). we stopped on red and green cause of their strong food association.

...picking the exact shade took almost as long as the actual logo design!

[suggestaurant]

*** suggestaschool: week 6 * find your friends ***

we're back to tell you all about how you can easily connect with your friends on suggestaurant. it's essentially a social inception...

how it works

step 1: go to nuts & bolts > social. step 2: connect to facebook and/or twitter. step 3: click the 'find friends' and 'find followers' buttons. step 4: locate and follow all of your friends. step 5: don't see your friends? it's probably because they aren't on suggestaurant (yet). yeah, we think it's a shame too.

[suggestaurant]

suggestastory: episode 5…what’s in a name?

are you a parent? if you are, then you probably went through a long process deciding what to name your child.

maybe you started out on the internet. searching through top baby names. then just baby names. then unique baby names. then foreign baby names. then you scrap all of that and move on to flowers, cities…weather phenomenon. you consider switching genders. hey, ashton and mila did it, why not you?

you make a list of all the options and take them to your partner. they have a list of preferences too (of course). and it doesn’t match yours. so you divvy up vetos and dwindle the names down to what you can only call the short(ish) list.

you stare at the names for months. doubting your top picks. switching them up every once in a while. randomly throwing in a rogue name from left field. finding yourself removing a name you’ve liked since the time you knew you wanted a baby. when the day arrives, you’ve settled on the perfect one! it’s go time. but as you hold your baby in your arms and whisper ‘hi, susan. susie. sue.’ you realize that it’s all completely wrong. she looks nothing like a susan!

ok, so maybe that wasn’t how you went about it. but if you have a startup — aka your baby — chances are good that that was you.

the name has to represent your product. be memorable. spell-able, maybe. you can’t change your mind mid-stream. once the business cards go out (and the ink dries on the stock agreements), you’re committed.

most times you ponder the name for months. it becomes a 24/7 job where you find yourself sitting bolt upright in the middle of the night and having to write down what you think is the most brilliant name of all time only to laugh at your semi-coherent scribbles when your coffee kicks in the next morning. you pour over everything you can find. bouncing ideas off of friends and family. writing names down on napkins. you may even hire someone to help you nail down what will essentially be one of the most important decisions you make for your company.

other times, a rare few times, you get lucky. stars and planets align and the name just comes to you.

team suggestaurant was prepared for the long haul. we had been absorbed in thought for a few days. a group text was created. names — potentially usable and completely not — were being sent at all hours. it was all going nowhere until jason called corey with an idea. we needed to adjust our thinking a bit. not just think of a company name that we'd love but think of a company name that we'd love even if another company had it. love the name and secretly seethe that we didn't think of it first. 'for example' jason said completely off the cusp, 'i’d be extremely unhappy if a company named ‘suggestaurant’ or something copied our idea.' there was a long pause. then corey asked, 'is that it?'

within the hour we had settled on ‘suggestaurant’ and the rest, as they say, is history.

[suggestaurant]

*** suggestaschool: week 5 * taste buds ***

suggestaschool again, and this week we’re all about taste buds — your friends on suggestaurant that is.

when you follow someone on suggestaurant, your actual taste buds benefit because that person’s suggestions appear in your feed. if he/she returns the favor and follows you, you can send each other suggestions directly to your respective suggestion boxes.

how it works

step 1: go to taste buds. step 2: select the ‘followers’ tab and do a search. step 3: click 'follow’ and meet your new taste bud! step 4: see his/her suggestions appear in your feed!

pro-tip…only those suggestions from people whom you’re following will appear in your feed. so choose wisely!

[suggestaurant]

suggestastory: episode 4…love at first site, part 1

it’s a problem that a lot of startups face — we knew it for a fact because we came upon it countless times in our search — finding a programmer is a total bitch!

unless you’re fortunate enough to have a friend that’s a programmer or a friend that’s dating a programmer or a friend who happens to work with a lot of available programmers…you get the picture. in fact, the biggest regret we had for the first few months of starting suggestaurant was that when we saw a guy wearing a ‘mongo db’ t-shirt crossing the street around union square (we were in a cab coming back from a trip to the printers) we didn’t immediately leap out of the cab and tackle him.

things got so desperate (programmer-wise) for a while that we started to refer to jason as json and all joked about learning programming ourselves. which, if we knew how long things would end up taking, would’ve been a perfectly justifiable use of our time.

the challenge was that we wanted someone — a perfect stranger — to fall in love with our idea as much as we had (having spent a fraction of the time with it), subsequently believe in it so wholeheartedly that he/she would immediately agree to quit his/her paying and stable job with benefits for this non-paying one, with a good amount of risk and the only immediate benefit of having your friends and family miss you a ton…cause you’d be working days, nights and weekends.

to find a programmer we tried regular job sites, irregular job sites, startup sites, job forums, job fairs, universities, colleges, computer classes…we actually considered setting up a table outside of google to solicit programmers working there but couldn’t decide what we could give away (besides equity and our souls) that would entice them to holt their coffee runs and listen. (do google employees even go on coffee runs? or do little battery-powered drones, sensing their every whim, swoop in with a cup of hazelnut mocha frappuccino, whipped cream optional, whenever the mood beckons?) and then we caught a break. we got two responses in quick succession from two programmers — a woman and a man — who seemed intrigued.

we met the woman first. the interview went well enough and she liked our idea very much. but she wasn’t sure if she’d be able to do this full time and not sure if equity would be enough so after a brief back and forth we moved on to the second candidate.

the second candidate went a lot further in the process. he met jason and corey first. they spoke at length about suggestaurant, about numbers and figures, about prospects, about avenues to take and streets to avoid. it went well enough to warrant a second meeting. this time dina came along too. they went over some of the stuff they discussed the first time. and they discussed some other things. he said that he’d go home and think on things. we said we’d do the same.

meeting number 3 turned out to be a skype date. jason, corey and dina squeezed onto a couch that was meant for two while he spent an hour going over a spreadsheet that he created detailing the estimated amount of time it would take him to program every minute detail of the site plus the amount of time it would take jason to do his job, corey to do his and dina to do hers. he then informed us that he was only available to work part time and that he might be getting a promotion at his full time, fully paid job…fingers crossed.

that was the end of the guy and the end of our current candidate pool.

we really should’ve started learning programming then…but we didn’t.  

-------------------------------------------------------------------------------------------

if you’d like to pick up some programmer swag for yourself or for a special someone in your life…here’s one of many possible options… http://www.spreadshirt.com/programmer+gifts#/list/programmer