|
When learned statistics at the university we had a data mining language at the console (I can't remember any name attached to it), that was almost as unreadable and messy like R looks like here...
Very promising...
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
We already know that there are two dominant mobile operating systems out there. But the current situation doesn’t really allow anyone to experiment, not without going through the interests and lenses of the two dominant players — Apple and Google. Somewhere in Redmond, a Product Manager is crying
|
|
|
|
|
Probably a few guys in Finland too
How do you know so much about swallows? Well, you have to know these things when you're a king, you know.
modified 31-Aug-21 21:01pm.
|
|
|
|
|
WP8, Ubuntu mobile , Meego-Bada-Tizen , BlackBerry OS , Firefox OS....
|
|
|
|
|
I think we have a debate over what mobile OS is...Or just Mr. Horowitz missed the counting at a very early stage...
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
I conceed that OpenVMS is not a very mobile OS.
|
|
|
|
|
For the last couple of years we’ve been tracking technical debt in our development backlog. "He that dies pays all debts."
|
|
|
|
|
|
When Apple CEO Tim Cook speaks, the world listens—even if he’s speaking to a room full of bankers and other finance bigwigs at the annual Goldman Sachs Technology and Internet Conference. Wait, let me guess: he's finally admitting to being a fan and copying its look and feel (retroactively)?
|
|
|
|
|
"Tim Cook explains what he really thinks of Android" after reading I feel like that's a clickbait title...
|
|
|
|
|
/shrug All headlines are clickbait: that's the sole reason for a headline.
"Tim Cook speaks at Goldman Sachs event, discusses stuff." might be more accurate, but is also clickbait (just not as tasty)
TTFN - Kent
|
|
|
|
|
More like click-chum, there's so much of it.
|
|
|
|
|
The new API for Java SE will define a specification for common issues and behaviours shared between most desktop and embedded applications. Standard behaviour across all desktop apps? That's just crazy talk.
|
|
|
|
|
The program, dubbed "trusted source," has seen more than 6,000 false positives fixed so far, just one week after the program started. "Many hands make light work"
|
|
|
|
|
Facebook is trying to combat the threat of malware and security through collaboration. The company just announced ThreatExchange, an API-based platform designed for organizations to share security threat information.
The idea for ThreatExchange manifested about a year ago through a discussion about a botnet causing a malware attack across a group of technology companies’ services. If there is a way to make it into a social platform, Facebook will find it.
|
|
|
|
|
New research finds that the core functionality of a program is encapsulated by just a small fraction of its code. "All we are is dust in the wind"
|
|
|
|
|
Did they look at only COBOL?
|
|
|
|
|
Almost as bad - I think they looked at Java (and included all the XML configuration files)
TTFN - Kent
|
|
|
|
|
I can believe it. For every one line of code that has actual business value, I find myself writing an awful lot of lines for things like exception handling, null checking, error logging, thread locking, bounds checking, etc... None of which has any business value beyond just getting the damn thing to run without problems.
|
|
|
|
|
I'd say all of that is required to provide the required functionality.
|
|
|
|
|
Not entirely. Thread locking is only needed if you have contention problems. Logging is only necessary if you need to go look at log files. Bounds checking is only necessary when someone tries to bypass UI validation, etc...
All of these are good things to have. I put all of them into my code. But the only thing they do is relieve IT headaches. They don't sell more widgets.
|
|
|
|
|
Vark111 wrote: They don't sell more widgets
Sure they do. Uptime is directly related to sales.
|
|
|
|
|
You only need an airbag in an accident, that is true.
Logging is not just required if someone wants to look at the logs; it is required to be able to track what the application is doing. Bounds checking is not just for people trying to bypass, but also to reduce accidental errors.
The fact that it is not explicitly mentioned as something that you get paid for doesn't mean that it has no value.
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
|
|
|
|
|
I don't disagree with anything you said. The point I guess I'm trying to make is that 15 years ago, when I was writing VB6 apps before I really should have been, I did none of those things. No null checking, no bounds checking, no logging, etc...
Those apps were an abomination from my (current) perspective, but did they provide business value back then? Unquestionably.
If I were to grab one of those apps today and add all those things back in - exception handling, null checking, logging, etc... Would the business value of those apps increase? In my opinion, that's questionable. If the app used to crash twice a day because of those problems, then adding those checks and balances in probably does increase business value. But if that app was only crashing once a year?
|
|
|
|
|
Vark111 wrote: But if that app was only crashing once a year? A few years ago, cars came without said airbag. You don't even need to be able to lock the car to provide the basic functionality.
Does it matter if it crashes once a year? Well, no, I hear that cars are called back all the time. As long as it isn't my car, all is great
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
|
|
|
|