Re: Wear the mask
Yeah, I've got 2 phones - my old Blackberry Classic and the MS Lumia 650 I updated to when prices dropped at the start of this year. Which of those should the government track?
1296 posts • joined 3 Jul 2009
Licensing is one of the constraints that goes into a systems operational architecture. I have seen developers include relational databases in containerised solutions but to me this should be tiering issue, any persistent data that requires ACID compliance should be in a self contained tier and if cost is your objective that makes more sense to be on a physical cluster or a dBaaS. Non-persistent data and application configuration is better off on an OSS data store and probably non-relational so stick it in the container. the nightmare is when you have to containerise an older application, because you don't have time to fix it properly, and then scale horizontally but consider MS licensing as being a fine on bad behavior then.
I don't think you know who GTS is - it's the descendent of IBM Global Services in the same way BCS is the descendent of PwC Consulting after the sorting hat of 2003.
They've been cutting costs by cutting experienced staff ever since and losing revenue by cutting experienced staff at the same time.
Agree - when my tablet/convertible broke I stuck a small Linux distro on my eeePC701 and it let me Citrix into the office whenever I needed to show online presence from the airport lounge. The sweet spot is probably 8"-10" especially if the display is edge to edge without bezels. I did try an 8" Fire tablet with a Bluetooth keyboard case but that didn't work as smoothly.
As this is definitely an 'at need' device, I'd be curious about a Psion Revo style device (maybe larger but jacket pocket sized at most) with a USB-C connection to my actual phone which just serves as UI, relaying screen and keyboard and not doing any actual processing or storage. That would have a lot longer lifespan as it could move from phone to phone as I upgraded.
I actively have to damp down my own love of new and shiny tech and techniques to remind myself what we're actually trying to do. Why is the new approach better than using something off the shelf? Why choose a technology where you need to pay premium for niche skills rather than premium for experience? If you can't answer that why to the satisfaction of all your stakeholders then stop.
Otherwise you're just blockchain.
Do a search for "Melrose","Unihertz" and "i9s" to find a few and then spin off from there.
There are still a few small phones. I haven't yet found one that ticks all my boxes (4g, NFC, fingerprint, 16:9 display, <100g) but I'm hopeful.
I remember, about a decade into my IT career, being taken aside by my manager, a born consultant on the track to junior partner and being told I needed to be less cynical. Unfortunately I'd been told 5 years before that by someone more senior and who had earned more of my respect that if I wanted to get ahead I needed to be more cynical. They were both probably lying.
This is some nice background but has the author actually held the phone and used it?
I'm intrigued by KaiOS (and open source GerdaOS) but what I've read about devices using it so far is negative, mainly on usability factors like button press, navigation, readability of displays, etc. For all I know Energizer may have put in the time to fix all those, if so please include that in the article.
"The core issue seems to be that it is hard to do microservices well."
I've certainly seen them done badly multiple times in multiple places, since that seems easier. Then there are the changes of mind, are the services accessed directly, via an API gateway or via an ESB. Why not all three? Why not change your mind half way about which API gateway? Once the microservices are distributed then it's almost impossible to reuse them so lets develop multiple ones doing the same job and flip a coin which to use. Then lets do a version upgrade...
If your problem isn't the problem that microservices are intended to solve then why, aside from religious conviction, use them?
Maybe once upon a time that happened but it sounds like a fairy story to me.
Software selection was done by writing a requirements document. It would be very detailed on the bit the people writing it knew and kind of vague on the rest. It would add some operational requirements that varied from absent to aspirational to impossible.
Every vendor then said they could meet all requirements in full. If not in this version of the software then in the next, probably and certainly by configuration rather than modification. The buyer would then ask for demos and customer references and would see a mock up and read about some customers using an unrelated product from the same brand. Coins would be tossed, drinks consumed, trips to vendor conferences taken and the product that was in the magic quadrant would get the nod, even if completely unsuitable to the job at hand.
The salespeople got their commissions and leveraged them into a promotion or a change of employer and then the delivery team arrived, read the contract and began cursing....
Have you fallen asleep yet or should I continue?
It's always the support. Those legacy systems aren't a problem because they're old or because they're slow, they're a problem because the hardware supplier has end of life'd them, the OS won't get any more patches and the last person in the company who understands the software is due to retire in 18 months.
Good plan. In fact that should be made a condition of trade talks with the US. It's important the UK demonstrate to the US they are “sovereign equals” and will need to play by British rules. I'm sure Facebook, Google and Amazon will just roll on their bellies once they see that stiff upper lip.
I'm just curious what qualifies this as a phablet rather than a phone?
I agree the screen is big but so are those of pretty much all competitors that El Reg calls phones.
I would actually love if someone came out with a phone with 18:9 or 21:9 display ratio in the same form factor as my old Sony Xperia Ray - call it 53mm wide for about a 4.4 screen size.
Biting the hand that feeds IT © 1998–2020