We have to take 8BIT big time cuz I really want to see Ryan Reynolds, Ashton Kutcher, Ryan Gosling, and Ian McKellan act out this TXT message on the big screen one day.
Early last week, I was having a conversation with a fellow tweep about our Press Start events during which he raised the question:
So I thought you guys were a WordPress shop?
At that point, I asked him to define what he considered to be a WordPress shop and replied:
Primary tool that you use / favorite development platform.
Bingo – good answer, right?
But I think he raised a valid question in asking about how Press Start fits into the overall business of what 8BIT is all about.
Considering the fact that earlier this month, we said that Standard 3.3 would not ship until WordPress 3.6 launched, this may come somewhat of a surprise but we’re officially proud to announce the release of Standard 3.3!
But with the recent drop of WordPress 3.5.2 and the uncertainty of when 3.6 will be released, we decided to review the roadmap, revise what we had plan, table some features that will be new in 3.6, and then bring some new features in that were tabled for a later release.
With that said, here’s what you can expect in Standard 3.3…
I can fall asleep anywhere within six minutes at any point whether I intend to or not.
When it comes to writing software, one of the things that we often use and refer to is the idea of “dependencies.” Dependencies are parts of the code base that depend on another set of code to get its work done.
Obviously, this isn’t unique to software – there are plenty of things in the real world that can be considered dependencies:
- A car depends on gasoline (or batteries, now) to run
- A television depends on electricity to get work done
- We depend on oxygen to breath
Simple stuff, right?
But what’s the hold up with Standard 3.3 and what do dependencies have to do with this? Continue Reading…
Given what we’ve shared on our about page and various blog posts, it’s fair to say that we – like many of you – are digital natives. We spend a lot of time online, and we do so for both work and play.
One of the things that we’re often asked about in email, on Twitter, or at meetups is how to blog frequently, code frequently, design frequently, or do whatever frequently. The truth is, there’s no single right answer to that, but there is something that everyone can do that helps make those things easier and it’s a bit of a paradox.
Simply put, get offline.
According to the WordPress 3.6 project schedule, WordPress 3.6 is slated to be released at the end of the month.
Exciting, isn’t it?
Perhaps one of the neatest things coming down the pipeline for this particular release is the revamped Post Formats user interface:
For those of you who have used Standard for the past year (or several years, at this point), you know that we’ve long been a fan of Post Formats, and have done our best to make sure that we not only support them but also uniquely style them within the blog.
Standard 3.3 is also slated to be released this month, and we’re doing what we can do make sure that it’s going to be compatible with both WordPress 3.5 and 3.6.
I don’t always save money, but when I do, I spend it.
Because Standard lives in two marketplaces – that is, in WordPress.com and WordPress.org – we have to change gears each quarter to address bugs, introduce new features, and generally continuing updating the theme to match the demand.
It’s a fun problem, for sure.
As of today, we’ve made our official commit for Standard 3.3 For WordPress.com!
The majority of the people on this team have spent a significant portion of their careers thus far working as developers, managers, or some other type of executives in larger companies.
This has been a Good Thing™.
At the very least, at has helped us to identify what the like and what we dislike about where we’ve been so that we’re able to begin building a company and a culture that brings the best of our collective backgrounds, while leaving the other stuff behind, and ultimately introducing our own spin on stuff.
Despite the fact that it’s very easy to hate on corporate policies or processes, the truth is, some things are there for a reason and when implemented correctly, provide a lot of value to the company.
All that to say: We’re not a team that sits down, identifies what it is that we’re going to do, and then goes off using our own tools and processes to implement it.
That’d be chaos and as much as fun as that sounds, it’s not exactly how I want to build a business. So with that said, I thought it might be neat to show some of the the stuff that we use that goes on behind the scenes when building our products.