• Skip to primary navigation
  • Skip to main content
  • Skip to primary sidebar

Remember Lenny

Writing online

  • Portfolio
  • Email
  • Twitter
  • LinkedIn
  • Github
You are here: Home / Archives for 2016

Archives for 2016

Idea: Slack/Github activity monitoring

November 2, 2016 by rememberlenny

Idea: Slack/Github activity monitoring

Working for a distributed company has made me aware of an issue: employees can ā€œdisappearā€ too easily and no one notices. When employees have issues, there is no predetermined face-time to nip it in the bud. HR visits, employee gatherings, and good ol’ one-on-ones are easier to avoid. Distributed teams naturally focus attention where work is getting done and miss potential areas where employee satisfaction is not ideal.

Poor employee engagement could be pegged to a metric based on the interactions a person has per week.
I think you can solve for this without being creepy.
Its plausible that a basic observation of how users interact with one another in a public venue is a high signal for employee engagement. Using a Slack based company for example, if users are never active in any Slack channels, then they are most likely not participating in group discussions. This could be the result of many things, but for one, it could be a individuals sense of no longer feeling engaged by their coworker community.

Employee engagement viewed over time.
It is important to note that a person’s engagement could be interpreted many ways. A highly participatory user could be feel very disengaged. A non-participatory user could be very active in syncing up with channel activity, and therefore feel engaged. Based on these examples, public participation is not foolproof.
The public participation could be a strong metric when comparing a user against themselves, over time. For example, when a user begins at a company, their activity may be above normal, due to the high number of introductory engagements. As time goes on, an employee may shift into a participatory trend that resembles more alongside their overall behavior. Based on the corrected average, any significant veering away would be a event worth noting.

Commit history mapped against a user’s commit trend could surface potential employee-project connections.
The same analysis could be run on an engineering centric organization with a shared code repository. Whether Github or some locally Mercurial equivalent, the individual contributor trends could be interpreted overtime for employee-project match. For example, potential fit can be gauged based on an employees rate of contribution during certain projects.
This can be creepy from a management and HR standpoint.

User activity could signify user happiness.
To make this work, observed results should never be used for consequential results. Punishment or reward based on analysis would be counterproductive. Employees who believe their overall behavior is being monitored and tracked could feel untrusted. This form of analysis could be the cause for employees to actually feel dissatisfied.
The overall goal of this would be to catch the otherwise uncaught signals. The goal is not to monitor your employees. If something major changes, some structure should be in place to see that the a struggling employee doesn’t simply fade away due to no longer being in the lime light.

Filed Under: Uncategorized Tagged With: Distributed Teams, Employee Engagement, Work Culture

Computer Vision in commercial establishments

October 24, 2016 by rememberlenny

Security camera to scene analysis and summary insight report.Computer Vision in commercial establishments

Since the inception of the ā€œquantified selfā€ and corresponding hardware devices, I have been curious about what people are doing with the data they collect about themselves. Fitbits, Apple Watches, and step tracking tools provide individuals with insight about their physical activity. With the increase in data generated about individuals, I tend to wonder how this information translates to groups.

Hardware companies have written interesting studies analyzing the data their platforms and devices collect, but this information is restricted to the company’s chosen points of interest. Smaller establishments, such as restaurants or commercial stores, do not have the benefit of gaining insight from the increase in these data points.

I think there is an interesting way to think about the other sensors that are newly available for analysis, specifically, the sensors that have always been around, but have not been fully utilized.

Tracking trends in public spaces is now available to all

In years prior, sonar, lasers, and similar one-use sensor technologies have been required for computing the physical world with data. Tracking the traffic trends in public spaces or tracking the foot traffic in commercial establishments have previously required specialized hardware. The specialized hardware was available to cities and large commercial ventures, but again, not for smaller scale commercial ventures.

Security cameras in restaurants, cafes, and bars could be used to reconstruct scenes.Software advancements now make common use digital cameras into complex sensors. Using software that processes images, the content of an image can be quickly analyzed for recognizable objects and human behavior. Computer-vision based software can be used to reconstruct scenes using networks of cameras. This allows for common security camera infrastructure to be used for real-life google analytics like analysis.

