Skip to main content

I am an Optimist..

 
I want to be an optimist

Being a software engineer involves a lot of pessimism: a lot of thought in the software engineering process revolves around things that might go wrong, that are going wrong, that have gone wrong, or that went wrong.

Over time, professional pessimism has been bleeding over into my personal life, and many times I tend to think more of things that could go wrong than about things that are going right.

There are times, though, when I want to be an optimist against the odds, and that even applies to the world of mobile gadgets.

I want phonebloks to succeed.



This is a great idea on paper. I hope that they can manage a level of integration that makes the size, weight, price and shape competitive with integrated solutions. I hope that going through a common backplane doesn't hurt battery life or system speed. I hope that hardware drivers can be made portable enough. I hope they can resolve the issues of antenna performance on a variable-geometry device, especially for big coils like NFC or Qi. I hope that carriers will be willing to provide end-user support for those devices.

I want Firefox OS to succeed.



This is another great idea on paper. I hope they can succeed in that direction where many other companies have failed. Looking at the ZTE Open, I hope that they can provide a user experience on that class of hardware that rivals what other systems offer on devices that cost nearly ten times as much. I hope they can transparently handle the high packet losses and connection drops that make the reality of mobile devices.

I want network interoperability to be a reality.

2G GSM interoperability was a mess. It took a while for phone to be available with all 4 common bands, and that didn't stay relevant for long as UMTS was getting deployed.

UMTS was a bigger mess, and it took 5 bands to cover the US and Europe (and most of the world with the notable exception of Japan). Now that we have phones that cover all 5 bands (e.g. Galaxy Nexus, Nexus 4), LTE is getting deployed.

LTE is an even bigger mess. It takes 5 bands just to cover the common US and European GSM carriers alone, and before you know it the list grows to over a dozen without digging much. Nexus 7 manages to support 4 bands in GSM, 5 bands in UMTS and 7 bands in LTE (and the LTE bands aren't the same in all variants). Other devices don't seem to be so lucky and have fewer connectivity options.

I hope that we can quickly reach a point where LTE devices can cover a dozen different bands or more, so that they can be used while traveling.

Popular posts from this blog

LibrePlanet 2017: Liberating your open source experience

LibrePlanet is a yearly gathering of free software activists, users, and contributors—and, it's my favorite conference of the year. Here's why.
LibrePlanet is run by the Free Software Foundation, and has steadily evolved from a yearly members' meeting with presentations from staff and board members to a full blown two-day conference with speakers and attendees from all over the world. The event brings people who care about free software together to talk about the future of the movement, address current challenges, and celebrate successes.
Prelude I was invited to give a talk at LibrePlanet 2017 on 25th March at MIT, in Cambridge, Massachusetts representing Mozilla as a Tech Speaker. I reached Boston on 25th early morning. Around 1 AM. The journey itself was awesome till I realized that you don't get Uber or Lyft at Boston Airport.

Not that the apps don't function there. They work! Just no driver will be ready to pick you up from Airport at that time. After trying t…

Maximum Call Stack size exceeded: My mishap with nodejs and MongoDB

Working with nodejs is always an adventure and mix MongoDB with it, and it becomes very interesting for a nodejs enthusiast like me.

While working on a pet project involving Native MongoDb driver and nodejs I encountered a weird problem.

RangeError:MaximumcallstacksizeexceededAs usual my first thought was to Google out what I was facing and googling it out led me to the following to links.RangeError: Maximum call stack size exceededCalling Model.collection.save() RangeError: Maximum call stack size exceeded Also In some posts in MongoDB’s forum I saw that peoples said saving in `process.nextTick` or wrapping the call function in `parseInt` will also fix the problem, but it most certainly didn't work for me.So I started digging in on my own and soon enough found the reason.

If you’re trying to save a document and saving process somehow exited with an RangeError: Maximum call stack size exceeded exception, it’s related to what you want to save in the database. I had this problem a…

All Hands 2016: MozLondon, A recount

I recently had the opportunity to take part in Mozilla All Hands 2016 (a.k.a #MozLondon). Mozilla All hands. All Hands are bi-yearly events of Mozilla where all the paid staff from different teams around the globe meet with each other along with a handful of invited volunteers to disscuss about future projects and get some work done! This year it was in London and just immediately before Brexit (I actually didn't even know about it before I went there). It was a work week, so essentially the event spanned from Monday to Friday. I arrived at LHR on Monday morning, and then there was the awesome Heathrow Express which took me to Paddington, just a 7 mins walk away from Hilton Metropole where I was staying with a bunch of other people. The event started with all of us having an evening orientation familiarizing us with rules and regulations along with Code of Conduct(that turned out to be really important later on...).  Tuesday started with a Planery. Which you can see if you are lo…