Not for today

In high school, my friends and I went to the movie theater almost every weekend, usually not even knowing what was playing, and decided how to spend our $5-10 when we got there. We knew it would buy us a few hours of entertainment, and we knew that most of the movies would be mediocre, a few would be horrible, and a few would be great. The predictability and low cost of these outings gave us a reliable way to be entertained on a regular basis.
One of the reasons the iOS App Store is so successful is that app-buying has become a form of casual, routine entertainment for iPhone and iPad owners.

Clever article on what will become to be a developer in a future ; quite like an entertainer, you see. Great. Read it , here; complete article by Mr. Marco Arment .

Making Good Software

Alberto Guitierrez is a spaniard living by programming in Ireland.

Recently, I have discovered his blog, kindly entitled “Making Good Software”; where he writes about software development theory, considered as a harmful one.

A nice subject, and also a recurrent of mine. First to say, I am not a full-time software developer, neither a simple developer, but an old cat who knows how to develop and code.

Being myself aside the field of daily development, I really enjoyed his views and matters. Quite positive and pretty well-minded. Worth a read.

In case you become too lazy to look this author by yourself, I place below, some fav of mine articles written by him.

The Dawning of a New Era

Five years ago, some of us, battled against a giant wall that surrounded the world of human communications.

Because of  abackground as a developer of concepts, reading and being inspired some texts written by web and design visionaries, it was realized by us that the mass media at that time is to change radically.

According to some, "distorted reality", but not easy for new programmers and designers understand how one had to bear smiles and looks contemplative when I was proposing then, back in time, a sort programming languages that, today, allow humans and machines communicate.

In three years we have seen made true what some of us knew a decade ago.

As a simple example to you, my dearest reader, I remember one of my intense battles working within the IT department of a large Spanish company; trying to create a logical way to present a project through the network, using for it tools we know today as common as Apache, PHP, XML, RSS ...  the need of a tool,

Placing 'the user in front' instead of the developer and the bureaucracy...

I remember myself trying to - with limited success - integrate that  IBM precious monster named Lotus Notes, so present at that time in enterprise-based solutions in Spain, with the nascent languages and technologies... A kind of prototype that showed we were able to generate a web page with the help of open-source libraries and language. More human, more readdeable. Presenting a cross-content, allow the normal user could work in network, to follow the standards preached from the same industry. I failed then, and that marked, somehow my career.

We lived in a closed communications ecosystem, ill. An ecosystem - as I understood it then - would become part of our everyday business activity beyond what the Information requested and offered its servants, say the IT personnel.

We live in a different world today, ten years later, but some people still has not understood it.

Complexity kills. Complexity sucks the life out of users, developers and IT. Complexity makes products difficult to plan, build, test and use. Complexity introduces security challenges. Complexity causes administrator frustration.

Read the entire article of Mr. Ray Ozzie here

On Web Design

After all, Twitter is really an internet service, not a website

This sentence clarifies the mistakes some clients do, when asking you for a software application that offers and does more things than a web-site is capable to offer and is planned for. Use it, in case of trouble. Some clients do not deserve less.

Via Zeldman.

The Visual Designer’s Experience

JavaFX syntax is based on CSS3, but they have customized some of the properties for our needs

One of the changes, you can see here, is their addition of the prefix “dash-fx-dash” to all the property names.

Just A Tree?

The default OReilly.com style does not like tables, so it may be preceded by some whitespace: apologies.

Read the complete article here.

On Graphic Design

; rectangle constructor
; combine a point, a width, and a height
(define (make-rect a w h) (cons a (cons w h)))

; rectangle selectors
(define (rect-width r)
(car (cdr r)))

(define (rect-height r)
(cdr (cdr r)))


Via BillTheLizard

Newer Posts Older Posts Home