Bhardwaj Rish

Tonbo Imaging is the best company to have started my career with, for I've had the opportunity to do something I got interested in at the very start of college; developing software for tangible systems. It has been 6 months of internship and 6 months of full time employment, and I'm certain I've learnt more than I ever could have during my four years at college. I've been very fortunate to have a very knowledgeable mentor, and a manager who gives us a lot of space to think and ideate, and spend time on research. In the past year, I've worked on developing an ecosystem of small-sized thermal cameras running a custom Android OS that perform video analytics, are controlled remotely and support global live streaming. It's taken a year to go from an idea to a proof of concept product - we're in no way scalable yet, and are continuously going through architectural changes while ideating and understanding the potential of this system. Most of my work has been R&

I'm sitting on a rooftop humming to half remembered lyrics of a song I heard the other day. I'm actively trying not to remember the long list of to-dos I've made for myself to finish before this year ends. I look at the passersby walking down the road and I see a couple wearing winter clothes. The first thing winter reminds me of is penguins. I ask myself what the name of the penguin from the animated movie Happy Feet was. I remember Lovelace, but he wasn't the main penguin. I'm then reminded of the fact that Marian Aunty, a grandmotherly figure from our time in Switzerland showed us giraffes in the Basel Zoo. I don't quite remember why they have black tongues, and so I start thinking of the survival advantages black tongues may provide. The thought doesn't stick too long as I see a bird fly into the tree that's as tall as the rooftop I'm on. Zap. Humans never evolved to see in the dark, but they made artificial sources of light. Do bats get e

There's this question that's been bugging me for over a month. It's a fairly simple question about a fairly common object in a city landscape, and yet it's an absolute mystery to me as to why I cannot come up with a believable solution. I've brought it up in ever-day conversation with friends and colleagues, hoping their answers might lead me to a justifiable answer. I've avoided Googling the answer for over a month, because some things in life just shouldn't be so easy. It's a fairly pleasant feeling to keep your mind pondering over such a simple question, and so the urge to pen this post. How are cranes transported and constructed? Take a minute, and visualise the size of these things. A crane is practically just two very long lines; one vertical steel pillar holding a similar horizontal one at the top. Moving them from place to place is difficult, and funnily enough, I've never seen a half-constructed crane. Here's a list of answe

Be the average man, the one if randomly picked from a group of identically average people, could represent just anybody. Let each day pass under its own circumstances, today, just the same as yesterday, letting the sole change setter, if any, be the minor perturbations life may bring. Don't actively think-ahead, plan in detail what you'd like to have achieved by the end of each week. Be tolerant, be just okay , with every new hardship. Settle, don't struggle too hard, be just okay  if you can't achieve your already not-so-high aspirations. - I did a small experiment with myself. For 2 weeks, I spent each day without planning ahead. I met all friends that invited me, I made all the easy decisions, slept for longer hours, didn't complain of not being able to do as much as I'd planned; because I'd planned nothing in the first place. I printed a calendar and wrote down what I did at the end of each day. I conclude it's far too easy being average. If

This is something I wrote in Aug 2016 when I was looking for a job at a startup, having already turned down working at Oracle. Read the Zoo of Jobs for context ! - This post assumes the startup has an idea of what they're building, has about 10-50 employees and is not necessarily funded yet. Most of these have been written with a tech startup in mind, but apply to businesses/established companies/institutions as well. I've been job hunting for the last month or so now, and have spent a good deal of time looking for internships last winter, summer, and the year before that. As of now, I don't have the liberty to pick and choose which startup's idea I like, and so have been going through hundreds of websites. Here's a list of things I realized during this period: All a company is a group of people who have come together to create a product or perform a service. State clearly what you do In the simplest of words, explain to me like I'm 5 what you do. All

Having finally settled into the post-undergrad work life, I realize how irrelevant my education was! You are hireable only if you add value to your employer. Since humankind is a social animal and most jobs function with constant interaction between people, you should know how to be a resourceful participant in a group and work constructively in a team. Every job can be thought of as a project. Whether it's construction, plumbing, computer engineering, teaching, or nursing. You start with a common objective and collectively work your way towards a goal. Independent of scale,  every  job is a project. Now, a project consists of being able to plan, negotiate, execute under strict deadlines and constantly collaborate with people. Since the primary role of education is to prepare the student to face the real world once they are out of their parents' protection, why don't we focus enough on working in groups? This is why Kindergarten was the best; the reason pre-school

I'm very fortunate to have grown up playing with LEGO. I credit my ability to patiently work on a problem for long hours to all my childhood days creating Lego train tracks, castles, and cities with Lego Minifigures walking around. It also taught me the complexity of going from a vague idea in your mind to creating a real physical model, and all the re-thinking and re-working involved. For example, I remember I wanted to create an infinity-shaped train track where the cross-tracks would be at different levels - some sort of a bridge. I ended up using a small table to elevate the track. A track similar to this, except raising one of the tracks at the intersection. It all starts with an idea and a vague picture of how the final model will look. You look at how many Lego pieces you have and whether you have the key resources you'll need. You then start building and as you face challenges along the way you learn to re-route to overcome obstacles. Once you're done with

We lost a OnePlus3T dev phone at work earlier this month. This upset me a lot, but later when I reached home and performed my customary routine of locking my cycle to the side railing, I questioned myself if I really have to go through the pain of locking the bicycle every single day - it's added effort and maybe even for no use. Much of security feels that way - 99% of the times nothing will happen, but the day it does you'll curse yourself for not being more careful. I tried coming up with a model to justify whether the daily time spent on securing these valuables was worth it. Here's a simple mathematical equation.  (Securing Justified) =   Price (precious_object)   - Price (things_bought_to_keep_it_safe)   - [ Value (daily_time_spent_to_keep_it_safe) x (#_of_days_from_purchase_till_theft) ]  If >> 0, yes, you should definitely go through the pain of securing your valuable everyday. If ~ 0, you could probably do without securing it. The amount of

I haven't written in a whole month and a half, courtesy my 70 hour work week, and weekends away at my friends'. I have a huge list of things I'd like to write about  scribbled [1]   in my Google Keep - there are things from over a year ago now that I haven't published, and wish I did for they seem less relevant to me now. For example, I made a list of qualities I wished to see in a Professor at University and never ended up publishing - but now that's in the past and what seems more relevant to my life at this moment is writing about how startups should function and a list of qualities I'd like to see in my work mentor. This is what I call a writer's dilemma. What were once  matters of consequence [2]  make little sense to write about now, and never will I come back to the time when these things hold as much relevance as they did at the time they were thought of and noted. Anyway, to rid myself of the guilt of not having written in so long, I spent the m

For over 3 years, I've been writing code in Java, and have worked on several projects which have grown to a moderately large number of classes. Apart from learning the syntax from a book in Grade 11/12, I've never formally learned  how to write quality readable and maintainable code.  The current project I am working on spans in all directions; it's an event based system, there is a lot of input coming from simultaneously running threads, there's Java-C interaction, there are multiple communication channels over different network mediums, there's an entire high-speed display rendering mechanism, and a lot more. The size of the project is sky rocketing and without a structured architecture, the code will not be maintainable in the foreseeable future. So, just as any other engineer would do, I've bought myself a copy of trusty Effective Java to formally learn how  to write code that scales.  Before I read this book, here's as much my 3 years of