Skip to main content

I am a COMPUTER ENGINEER

I am a Computer Engineer.

I know what you're thinking.
You're thinking, "That guy is Cool".

You're so right. I don't like to brag, too much, but I'll let you in on some details.

I have many friends
in chat rooms.

I have excellent contacts
but I prefer to wear glasses because they make me look so cool.

Many women want me
to fix their computers.

I frequently get laid
off.

I know many languages:
Java, C, C++.

I travel to many exotic places
in online games

I'm into sports
drinks.

I collect fancy cars.
Most are still in their original Hot Wheels packaging.

I smell good
so I don't shower very often because I don't want to ruin it.

I have a black belt
that I wear when I can't find my suspenders.

I know that you're now thinking "I want to be that guy."
But you can't.
I was here first.

Courtesy: an unknown blog with an unfamiliar name. Anyways, thanks.
Prince Mishra
Computer Engineer

Comments

Popular posts from this blog

On working remote

The last company I worked for, did have an office space, but the code was all on Github, infra on AWS, we tracked issues over Asana and more or less each person had at least one project they could call "their own" (I had a bunch of them ;-)). This worked pretty well. And it gave me a feeling that working remote would not be very different from this. So when we started working on our own startup, we started with working from our homes. It looked great at first. I could now spend more time with Mom and could work at leisure. However, it is not as good as it looks like. At times it just feels you are busy without business, that you had been working, yet didn't achieve much. If you are evaluating working from home and are not sure of how to start, or you already do (then please review and add your views in comments) and feel like you were better off in the office, do read on. Remote work is great. But a physical office is better. So if you can, find yourself a co-working s

Capture and compare stdout in python unit tests

A recent fan of TDD, I set out to write tests for whatever comes my way. And there was one feature where the code would print messages to the console. Now - I had tests written for the API but I could not get my head around ways to capture these messages in my unittests. After some searching and some stroke of genius, here's how I accomplished capturing stdout.

Todo lists are overrated

My tasks come from a variety of sources: 1) Tasks from emails  2) Meeting notes with details of people who participated  3) Project related tasks that can have a long format and can be tagged/ delegated  4) Scratchpad for unrefined ideas  5) Detailed documentation for completed technical tasks / ideas  6) FIFO list of high priority small daily tasks No one app has been able to map all the requirements above, and I have tried a lot of them! In my lifetime I’ve tried a dozen todo apps. In the beginning they all seem different, novel and special. Slick UI, shortcuts, tags, subtasks, the list goes on and on. But all our stories were the same: I start using the new app, then after awhile I stop using it. Up until the last week I thought the problem was in myself (you probably think so too). After all, David Allen seems to have figured this shit out. Also there are people leaving long 5 star reviews on every major todo list app, they discuss them on forums, recommend them to friends. But the