Data gained from analyzing customers could be used to gauge customer loyalty.Human activity in a common space, monitored with a digital camera, can be used to interpret common movement into analyzable data points. Further, in commercial establishments, transaction data can extend these reference points to understand how a brick-and-mortar business operates. I assume this information would not provide revolutionary insights for a business owner, but would be a great reference over time for change in business activity. It’s reasonable to assume this data, over time, would help to foresee trends in business growth or decline.

In the immediate, this kind of monitoring and analysis is uncomfortable. I’m curious to see if our expectations and cultural norms will change with time. Already, our activity online is analyzed and used as a commercial product. The click-trails we leave behind are aggregated and used to better target ads. The search behavior, communication patterns, or social graphs we create offer greater insight into the kind of person we are than most of us would like to admit. This monitoring of behavior is something people have become both more sensitive to and less aware of.

Given the changing times, I wonder if brick-and-mortar businesses would be comfortable using their existing infrastructure to gain deeper insights in to their business. Further, I wonder how customers would feel knowing that their activity is being monitored and analyzed for the benefit of a business.

This technology is already being widely used in public places. Companies like Sidewalk Labs that offer free wifi using publicly placed kiosks outfitted with high quality cameras, which are undoubtedly being used to monitor public activity. I’m curious if this kind of monitoring and analysis would have required a different approach using older hardware solutions in the past.

Also posted on Medium

Filed Under: Uncategorized Tagged With: Big Data, Computer Science, Computer Vision, Hardware, Image Recognition

The history of art and the finiteness of human production

August 12, 2016 by rememberlenny

There is so much ART, but its actually limited. A computer could understand all of the art humanity has produced and analyze it down to its features. Color, stroke, contrast, characters, symbolism. All the symbolism that is produced for meaning can be interpreted.

Computers could understand the components that underline meaning in art. Computers have all of the historical context and relational knowledge to make connections people dont make. The internet’s resources provide all of the resources to interpret cultural value. Think about the biographical information about author. The social connections depicted in papers and history books. The cultural leaders of a time, the records of travel, the economic and social influences.

Does anyone know what field of academic study this would fall under?

Filed Under: Uncategorized Tagged With: academia, Art, art history, Digital Humanities, Machine Learning

Time as an asset in mobile development

May 29, 2016 by rememberlenny

Read on Medium Ā»

On http://ift.tt/1sVNvsn

Time as an asset in mobile development

User experience guidelines for mobile devices have become clearly defined in recent years. Developers have learned how to utilize the limits of a small screen size and prioritize content. Applications targeted at younger demographics (think SnapChat) are successfully leveraging intuitive interfaces for digital natives. There are not many impressive interfaces designed to utilizes time as a resource.
What is out there?

Read later apps touch on the idea of using your current attention to make you more intentional in the future. The notion of a bookmark lets you keep something for later, so you can return to it as needed. Services like Pocket, Instapaper, and Readability, effectively give people a infinite memory bank, where they can collect and store content they discover. This concept works well when used on mobile phones to provide access to content without an internet connection. Similarly, it can make it easy to discover content on one device, then access it on another later.

Time as a design element

Time is an important resource in designing a user experience. Resource value in screen real estate, color priorities, internet connection speed, and many other factors are already kept in mind. Time and its use for the future is not something that actively feel triggered to think about. Time, as a design element, could be used to direct users intelligently.

Current applications are constantly trying to one-up users for a little bit more time. They want to show you one more advertisement or find a hook to get you to come back one more time. Your inbox is bombarded with daily update emails, requests for browser notification access, and too many tracking pixels.

People don’t like distractions. Intentionally creating distractions is disrespecting the end user who makes a company even possible! What if platforms made a better effort at allowing their users to decide how frequently they wanted to engage? What if all the data crunching and analysis that is done to find common trends amongst high value users was used to create a high value experience for users that don’t want to spend their time budgeted for other services?

This is where using time as a design element starts to make sense.
Where it works

Email newsletters are a great to subscribe to a future time commitment for content. Users sign up to email newsletters because they like the content being produced. They are subscribing to the idea that they will get more of the same kind of content. The unspoken contract is that the email address, which is a door into the user’s attention, will be respected.

