|
David Crane, designer of Pitfall for the Atari 2600 gave a talk at the 2011 Game Developer’s Conference. His 38-minute presentation rounds up to a full hour with the Q&A afterwards. It’s a bit dry to start, but he hits his stride about half way through and it’s chock-full of juicy morsels about the way things used to be. Pro tip: jumping on alligator heads is not advised in real life.
|
|
|
|
|
Armed with Kendo UI DataViz, I felt compelled to share information with folks in the developer community about a growing concern of mine; the weight of web pages or, what I like to call "webpage obesity". In terms of bytes-on-the-wire, the Internet is getting fat. Quite fat, in fact. For example, did you know that an average webpage is around 1.4 MB? Not surprised? You should be. "But, why should I care?" you may ask. The reason is simple: performance. I like big DOMs and I cannot lie, you other devs can't deny...
|
|
|
|
|
In the 1990ies, 14400 bps was a good speed - try to load such fat pages with such a line, and you'll have to wait some 10 minutes.
And by the way, the content of current web pages is often less than 1000 characters - i.e. a 1000 times more than the content is used for design purposes.
|
|
|
|
|
Microsoft will make available as part of its upcoming Windows 8.1 "Blue" release of Windows client the rumored Outlook 2013 RT mail client, company officials confirmed on June 5. Microsoft's Chief Financial Officer of Windows, Tami Reller, made the announcement during the Computex show in Taipei, claiming that Office RT is a top business and consumer feature request. You've got [touch, swipe, pinch] mail!
|
|
|
|
|
Ever wish you could talk to your dog? Understand what’s bothering him? How much of the time she paces around when you’re not home? Whistle, a startup that makes a wearable tracking device for dogs, wants to help. This summer, it plans to start shipping a $99.95 metal disc that affixes to a standard collar, and promises to go for 10 days on a single charge.... Owners can then chart their Whistle-wearing dogs’ daily minutes spent walking, playing and resting, as detected by an accelerometer and displayed on a free Whistle iPhone app. My master made me this collar. He is a good and smart master...
|
|
|
|
|
This paper concentrates on the development of the basic ideas and distinguishes two periods - Summer 1956 through Summer 1958 when most of the key ideas were developed (some of which were implemented in the FORTRAN based FLPL), and Fall 1958 through 1962 when the programming language was implemented and applied to problems of artificial intelligence. After 1962, the development of LISP became multi-stranded, and different ideas were pursued in different places. John McCarthy's classic 1979 (history (of (Lisp))).
|
|
|
|
|
I prefer the version from A brief, incomplete, and mostly wrong history of programming languages:[^]
"1958 - John McCarthy and Paul Graham invent LISP. Due to high costs caused by a post-war depletion of the strategic parentheses reserve LISP never becomes popular[1]. In spite of its lack of popularity, LISP (now "Lisp" or sometimes "Arc") remains an influential language in "key algorithmic techniques such as recursion and condescension"[2]."
|
|
|
|
|
Bad Developers Should NOT Use Frameworks
The sad part about this article is that the people that actually need to read this won’t. Why; because they simply don’t care about what they do. It really is the honest truth. Nonetheless, I will courageously continue writing in hopes that the good developers will magically convey this message to the people who need to learn it!
This totally hits the nail right on the head!
|
|
|
|
|
Bad developers shouldn't develop, regardless of whether they use a framework or not.
Marc
|
|
|
|
|
It depends on "why are they bad?". Someone who still learning will make some mistakes (everybody has done some poor and ugly coding).
The big problem is when things are bad and the developer don't care or don't review his (or her) work.
|
|
|
|
|
Diana NoWay wrote: It depends on "why are they bad?". Someone who still learning will make some mistakes (everybody has done some poor and ugly coding).
Exactly, a bad developer is one who doesn't care and doesn't learn from mistakes. We all make mistakes, you should see some of mine!
Marc
|
|
|
|
|
Mistakes do not make you bad. Everyone makes mistakes or even writes code that won't work as envisioned.
I've had to work with some really bad programmers, although mostly it seems I get to follow behind them and clean up their messes.
What's a bad programmer for me?
One that doesn't even understand what they are writing. I was given some code this programmer had written before he went on vacation, he swore up and down that he had tested it. Didn't come close to working. I gutted it down to 1/3rd of its original size and when he got back from vacation I showed it to him. He didn't even see where I had made any changes.
Another one thought if the program crashed, it was the user's fault.
But the worst for me have been the ones that convince management they are God's Gift to Programming ard produce something that barely works and then moves on, leaving me to seemingly whine to management about the crap code and how resistant it is to even simple changes without crashing the entire program. You know, writing a subroutine that does 10 things and then call it because you are only interested in 2 of the things it does and you hope the other 8 don't step on anything important.
Sorry, I'm getting off on to a rant that could go for pages.
To me, the only advantage of a bad programmer is that they teach what not to do.
Psychosis at 10
Film at 11
Those who do not remember the past, are doomed to repeat it.
Those who do not remember the past, cannot build upon it.
|
|
|
|
|
Seems like the argument is "bad developers shouldn't use frameworks, because bad developers don't use frameworks". 
|
|
|
|
|
Good developers shouldn't use frameworks either.
|
|
|
|
|
Yes, good developers do not need Frameworks !!!
|
|
|
|
|
I'm sorry. This is an incoherent rant.
|
|
|
|
|
Bad developers should also never be allowed to BUILD frameworks. I've experienced the outcome from this first hand. It was horrifying.  
|
|
|
|
|
|
LOL, been there! I once worked with a guy who was obsessed with frameworks, he wrote an in-house one that was critical to our business. Only, he never finished it, or any other project he started. It was a horror show of method stubs and debugging code and commented-out changes, and this was in production! He refused to fix any bugs or complete needed functionality, considering that someone else's job, so the other programmers were forced to work around the problems or make the fixes themselves.
He also liked to use frameworks for totally unnecessary applications, like for a simple SFTP client to pull an import file, a tool I was once forced to use. It was a ridiculous error-prone mess with objects being passed through seven layers of hell when there was no reason for abstraction in the first place. I ended up removing the reference to his code and just wrote some simple reliable code to do the basic SFTP pull (I suspect that he wanted me to use his tool so I would get tagged with ownership and maintain it for him--not it!).
As for the article, though, I'm not sure what the guy was getting at. Frameworks are tools, it depends on how they are used. That's true of all tools in programming, including the languages themselves.
|
|
|
|
|
Incoherent argument. What was the point? I've read a few of this person's posts and after reading them I'm always left with the feeling that they must be terrible to work with.
|
|
|
|
|
This is a useless argument that is there just to boost the author Adds income.
If one is a bad professional he shouldn't be doing it, period!
But life isn't as simple as this and we all know how it goes and we have to live with it.
Everyone at least once looked at he's own code some months later and thought:
"S**t! What was I thinking when I wrote this?!"
Architects
Here we're speaking about developers, but these are far from being the one that really weight on bad software at the end.
For me, bad Architects (or the lack of a defined architecture) can damage much more than a bad developer.
On top of the damage, a bad architecture is much harder to rollback than just a piece of bad written code.
Project Leadership
Bad of lack of project leadership leads to bad developers "perception".
You might be a good developer but if you don't have the right info to work with you might end up writing bad code and not even knowing it.
Frameworks
There's a lot to say about this but bottom line is that Frameworks are never the problem.
In fact they help to encapsulate logic that most of the time we would end up writing anyway so what's the problem?
The problem is the same as Googling and Copy/Paste. Using them blindly, without caring about what they really do underneath.
Of course, at the end it's easy to blame who actually stroke the keys and code the damn mess, but I've seen much more crappy software than crappy developers and this should mean something...
Cheers!
|
|
|
|
|
AlexCode wrote: Frameworks are never the problem.
I would beg to differ but MFC doesn't provide a way to do that with making a fool of yourself. 
AlexCode wrote: Using them blindly, without caring about what they really do underneath.
Agree 100% but of course this can only be solved if the framework itself is transparent, open source and well documented.
I do framework development because it's hard and therefore a good way to learn. 10 years and I'm still learning exactly how hard it is. 
"The secret of happiness is freedom, and the secret of freedom, courage."
Thucydides (B.C. 460-400)
|
|
|
|
|
Based on this article, I'd say bad writers shouldn't use blog engines.
|
|
|
|
|
Framework that can be used only by expert developers is probably not so good
|
|
|
|
|
The same goes for API's...
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
