|
Quote: Student: My code isn't working. Can you tell me what's wrong with it?
Teacher: I'm not psychic! I need more information.
Can you answer these questions as best as you can, first?
1. What makes you say your code isn't working?
2. What did you expect your code to do and why?
3. What did your code do instead and how do you know?
Student: <fails to answers questions effectively >
Sutdent: Plz Halp!!
Ohhh, I see what's wrong!
Teacher: Imagine if you had a habit of asking and answering these
questions yourself. Half the time you'd solve your own
problem and the other half you'd be able to ask a much
more specific question and get relevant help more quickly.
Student: I totally agree.
Student: Gimmie the codez! It's urgentz!!!!
FTFY
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, waging all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
--Zachris Topelius
Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies.
-- Sarah Hoyt
|
|
|
|
|
There’s been a lot of hullabaloo lately about the state of test driven development (TDD). It was the best of tests, it was the worst of tests
|
|
|
|
|
Software development is still just so much voodoo. I wonder why we can't actually create a legitimate discipline worthy of the term "engineering" out of it.
Marc
|
|
|
|
|
Saving files to memory is something that's supposed to be mostly invisible for the end user. We don't need to think about it; it just has to work. But whether it's a solid-state or hard disk drive, conventional storage solutions have their limitations -- namely, speed, rewritability and durability. A team at IBM Research's Almaden facility in California has a cure for all of that and it's called "racetrack memory." "Memory is merely the process of tuning into vibrations that have been left behind in space and time."
|
|
|
|
|
You always hurt the ones you love.
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, waging all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
--Zachris Topelius
Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies.
-- Sarah Hoyt
|
|
|
|
|
“The good old days of personal computing” doesn’t apply to the amount of manual effort required to backup a hard disk. The process of safekeeping our data – using diskettes, the only affordable option for mere mortals – was so arduous that, honestly, few of us actually did it. What are these backups of which you speak?
Ugh, diskettes. Gone, and gladly so.
|
|
|
|
|
Kent Sharkey wrote: Ugh, diskettes. Gone, and gladly so. ..imagine booting you operating system from a single 880 kb (!) floppy. A multitasking, windowed operating system.
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
|
|
|
|
|
Oh, been there, don't miss it. I was told I was lazy and extravagant when I added a second floppy to my Apple II so I wouldn't have to swap out the OS disc all the time.
Amiga? Or GEOS? Or something else?
TTFN - Kent
|
|
|
|
|
Amiga.
Kent Sharkey wrote: my Apple II One of the crazy ones
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
|
|
|
|
|
Yeah, a few of my friends had Amigas. Great machines - way ahead of the times.
Only Commodore (and Atari) could self-destruct like they did.
TTFN - Kent
|
|
|
|
|
Floppy disks were a luxury!...you should have tried saving your program from a Radio Shack TRS-80 to those tape cassettes, they sucked!...floppies were a lot less error prone, anyway.
|
|
|
|
|
Heh I wonder where (and when) I lost this little screwdriver It was quite essential at that time...
--
"My software never has bugs. It just develops random features."
|
|
|
|
|
We found it
|
|
|
|
|
Developers often pick sides: They stick to just Web or just native. It’s obvious that when users are on a desktop, they will tend to use their desktop browser to access their favorite applications. On mobile, users prefer dedicated apps for popular websites over mobile browsers.
"There ain't room in this town for the two of us."
|
|
|
|
|
What's interesting about that quote is:
1. using desktops to fire up browsers to access apps.
2. dedicated apps on mobile devices.
Where did "dedicated apps on desktops" go?
Marc
|
|
|
|
|
They were eaten by the velociraptors.
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, waging all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
--Zachris Topelius
Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies.
-- Sarah Hoyt
|
|
|
|
|
Or is it the other way around? When users are on the desktop they want apps that will take advantage of the powerhouse in the desktop hardware, but on mobile they will prefer browser because of accessability?
|
|
|
|
|
I have debated this one a lot at my current place of employment. Unfortunately, the powers that be are in a "browser only" mode. Personally, I believe in more of a "right tool for the job" way of doing things and in a corporate environment when you have users that are more than casual users, I feel the better user experience is that of a native application. With that said, I believe technologies like ClickOnce (for deployment) and Services (pick your flavor; wcf, rest, etc., to centralize logic) provide the best balance of user experience, performance, security, and manageability.
With that said there are times when a browser application is more appropriate. Just depends on the purpose, audience, security requirements, etc.
For those that feel native development is dead, just ask yourself if you would rather use Outlook or OWA? Would you rather use Google Docs for word processing or actual MS Word? For a quick check of your email or small update, possible, but if you're writing a large document with complicated formatting (or heaven forbid, your network connection hiccups), would you really want to be working in a browser then?
|
|
|
|
|
Every developer should stick to developing for the web!
(Because all my work has been coming from clients that need desktop apps ... e.g. SCADA; Kiosks; Time Trackers ... and they haven't been able to find any other experienced "desktop developers" ... heh, heh).
|
|
|
|
|
Mozilla OS has arrived, based on only HTML, CSS and JavaScript. All native app development should be killed.
|
|
|
|
|
Tcomb validation library emphasizes models as 'single source of truth' and focuses on early bug detection
There's no[de]where to hide from Node.js.
|
|
|
|
|
"In my book, models should be the single source of truth, and you should be able to derive as much as you can from them: type safety, validation, documentation, auto generated UIs.
It's about freaking time that the rest of the world catches up to what I've been doing for 10+ years now.
Marc
|
|
|
|
|
Misleading title. Node.js is not part of Javascript
|
|
|
|
|
Today, President Obama announced that Megan Smith will serve as the next U.S. CTO and Assistant to the President, succeeding Todd Park, and that Alexander Macgillivray will serve as a Deputy U.S. CTO.
I wish her good luck, she'll need it...
|
|
|
|
|
Most people think that because the data is housed by a large company like Apple or Microsoft, and that access is protected by a really secure password, that their data can only be accessed by those that the user wants to allow access to. That is a major fallacy, and this past weekend proved it.
"Gentlemen, you can't fap in here. This is The Fappening room!"
|
|
|
|