Email newsletters lose their value when the user’s inbox is overwhelmed with too many emails. Like real life mail, too much email goes unopened and ignored.

Monthly gatherings are another good example. A predetermined amount of time is being committed to a predetermined purpose, with an expectation of some predetermined experience. This is good. For a person who participates in a community, either on or off the internet, a budgeted length of time is great.

The goal here is not to come up with a system for creating a structure for predetermining how time is used. The goal is to come up with a solution for companies resort of attention grabbing.

Where it doesn’t work
The ā€œsave for laterā€ services have some basic faults.

First, when the content goes into the bookmarking service, and into the ā€œread laterā€ display, the content producers lose access to the ad impressions/tracking needed to pay for the content. This has its obvious issues for the content producers and seemingly less obvious issues for the consumer. When content producers are not getting a return on investment for their product, they can’t continue producing content. The ads and tracking itself isn’t bad, its the way they are being implemented. Right now, it doesn’t work for the user and the producer.

Second, when the rate of saving content is higher than the rate of consuming content, the saved content is forgotten. People develop habits around bookmarking and categorizing bookmarked content. Most people aren’t sophisticated enough to create a process for consuming saved content, and eventually never do. Saving content without determining when it will be consumed is DOA.

Time as a design resource on mobile

With mobile devices in particular, time is a great design resource. Since user’s are forced to interact with one piece of content at a time, understanding how to leverage the mechanics of intentional delayed engagement is important. Content should be designed with the notion that it is not going to receive the full attention of a user. That doesn’t mean that it can’t at some future time.

What would incentivize companies to adopt time as a design resource?

Filed Under: Uncategorized Tagged With: Leonard Bogdonoff, Time as an asset in mobile development

March 7, 2016 by rememberlenny

Next painting based on Ray Collin’s Seascape series painting after digitally manipulating the photo

/2016/03/07/next-painting-based-on-ray-collins-seascape-2/

Filed Under: Uncategorized

How to write Desktop-first responsive emails

March 6, 2016 by rememberlenny

Most web pages are written with the assumption that all the content is loaded, then the CSS determines the priority for styling. In emails, you have to design your CSS/class/markup base on the assumption that you can have some parts of your code NOT run.

When it comes to responsive layouts, you have to design for the case where desktop is default (without the media queries) and any media queries are added, only if its possible to run inline styles. In the case where you have things like Gmail, where the style tags are stripped out, you need to account for this.

Inliner from Zurb Foundationā€Šā€”ā€Šhttp://foundation.zurb.com/emails/inliner.html

Inliners

Most email browsers don’t read style tags. As a result, you have to write your emails with all the CSS properties as style tags in the html tag. This is called inlined CSS. Instead of writing the raw HTML with inlined CSS, there are many services or libraries for inlining a block of HTML and CSS.

The problem with email inliners, like Rail’s Roadie, was that it was inlining the media query styles that would run on mobile, which broke the default desktop layout. By having roadie ignore certain styles, we control the designed layout to render the desktop mode in all cases, and then serve the inline style tag with media queries to be run where possible.

To make things more complicated, Outlook is very outdated. Specifically, there are a lot of CSS3 properties and even CSS2 properties it doesn’t render. As a result, outlook has some legacy hacks where you can use comment flags to tell Outlook NOT to render certain content.

Basics

For responsive emails, where you use media queries, you have to keep a few things in mind.

1. The email is being inlined
2. Email browsers render CSS2 on average
3. You have some email browsers that have comment hacks (ie. outlook)

Where toĀ start

Write Desktop-First HTML andĀ CSS

Based on this factor, you have to code your emails to be desktop-first. The CSS, without any media queries, need to look good on desktop email browsers. This way, you can assume at the very least, the email looks like this:


Add Media Query for mobileĀ CSS

Considering you want to add a media query, you need to add an inline media query on the email. This is pretty straight forward for desktop rendering. For example, you would get something like this:


Setup yourĀ inliner

