3,343 karma · joined September 12, 2011
I wonder how we'll look back at all of the people currently proclaiming that they are, in fact, trying to change the world..?!
It's quite easy to get the basics up and running but quickly becomes tricky getting all of the messages to display consistently. Then you can add embedded images and attachments to the mix. The list goes on and on. But, you really will learn a lot about protocols, parsing text & binary data, working with legacy formats and just all kinds of interesting stuff. Even if you don't wind up with an amazing client, it's still a lot of fun!
Every time I see "google calendar" in our issue tracker, I die a little inside.
The QA department, then responsible for testing this new "feature" will most likely go off of a script that was sent to them by the developers to verify the old and new behavior, going on some metric that perhaps they don't really understand.
In some cases, the QA may actually have to rely on a tool actually built by the developers to test the feature. So in some cases the QA, not being software developers and not responsible for actually reviewing the code, will have to somewhat go on faith that the scripts and tools provided by the developers are accurate.
I'm not saying that means the engineers were responsible at VW, but it does explain how something could slip through the checks-and-balances that have been set up.
If this was a tech-only forum then the business guys & gals probably wouldn't even be welcome, & vice-versa if it were a business-only forum. It's an interesting mix here that probably wouldn't normally have a lot to talk about together. But I do think it puts stars in a lot of programmers eyes who might not otherwise care about that kind of stuff.
Mozilla likely submitted the app a couple of weeks ago and just hit the release button today.
It was extremely difficult because the software was written over a long period of time by multiple generations of programming teams and programming styles. It was hodge-podge to say the least. Take that system and integrate it with another equally hodge-podge system. Then add a couple more hodge-podge systems to that. There were just lots of redundancies and disconnects. I did feel sorry for the people who were going to have to use that system.
I'd say that medical administrative software is ripe for "disruption" just because it sucks so badly. Except for the fact that the systems are a) huge b) require extensive domain knowledge c) are regulated d) sales of such systems are extremely political and e) there's no way to do an end-run around the administrators who are purchasing these systems. It doesn't seem very suited for a "move quickly and break things" scrappy startup.
"I skipped breakfast today. I'm starving."
If you are truly uncomfortable with these sentences then it's possible that you are either a bit overly sensitive, or else you have trouble differentiating between literal statements and common english expressions.
It strikes me as similar to how .NET is cross platform. Command line apps will run, but anything with a GUI would have to be written with a cross-platform UI kit.
But to try to say that x++ is complicated to understand? It's no more complicated than a lot of operations. I don't think anyone would intuit what x%2 means either. There are things that you can get just by looking at it, and others that you just have to learn once, then you go "oh, that's what it does" and move on.
But, at the same time, they keep users upgrading at the same relentless pace and so you generally don't need to worry about supporting 10 year old versions of the OS.
Cuts both ways I guess!
Google glass, on the other hand, seems in my observation to have launched with about 25% cool factor and 75% dorky, show-off, elitist kinda vibe to it. It devolved from there.
Despite Apple's reputation for coolness, the watch seems like it's at about 50/50 on the scale at best. I love technology and probably have a reputable score on the dorkiness scale myself. But, when I see Apple watches, they even seem a bit much for me.
Finally, one day I accidentally triggered that annoying error by doing a specific sequence of things and then clicking the browser back button a few times, then doing another specific sequence. That was a day of celebration!
I found the dark themes to look great with certain, staged screenshots. But then when you use it, the scrollbars are blaring white. Or the bar that shows your code blocks can't be styled (controlled by the OS). So you wind up with a mostly dark theme that has 2 or 3 blaring, ugly, mismatched elements that defeat the purpose.
Styling the editor window is something I've spend days tediously trying to tweak a nice pastel color pallet (that pretty much every app with a dark theme uses). But all the included ones are bright neon colors or just radically weird color choices. I've been able to get my code window 95% the way I'd want, but then all of the other windows like the explorer or the console don't match! The settings are all over the place and sometimes take a restart of Eclipse to if you got the right setting or not.
Basically I just gave up with the dark theme because it seems there's no way to get it consistent.
Even still, the outcome for most businesses is failure. And I'd assume you are correct that fashion is probably one of the more fickle businesses.
The skull, perhaps was just having some fun, though!
I probably don't have to mention who got that alert while working one day. The president of the company, of course! Luckily for me it was not a customer-facing function & they found it funny.