Category: Articles (Page 205 of 258)

Personal opinions and how-to’s that I’ve written both here and as contributions to other blogs.

Should Products Have Landing Page Consistency?

February 10, 2014 / Tom / 0 Comments

Last week, I did a “soft launch” for the upcoming release of Mayer. “Soft launch” may even be more of an overstatement. Honestly, it was nothing more than a tweet to the landing page that I setup to prepare for the launch.

By landing page, I’m not talking about the type of pages that basically announce that a product is coming and that [may] attempt to collect an email address for when its ready.

Instead, I’m referring to product landing pages that detail the product and provide calls to action for purchasing the product, how to find more information, and/or that details features, and all of that fun stuff.

But as I’ve been thinking of additional projects that I hope to release throughout the year, I’ve been thinking about landing page consistency for products across a given brand, and how much it matters.

My Day-To-Day: Lift App, Part 2

February 7, 2014 / Tom / 0 Comments

This post is the final part in a two part series. Be sure to read Part 1.

At the beginning of January, I shared that I was going to give Lift App a trial for about a month, and then see how well it integrated itself into my day-to-day routine.

Specifically, I had set aside four goals that I wanted to accomplish over the next three weeks (which have since passed), and then I was going to see how well I had stuck to the goals, as well as how well Lift App actually worked at getting me to stick to my goals.

So the result?

A Rule of Thumb for WordPress Partials

February 6, 2014 / Tom / 0 Comments

For anyone who has worked with WordPress on some level, you’re likely familiar with the concept of templates.

In the context of WordPress, templates are the files in which information retrieved from the database is rendered. In other frameworks or platforms, they may also be called templates, but are also often referred to as views.

But for anyone who has done enough work with building web applications, you know that as much as we like to build reusable components on the server-side – be it functions, classes, or whatever else – that we also like to do so with client-side related code, too.

Markdown Syntax (And Developer’s Tunnel Vision)

February 5, 2014 / Tom / 0 Comments

As far and and as exciting as text editing can get, one of my favorite introductions into the space in the last decade has been Markdown.

I remember the first time I read about it, I loved it – it was essentially simplified markup – and the first time I used it regularly was when Stack Overflow launched.

Then I began to write my text files using the format even if the tool didn’t support formatting because it help to make reading the text file that much cleaner (besides, sometimes word processors are just overkill, aren’t they?).

Notes for Mayer in Markdown

Then other development-oriented sites began implementing markdown parsers into their site much like Stack Overflow did when they started. For developers and others who enjoy writing in markdown, it’s been a really cool ride.

With tools and services like:

I’d say that markdown is more prevalent than it’s ever been.

And although I’m someone who clearly is clearly a fan, I can’t help but think that developers are developing a bit of tunnel vision as it relates to a way for everyone to write.

The Best Programming Language, Tool, and Technology is Here!

February 4, 2014 / Tom / 0 Comments

I think one of the biggest challenges that developers face – especially new developers – is this feeling of having the keep up with the newest, latest, and greatest technologies that come out almost monthly (if not weekly), and the guilt that follows when peers attempt to “hold them accountable” (for lack of a much better phrase) for not knowing or not using something.

Now, for the record, when it comes to the technologies that people opt to use for their projects, I don’t really care – to each his or her own. Whatever makes you more productive and gets you solving problems faster, then awesome.

Sure, there’s something to be said for a team using a unified set of tools, but that’s content for another post.

Generally speaking, can’t we stop with espousing every latest-and-greatest language, tool, framework, whatever as the next best thing?

Because it’s probably not.