The problem comes up in emails, the two conditions above don’t work perfectly. For CSS to render in emails, it needs to be inlined. This means that the desktop or media query conditions don’t jive well together. This why we started with the Desktop-First css structure. One you inline your css, when theres a media query, you get this mess:


Consider your inliner to ignore media query forĀ inline

When you have a media query, the media queries CSS gets inlined, and consequently overrides the desktop CSS. As a result, you get markup that looks broken. To prevent this, you have to queue your CSS inliner to ignore the media query CSS. To do this, you separate the media query CSS in a seperate style tag and you flag it in the inliner. In the case for Roadie, thats the `roadie-ignore` flag. This way you get this:


Wrap up

By setting the inliner to ignore the media query style tag, you allow all email browsers to render the working desktop CSS. In the case that the email browser will parse the style tag, it can view the media query and optionally render the mobile styles when relevant. This is how you can have cross-email-browser functional CSS emails!


This was written as a comment in a pull request for C2, a project at 18F. We are using this responsive email structure to make our transactional emails better for our end users. We are also doing some awesome stuff. Reach out if you want to learn more.

Filed Under: Uncategorized Tagged With: Email Marketing, Responsive Emails, Web Development

  • Go to page 1
  • Go to page 2
  • Go to Next Page »

Primary Sidebar

Recent Posts

  • Thoughts on my 33rd birthday
  • Second order effects of companies as content creators
  • Text rendering stuff most people might not know
  • Why is video editing so horrible today?
  • Making the variable fonts Figma plugin (part 1 – what is variable fonts [simple])

Archives

  • August 2022
  • February 2021
  • October 2020
  • September 2020
  • August 2020
  • December 2019
  • March 2019
  • February 2019
  • November 2018
  • October 2018
  • April 2018
  • January 2018
  • December 2017
  • October 2017
  • July 2017
  • February 2017
  • January 2017
  • November 2016
  • October 2016
  • August 2016
  • May 2016
  • March 2016
  • November 2015
  • October 2015
  • September 2015
  • July 2015
  • June 2015
  • May 2015
  • March 2015
  • February 2015
  • January 2015
  • December 2014
  • November 2014
  • October 2014
  • September 2014
  • August 2014
  • July 2014
  • June 2014
  • May 2014
  • April 2014
  • March 2014
  • February 2014
  • January 2014
  • December 2013
  • October 2013
  • June 2013
  • May 2013
  • April 2013
  • March 2013
  • February 2013
  • January 2013
  • December 2012

