Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
Get a devDuck
Rubber duck debugging has never been so cute! Get your favorite coding language devDuckBuy Now
Search - "handoff"
An application that simply allows you to continue viewing something important from your phone (instant handoff)5
Smart contact lenses and the appropriate software. It would be the ultimate AR experience. I have no idea how to produce them, as they would need to be super high resolution, lag free, completely wirelessly powered and connected, safe to use and to wear and useable 24/7.
My current concept is a ultrabook sized block that can be taken around in a backpack.
Oh and wireless handoff ...
meaning everything I grab and throw in your general direction becomes available to you, kind off like they do it in Avatar. This should also work with PCs, tablet and everything else.
Speaking of grabbing you would also need some kind of minority report glove so every bit of hand movement can be tracked precisely. But probably a bit more elegant meaning only small stickers on the back of your hand.
Did I mention that sharing stuff should enable working together on the same object in real-time?
Also this system should integrate seamlessly with a smart environment, meaning looking at the light, opening its context menu and changing its brightness or colour should be no effort at all.
And of course all of it should be open source, highly scalable and either hosted on public infrastructure (funded by taxes or smt) or by each individual for himself to protect his or her privacy.
So who is with me?2
So a client (BPOS) asks me to build a website for their client(let's call them A). So BPOS decides to 'design' the site. The design is alright but the components they want does not exist. I need to build everything custom. And the website takes a few months longer than estimated. Mainly because BPOS doesn't do any QA for 3 months. At the end of the last month as we near handoff, BPOS wakes up and starts to do QA which mainly consists of vague information like " change to gray" instead of color codes and "increase font size" instead of the actual size.
By this time A is utterly pissed off and wants to give development to someone else. They get in touch with me directly to work with after the hand off by BPOS.
It's so amusing that I need to be in a KT meeting with BPOS and A when BPOS is pushing for annual maintenance and A doesn't want to give it to them and they keep ignoring BPOS.
ALL the delays are because an "account manager" who works for BPOS went on a trip to Australia.3
I use the ICU format often for translation because it's simple enough and supported on many platforms. It's something of a standard so I can use the same translation string format and similar library functions everywhere.
ICU is like a really simple templating language, somewhere between printf and something like smarty or twig simplified and specifically intended for internationalisation.
I updated a library providing ICU compatible parsing and formatting for one of the platforms I'm using and find tests break. I assume that only thing to change is the API. ICU very rarely changes and if it did it would be unexpected for it to break the syntax in a major way without big news of a new syntax.
The main contributor of the library has changed since some time last year. Someone else picked up the project from previous contributors.
Though the library is heavily advertised as using ICU it has now switched to using a custom extended format that's not fully compatible and that is being driven by use case demand rather than standardisation.
Seems like a nice chap but has also decided for a major paradigm shift for the library.
The ICU format only parses ICU templates for string substitution and formatting. The new format tries to parse anything that looks XML like as well but with much more strict rules only supporting a tiny subset of XML and failing to preserve what would otherwise be string literals.
Has anyone else seen this happen after the handover of an opensource library where the paradigm shifts?3
Handed off my code to Devs working on main products. Long presentation explaining everything.
Have discussion afterwards about what it does, but not how it looks.
They say thank you, I say you're welcome, and since this is my first bigger project, if they have some pointers or glaring defects in the code I'd welcome the feedback.
They all start laughing. I do too but in my head I'm like "wtf, I ask for feed back and you laugh? That's."
It's been bothering me.2