Great thread What do software engineers who work at a large scale understand that other developers don’t? at /r/programming
Since major overhauls to a web site are relatively infrequent and set the stage for years to come, they are rare and vital opportunities to step back to basics. What should the site be? What should it express? Who is it for and what should it do for them?
MindBody is a web-based management system widely used by yoga studios. Using MindBody’s SOAP-based API, eeMindBody provides an easy way for a studio’s ExpressionEngine web site to access its MindBody data.
The inaugural State of SaaS Report.
In trying to improve the performance of an ExpressionEngine-powered web-based system, I came across the following database fields within MySQL query WHERE clauses that therefore should be indexed but aren’t:
- exp_actions: class, method
- exp_categories: cat_url_title
- exp_ce_cache_tagged_items: item_id
- exp_channels: channel_title
- exp_channel_fields: field_name
- exp_extensions: enabled, hook, priority
- exp_fieldtypes: name
- exp_members: in_authorlist, screen_name, username
- exp_menu_items: sort
- exp_modules: module_name
- exp_playa_relationships: parent_is_draft
- exp_plugins: is_typography_related
Every little helps.
Smoother CSS shadows by Philipp Brumm. Simple; excellent. [via CSSTricks]
Matt Layman’s handy Failed SaaS Postmortem — too much tech tinkering; I need to take heed. Plus it’s great he’s getting right back in the saddle.
A deep dive into the newness of the iPhone 11 camera at the Halide blog.
Gadget: 1. Survey [PDF] is a cool history of software milestones “from Smalltalk to Minecraft” Chaim Gingold (2017). When you see these things collected you realize how much progress they collectively represent. I wonder what we’d have been doing otherwise…
Volvo unveils its first full battery electric model, the XC40 Recharge SUV with 402bhp a 248-mile range. Featuring no front grille!
A deep dive into the Grand Seiko Snowflake on Hodinkee. “The entire thing seems to have been calculated to create an effect of serenity without boredom; of minimalism without sterility.”
As well as smarts, what really makes a successful implementation likely is experience.
rmed with a plan for the back-end, the rubber hits the road with the installation and configuration of the system chosen for the project.
Each system of course has its own way of doing things, and developing a plan on paper into an actual working system is always a bit of an act of translation. The likelihood of a successful realization of a plan within a particular system is increased mostly by one thing: experience with that system (smarts notwithstanding).
Engaging.net’s experience is with ExpressionEngine — as users of its predecessor, pMachine, we’ve been using EE from the moment it was released.
With EE, the system itself needs to be installed, as well as the software it rests on (see the ExpressionEngine Requirements page). Then we can install and configure the add-ons and build out the channels, fields, categories, statuses and member groups.
The entire process, with dependencies