Tags

  • 10 year reflection (1)
  • 100 posts (2)
  • 2013 (1)
  • academia (2)
  • Advertising (3)
  • aging (1)
  • Agriculture (1)
  • analytics (3)
  • anarchy (1)
  • anonymous (1)
  • api (1)
  • arizona (1)
  • Art (2)
  • art history (1)
  • artfound (1)
  • Artificial Intelligence (2)
  • balance (1)
  • banksy (1)
  • beacon (1)
  • Beacons (1)
  • beast mode crew (2)
  • becausewilliamshatner (1)
  • Big Data (1)
  • Birthday (1)
  • browsers (1)
  • buddhism (1)
  • bundling and unbundling (1)
  • china (1)
  • coding (1)
  • coffeeshoptalk (1)
  • colonialism (1)
  • Communication (1)
  • community development (1)
  • Computer Science (1)
  • Computer Vision (6)
  • crowdsourcing (1)
  • cyber security (1)
  • data migration (1)
  • Deep Learning (1)
  • design (1)
  • designreflection (1)
  • Developer (1)
  • Digital Humanities (2)
  • disruption theory (1)
  • Distributed Teams (1)
  • drawingwhiletalking (16)
  • education (3)
  • Email Marketing (3)
  • email newsletter (1)
  • Employee Engagement (1)
  • employment (2)
  • Engineering (1)
  • Enterprise Technology (1)
  • essay (1)
  • Ethics (1)
  • experiement (1)
  • fidgetio (38)
  • figma (2)
  • film (1)
  • film industry (1)
  • fingerpainting (8)
  • first 1000 users (1)
  • fonts (1)
  • forms of communication (1)
  • frontend framework (1)
  • fundraising (1)
  • Future Of Journalism (3)
  • future of media (1)
  • Future Of Technology (2)
  • Future Technology (1)
  • game development (2)
  • Geospatial (1)
  • ghostio (1)
  • github (2)
  • global collaboration (1)
  • god damn (1)
  • google analytics (1)
  • google docs (1)
  • Graffiti (23)
  • graffitifound (1)
  • graffpass (1)
  • growth hacking (1)
  • h1b visa (1)
  • hackathon (1)
  • hacking (1)
  • hacking reddit (2)
  • Hardware (1)
  • hiroshima (1)
  • homework (1)
  • human api (1)
  • I hate the term growth hacking (1)
  • ie6 (1)
  • ifttt (4)
  • Image Recognition (1)
  • immigration (1)
  • instagram (1)
  • Instagram Marketing (1)
  • internet media (1)
  • internet of things (1)
  • intimacy (1)
  • IoT (1)
  • iteration (1)
  • jason shen (1)
  • jobs (2)
  • jrart (1)
  • kickstart (1)
  • king robbo (1)
  • labor market (1)
  • Leonard Bogdonoff (1)
  • Literacy (1)
  • location (1)
  • Longform (2)
  • looking back (1)
  • los angeles (1)
  • Machine Learning (13)
  • MadeWithPaper (106)
  • making games (1)
  • management (1)
  • maps (2)
  • marketing (4)
  • Marketing Strategies (1)
  • Media (3)
  • medium (1)
  • mentor (1)
  • message (1)
  • mindmeld games (1)
  • Mobile (1)
  • Music (2)
  • Music Discovery (1)
  • neuroscience (2)
  • new yorker (1)
  • Newspapers (3)
  • nomad (1)
  • notfootball (2)
  • npaf (1)
  • odesk (1)
  • orbital (14)
  • orbital 2014 (14)
  • orbital class 1 (9)
  • orbitalnyc (1)
  • paf (2)
  • paid retweets (1)
  • painting (1)
  • physical web (1)
  • pitching (2)
  • popular (1)
  • post production (1)
  • Privacy (1)
  • process (1)
  • product (1)
  • Product Development (2)
  • product market fit (2)
  • Programming (6)
  • project reflection (1)
  • promotion (1)
  • prototype (17)
  • prototyping (1)
  • Public Art (1)
  • Public Speaking (1)
  • PublicArtFound (15)
  • Publishing (3)
  • Python (1)
  • quora (1)
  • Rails (1)
  • React (1)
  • React Native (1)
  • real design (1)
  • recent projects (1)
  • reddit (3)
  • redesign (1)
  • reflection (2)
  • rememberlenny (1)
  • Remote work (1)
  • replatform (1)
  • Responsive Emails (1)
  • retweet (1)
  • revenue model (1)
  • rick webb (1)
  • robert putnam (1)
  • ror (1)
  • rubyonrails (1)
  • segmenting audience (1)
  • Semanticweb (2)
  • Senior meets junior (1)
  • SGI (1)
  • Side Project (1)
  • sketching (22)
  • social capital (1)
  • social media followers (2)
  • social media manipulation (1)
  • social media marketing (1)
  • social reach (5)
  • software (3)
  • Soka Education (1)
  • Spatial Analysis (2)
  • spotify (1)
  • stanford (2)
  • Startup (21)
  • startups (7)
  • stree (1)
  • Street Art (4)
  • streetart (5)
  • stylometrics (1)
  • Technology (1)
  • thoughts (1)
  • Time as an asset in mobile development (1)
  • Towards Data Science (4)
  • TrainIdeation (42)
  • travel (1)
  • traveling (1)
  • tumblr milestone (2)
  • twitter (1)
  • twitter account (2)
  • typography (2)
  • unreal engine (1)
  • user behavior (1)
  • user experience (3)
  • user research (1)
  • user testing (1)
  • variable fonts (1)
  • video editing (2)
  • visual effects (1)
  • warishell (1)
  • Web Development (8)
  • webdec (1)
  • webdev (13)
  • windowed launch (1)
  • wordpress (1)
  • Work Culture (1)
  • workinprogress (1)
  • zoom (1)