http://influencehacks.com/why-i-desperately-needed-to-learn-to-code

This is a blog post that seems to be in response to that. I believe the lessons learned listed in this blog post are worth more than the whole debate about learning to program or not. 

I like the list. I like the perspective gained. I wish this was more pervasive.

Regardless it’s a rather clean and simple setup. The rhc client is nice and it’s extremely cool that the project starts with a template (at least the Node.js application I created did). The project template has README files documenting available cartridges and hooks for build/deployment cycles (nice touch).

I’m a big fan of Heroku. I have an account there too. Now if I’d only build applications to host on each of them

Seems to me it would be cool to a name like “Polyglot Virtual Machine”.

To further complicate things, web browers (Chrome / Firefox / Opera / Internet Explorer) all treat the rules of CSS differently. Even though there are standards written on what should happen for certain features and constructs, they still each have their own nuances. Seemingly simple things like rounded-corners are handled differently by a few of these browsers.

Now you can reverse that paradigm: Hitch

Right now browser vendors (Google / Microsoft / Mozilla / Apple) control how CSS works in the browser you’re using. There are utilities out there that make writing CSS easier and better, while trying to minimize these vendor differences. For example, Sass is a CSS superset in which you can write CSS with certain syntactical features and Sass will re-compile your Sass into standard CSS and specifically for each vendor’s nuances. It does not however change how CSS works, and relies on the browser’s current functionality for CSS features. There is also LESS – very similar to Sass. (These are both wonderful utilities and you should use them.)

Hitch switches the control of the web page from the vendor to the developer. It provides true functional changes via CSS, not just syntactical extensions. The way Hitch does this is through a JavaScript API that hitches onto the execution of CSS, intercept it, change it and then let it continue. Specifically it’s designed to extend the CSS pseudo elements and pseudo classes by making them more like filters.

An Example

Imagine you need to style the links in your web page according to an information architecture where the nested level of the link’s URL path is important. For example the URL path /2012/05 is important because it represents a month and /2012/05/05 is important because it represents a day. The markup for these is very simple:

<a href="/2012">View 2012</a> 
<a href="/2012/05">View May</a> 
<a href="/2012/05/05">View May 5th</a>

With standard CSS there is no way to apply a style based on the path nesting. But with Hitch there is:

/* links with /-- should be black */ 
a:-links-local(0) { 
    color: #000000; 
} 
/* links with /--/-- should be blue */ 
a:-links-local(1) { 
    color: #336699; 
} 
/* links with /--/--/-- should be gray */ 
a:-links-local(2){ 
    color: #333333; 
}

With the Link Pseudo Class filters you can specify a style for any number of nested paths and even base the style on whether the path is local to your web page or external. The CSS rules are subtly different (but still very standard) while the functionality is extremely new and currently not doable without Hitch.

Not only does Hitch come with a few built-in features like filters, widgets and constants – it is also extensible by you. And this is where it breaks the current paradigm:

Now you can control your CSS functionality and not be bound to a vendor.

Note: Hitch is a rather new project. It has amazing potential and also a few things yet to be built. It’s open sourced and available on Github: https://github.com/bkardell/Hitch/. Fork it. Change how CSS works!

Parsers

There are tons of parsers out there. And frankly the field is quite big. But honestly I’m pretty humble about my expectations. I created a project called Peggy.js and I hope to get some activity in that library. I’d like to be involved in the many web projects out there that require their own grammar/parser. What I’m learning so far is that nearly everything in software development is some form of parsing (more than one might imagine). And it can be very difficult.

Sentiment Analysis

Sentiment analysis is another field that is rather big and actually becoming quite popular (or trendy I suppose). To be honest, I’m not even sure that the field has a name like that. It’s basically the study of emotion/attitude/opinion in content users submit to web applications. At least that’s my definition. Essentially I’m interested in the Front-End perspective. How do web/mobile applications handle sentiment analysis? Is there a way to do so on the Front-End that will add better user experience? Or is it really only suited in the post-content-submission perspective. I’ve started (I use that term very loosely) 2 projects for this. One in Ruby and one in JavaScript: Sentiment.js and Altimeter. I’m really hoping to capitalize these projects as not only learning experiences, but potentially career altering opportunities.

I have a ton to learn. I’m very interested in these things. Hopefully something will come of it.

When you’re a kid you plan on big things. You believe in big ideas. Some time later you give up on a few of those. Then as age creeps up on you, it starts to remove the gloss on those shiny plans you had.

It’s so obvious, and yet very hard to really accept. Plans are meant to be broken. You just can’t control life. Fate or higher power, call it whatever you want, just understand it’s not you.

Willie wrote once: “We are not in control. And that’s Ok.”

If you let plans slip, and allow it to be Ok, life is much easier to understand. Otherwise you can waste a lot of time being frustrated and confused.

This week a one or two things didn’t go as planned and it caused me a lot of stress and frustration. My patience got really thin a few times. But I can look back to this week and be happy, because while my plans changed my life didn’t.

And that’s Ok.

Twitter moving to the JVM more and more

The important part of this presentation is about the virtual machine and it’s performance/scaling. Not the language. In fact if he never mentioned languages at all the presentation is still valuable.

This is more tricky than might be imagined. It’s a gallery of modules. It’s a development environment. It’s a hosting environment. It’s a core library. And not always in this order.

It’s exciting stuff to think about. And it’s really cool to think about doing it with JavaScript (client and server sides). A few things that cause concern are the definitions of things.

• What is a module?
• What is a component?
• Is there a difference?
• Or are components applications?
• What does “development environment” mean?
• Does hosting mean you get what you get or does it mean you can get what you want?

It’s answers to these questions that are critical in designing a system like this.

Fun stuff.