Search This Blog

VC: Bento Roles & Business Pitch

So after much deliberation and focus on getting our mission, vision and some of other core ideals of Bento set in stone on content we began the work our presentation. It took a lot of thought to decide on the content of the presentation. To begin with we took our mission, vision and some core ideas. A lot of it had to be cut out to properly format it in the form of a presentation.

Another thing we had to sort out was roles. We set about creating two roles for each of us, one more technically oriented and one business oriented. Knowing where each of our strengths and weaknesses were, Cai's role was fairly easy to define as the Lead Designer and Creative Director. However both Chris and I are primarily developers, so this was a little tricky. We decided to name me the Lead Developer and Technical Director, while Chris went with Interaction Developer and Managing Director. While these are great on paper in reality our set roles would be a bit more blurred, put perfectly by this quote from Breakfast NY, one of the companies we researched:

"Our account guys code, our coder guys concept, and our designer guys do spreadsheets. Why? Because they want to, and see the benefits: they move faster, take part more, and produce better work because of it. We like it when people get the itch to try something new and completely different. We wouldn't exist without that."

Once we had our roles set and refined our mission, vision and USP. We began deciding on who was saying what during the presentation. Initially the three of us were going to present. However we felt that with the way the content worked it would deter from the presentation if we all spoke for the sake of 'all of us speaking'. Cai was to talk about our branding and Quote.me, while Chris talked about the team, our mission, vision and USP. I was to demo the Quote.me website while Cai talked about it. Here's the final presentation:

Comments

Post a Comment

Popular posts from this blog

So I recently acquired a Logitech G502 mouse, and I have to say I absolutely love it. It's a beautiful mouse, and a worth upgrade to my old G500s mouse. However my one gripe was the new all-metal scroll wheel. While the weight was nice, I missed the rubber ring around my old 500s. This led me to attempt to replace the new 502 scroll wheel with the old one from my busted 500s.

So let's get started shall we?

So as you can see, these are what the mice look like side-by side. While they look drastically different, the ergonomics are actually very similar among the two.
The first step was to take the mouse feet off and unscrew the screws that hold the chassis in place.

So the feet are layered. There's double-sided adhesive foam, with the feet on top. On the back foot, I managed to peel off the feet with the foam. However on the front two feet the foam stayed stuck to the chassis.

So my old Dell L502x died. However most of the components were fine, it's just the motherboard that seemed to be down with a case of water damage. So along with turning the chassis of the laptop into a dock/stand for my new laptop I wanted to turn the laptop's screen into an external monitor.

So the first thing I did was extract the panel from the housing to take a look at the model number and the interface. If you're looking to do this yourself just look up the documentation for your laptop or go to ifixit.com and look it up. Fortunately Dell has excellent documentation and a pretty straightforward teardown process.

So Tuesday went... interestingly. Getting the transmitter transmitting data other than the binary ones and zeros went kinda well. It wasn't quite as hard as I expected, but still took a little while to get sorted.

The goal was to set up the transmitter sending a numerical ID and a value between 0 and 170. The 0-170 value was so that the receiver could forward this onto the servo, which would then the volume knob. This was generated by a potentiometer reading being mapped from 0-1023 to 0-170. Then this number was converted into a string, and prefixed with a number of '0's to ensure the string length was 3 characters. So essentially '139' would remain unchanged, '72' would be prefixed with a '0' to make the string '072', and '8' would be prefixed with two '0's to make '008'. This three character string would be then prefixed by the one character ID. Broadcasting something like 1139, 1072 or 1008.