Ordered List Blog

Stop Being an Idiot

2010-02-08T17:23:33-0500

I hear this phrase a lot, and even recently, out of my own mouth: “Users are stupid, so we have to dumb this down to the lowest common denominator.” Stop it. Just stop it.

Our job, when designing features and interfaces, is to make them powerful, usable, and understandable. Not to cater to those people too lazy to think. Our job is to make things intuitive. But intuition still requires an individual to want to understand something. It requires an attempt to understand. It requires thought, even subconsciously. We have little power over people’s desire to succeed. We can only provide the tools to do so. So teach people, don’t criticize them.

People aren’t stupid. Really, they’re not. It’s possible they don’t have the same experiences you do, but that doesn’t mean they’re an idiot. Writing people off, and dumbing down utility in the name of stupidity is, well, stupid. Bring people with you, and provide them tools to learn and be successful.

Exercise and Education

When you exercise, you stretch yourself. You get healthy by pushing past your existing level of fitness. You don’t succeed by dumbing down your workout. You push, you learn, and you get better. We educate users the same way. We must show, explain, and gently push our users to succeed.

Simple, not Stupid

And don’t misunderstand. Keep things simple. But simple doesn’t mean stupid. Simple doesn’t mean boring. And simple certainly doesn’t mean standard. It means you can figure it out, even if it takes a minimal amount of thinking.¹

Celebrate when users succeed, and don’t patronize them for wanting or needing help.

Teach, Don’t Ignore

Again, your users aren’t stupid. They could very easily be intimidated. Nobody likes the unfamiliar. But people love to succeed. So help them. Provide cues, hints, and even invite questions. But don’t dumb it down.

And here’s the real truth: If you’re dumbing down your interface or features because you think people won’t ‘get it,’ you’re hurting the experience of those who are more comfortable in your software. If you don’t provide hints and cues in your interface, you’re intimidating and hurting the experience for people who aren’t as comfortable on the web. Either way, you’re keeping people from learning, and that’s just uncool.

So stop thinking your users are stupid. Teach them, train them, and let them succeed. And in the process, if you let them, they’ll teach you a thing or two as well.

Stop Blogging

2010-02-04T09:29:55-0500

I mean it. All of you people are writing fantastic, useful articles about code, methods, and technologies, but you’re putting them in blog posts — a date-based format that encourages us to leave things as they were, historically.

And with any blog post about technology, it gets stale. It gets outdated. And in the worst case, several months or years later, it’s just absolutely wrong.

As a content consumer, sometimes we can tell. Some of us might pay attention to the post date, some of us might be deep enough into the subject to tell outdated information from fresh. But lots of people can’t. And keeping incorrect information on the web, simply for historical reasons, is — well, just selfish.

Looking in the Mirror

I’m only saying this to you because I said it to myself about six months ago. I’m annoyed that this very site contains bad information in its archives. So I’ve decided to clean it up. Yes, this may mean broken links in some places on the web. But a broken link is better than misleading someone who is genuinely looking for information.

We have a responsibility, as publishers, to maintain and cultivate our sites. I agree with archiving our opinions, or our experiences, but keeping old, outdated code, examples, or resources isn’t helping the web.

Our Solution

We’ve decided to maintain a resources area where we will post examples, data, and code samples. We will likely refer to them in our blog, or make posts when we create or update them, but those posts won’t get stale. The content of the resource, however, might. So we’re making a decision to regularly go through our resources to tweak them, rewrite them, or sometimes even delete them¹, if it makes sense.

Keep in mind that this is a process. We’re not done moving old posts that should be resources, and some of our resources may already need a little updating. It will take work, but we think it’s worth it.

So what do you do to keep the web fresh?

A New Look, a New CMS

2010-01-21T09:45:11-0500

We’ve been focusing our efforts on building Harmony the past few months, but we recently carved out some time to give our site some much needed love and attention.

This design has been waiting in the wings for a few months, and now that Harmony is able to handle most everything this site needed, we’re ready to make the switch. We’ve reorganized and replaced some content, so I’m sure a few things will be broken. If they are, just let us know.

Also, this design uses some pretty advanced CSS3, so things might not look quite the same in older or less capable browsers. We’re fine with that, and will likely give them a little more love in the near future.

We hope you enjoy the new version of OrderedList.com.

Harmony Documentation

2010-01-05T17:07:21-0500

We’re finally revealing the tip of the Harmony iceberg in the form of a nearly-complete documentation site that will fuel our beta testers, and help future customers hit the ground running once the CMS is released.

I say ‘tip of the iceberg’ for two reasons. One, Harmony has been in the making for 18 months now, and has been under constant revision, refinement, and improvement the whole time. It’s was clear when we started Harmony that we knew what direction we wanted to go, but had no idea what it would become, specifically. But more importantly, reading about, and watching screencasts, just can’t give you the same experience. You really have to use Harmony to get just how intuitive and powerful it really is.

We’re happy to say that as we’re writing and testing some of the last bits of code before we can let other people use it, we couldn’t be happier with how Harmony is turning out. We love using it. And we can’t wait to make it better.

So head on over to the Harmony site, and check out what all the fuss is about. And don’t forget to check out the documentation. We’d love to hear what you think.

Building Evented Single Page Applications

2010-01-04T14:07:29-0500

Today I did a presentation on what Steve and I have been working on behind closed doors for the past year (or more it seems). It is always fun to share the exciting things we have been up to and this was no different.

I promised those that were at the talk that I would post my slides, so here you go. I don’t know how helpful the slides are without my incredible, booming voice, but hopefully you find value in them.

Since people were curious, I have also pasted some of the code online. Right now it is quick, dirty and relies on an older nightly version of jQuery, but hopefully some will find it helpful. Once 1.3.3 is released, you will not need this nightly version to get stuff working. Also, your mileage will vary in IE as we haven’t really done any testing with it.

You can download the core layout javascript file from Harmony (gist) and from Peoplebase (gist). The two files are very similar, but have a few different features that haven’t been merged together. Feel free to play with it, but I in no way recommend using it in production right now. Just look at the code for ideas.

Once we get some time, we’ll extract the parts that we see valuable into a framework with tests that anyone can feel free to drop in to their project.

Atmail Launched

2010-01-07T17:09:01-0500

Every once and a while, a project comes along, that despite your current workload, you just cannot turn down. Last November, Atmail brought us a project like that.

Atmail is a Linux based Webmail Client + Email solution that you can use as an alternative to Gmail or Exchange to bring your organization’s email under control. They came to us looking simply for ideas and nothing more. Perfect.

We have always had a soft spot for webmail and the thought of ideas being a deliverable was exciting. We spent some time brainstorming and then Steve’s eyes glazed over much like Isaac, the painter on Heroes, and he went to work. A few revisions later, we had something we were excited about and it was time to make sure it would actually work.

Since Steve did the design, I worked on the XHTML/CSS. I can promise you the implementation was anything but typical. Supporting IE6 is usually not much of an issue, as both of us have experience bending it to our will, but we did not have a lot of experience making web apps rendered with IE6 look and feel like a paned desktop app. A few expressions and some crazy css later, we had it working in all browsers and good to go.

We delivered the files to Atmail and hoped they were happy. Normally, we get feedback in the design process long before we implement the XHTML/CSS. Atmail was different though, as they just wanted to see what we would do without them. Talk about a cool client! Here’s what they had to say about our work.

I was impressed with the delivery and formatting of the HTML/CSS templates from Orderedlist – This enabled us to easily transform the mocks into jQuery and Zend, and get the prototype design into working code!

Evidently they were as happy as we were with the direction as they took it and ran with it. Last month, they launched version 6, which is our initial thoughts, brought to fruition by the their team. We were impressed at how well they took our 2 or 3 mockups and used them to create a cohesive app with a lot of functionality. Below is a screenshot of the final product.

Congrats on the launch Atmail, and we are glad we could help out!

Google Ajax Feeds Fun

2010-01-04T14:07:29-0500

Often times when new things come out, I am aware of them, but for whatever reason, they don’t really click with me. I heard about Google’s Ajax libraries a while back and I remember thinking whoop-dee-freakin-doo.

Today, somehow, I ended up on the docs page for Google’s Ajax Feed API and it clicked.

On RailsTips, I show the latest quick tips (ruby and rails related links) in the footer on every page. I didn’t want to customize Mephisto to spit out the link list, so I set out to find a client-side solution. I ended up creating a Yahoo Pipe with a JSON callback to show the list on page load. This worked fine, but it annoyed me that I had to manually create a Yahoo Pipe each time that I wanted to do this on a site.

The Solution

Today, when I randomly ended up browsing the documentation, I realized that the Google Feed API would be a better solution for what I needed. In just a few minutes, I ended up with a really simple solution.

RailsTips.QuickTips = {
  load: function() {
    var feed = new google.feeds.Feed("http://feeds2.feedburner.com/railsquicktips/");
    feed.setNumEntries(12);
    feed.load(function(result) {
      if (!result.error) {
        var list = jQuery('#more_quick_links');
        for (var i=0; i < result.feed.entries.length; i++) {
          var entry = result.feed.entries[i];
          list.append('<li><a href="' + entry.link + '">' + entry.title + '</a></li>')
        }
      }
    });
  }
}

The Live Demo

No need to login to Yahoo Pipes, create a pipe and copy the URL. All I need to do now is just include Google’s AJAX Feed API and tell it which feed I would like to display. Of course, being the astute gentleman that I am, I created a demo for you to check out.

If you are curious about my previous solution, using a Yahoo Pipe, Snook just wrote a little bit on it, so feel free to head over there.

The ability to show feeds on a website using JavaScript is really cool. The possibilities are endless. Anything that is in feed form can now be shown on any site with no hardcore programming needed. Pretty crazy. Next you’re going to try tell me that in the future we can use multiple background images on a single element. Ha, you’re funny!

Harmony Update

2010-01-04T14:07:30-0500

Things have been silent on this here blog because Steve and I have been making ridiculously awesome progress on Harmony. We are actually less than a week away from our first deploy and only a few weeks away from running OrderedList.com in Harmony.

Yep, you heard it here first. We are actually going to be able to demo this thing at SXSW in a few weeks. Exciting! Tonight, we spent some time showing it off at our local Ruby group meeting and it went pretty well. Below is a rather blurry picture of Harmony projected onto the wall at the meeting.

Some Stats

Harmony is currently hosted in a private repository on Github, so I used Github’s API along with HTTParty to generate some stats. Below is the number of commits by month to the repo, which is a general indication of the intensity on our part. If you are curious about the code, it is nothing special, but you can find it here.

Month	# of Commits
June 2008	99
August 2008	2
September 2008	16
October 2008	28
November 2008	3
December 2008	0
January 2009	122
February 2009	129
March 2009	17

As you can see, we were pretty sporadic with Harmonious Fridays from June to December. We noticed that in January and decided it was time to spend more time on Harmony. Since January, you can see a massive upswing in activity. Heck, we already have 17 in March (only 2 days).

I’ve been working on Harmony full time since mid-January and Steve has been putting in extra hours on top of client work. Speaking of client work, we have some cool projects that we need to post about. I’ll make a note to myself to get that done in the next couple weeks. That is all for now. Hope a blurry photo and a promise of work being done is enough.

If you are heading to SXSW, find us (twitter should work) and we’ll give you a demo. We didn’t get conference passes, but we’ll be in town from Saturday to Tuesday enjoying the night life. :)

Is The Web Recession Proof?

2010-01-04T14:07:30-0500

Economy, economy, economy. I swear it is all you hear about these days. Turn on the news. Go to a cafe. Doesn’t matter where you are, someone mentions how bad the economy is. Because Steve and I left extremely stable and secure jobs, we often get asked, “Are you feeling the hurt?”

So are we? Currently and thankfully, we are a not. On the contrary, we have noticed an increase in project requests in December and January. Granted, project requests do not always turn into projects, but I think for us they are pretty indicative of interest.

Here are my unfiltered and most likely naive thoughts on our current circumstances. I believe that even though the economy as a whole is hurting, there are pockets of growth. I believe that one of those pockets is the web. I believe that if you are a company that has been fiscally responsible, grown at a reasonable rate, and continually provided high quality products and services, you are going to be fine.

The answer is no. The web is obviously not recession proof, but if there is any industry right now that provides opportunity, it is the web. Stop worrying about the economy and focus on strengthening your business. What do we do, here at Ordered List, to make sure we are strong?

Cash flow. We don’t obsess over cash, but we require payment to do work. Yep, we are paid before we do work, not after. If a client wants a fixed price, they’ll get one, but they’ll pay all or at least half of it up front. If the project is larger, we work in 100 hour blocks. Once we have logged 80-90 hours, we let the client know and go from there.
Keep reserves. It is tempting to pay yourself a ridiculous salary or pay out large profit checks, but that is very short-sighted. We pay ourselves modest salaries, even for South Bend, and always make sure we have several months of expenses in the bank before we partake in profit sharing.
Spend money where it counts. If you don’t need an office, don’t pay for office space. This is different for everyone, but instead of paying rent and utilities every month, we choose to keep our recurring monthly expenses low. Instead, we splurge more on laptops, gadgets and conferences. We care a lot more about that.
Build a reputation online. Every piece of work that we are commissioned to do comes from the reputations that Steve and I have built online. Geographically, our closest client to date was almost 100 miles away. Our clients find us online and we work remotely for them, which opens up far more opportunities than if we focused on the local chamber of commerce. Recently, someone asked me what the market was like in South Bend. My response was, “I don’t know.”
Stay current. Don’t shoehorn yourself into one thing. Our primary service is website and application design, but we are also pretty knowledgeable in Ruby and Rails, and more recently, have been diving into iPhone development. The great thing about being small and current is that different opportunities are more profitable at different times, and if you are current, you can not only see them coming, but also take part in them.

I could be wrong. We could be in for dark times, but worrying about that won’t get us anywhere. Focusing on what is going good and attempting to amplify that will.

What is your sense of the web world right now?

Another Blawg Enters The Sphere

2010-01-04T14:07:30-0500

I have spent a lot of time over the past few months growing RailsTips, a Ruby and Rails programming blog. All the tweaks I have been doing over there, have left me wanting an outlet to share.

I didn’t want to completely change topic here on Ordered List, since Steve is doing such a great job on HTML5, so last Sunday I whipped BlawgTips together and invited my friend Chas Grundy to co-author it with me. Get it, blawwwwg? Hilarious, I know.

What it will/won’t be

I can promise you now that Blawgtips won’t be boring. It won’t teach you how to install Wordpress (or any WP plugins for that matter). It won’t be about how to use blogging tools. So what will it be about? Why. Why should you measure your traffic? Why should you think about your post titles? Why you should go from specific to general in your <title> tags. These are principles that are helpful for all websites, but we will focus on blogs in particular.

A Sampling

Below are a few articles we added last week, to kick things off and give you an idea of what is to come. I have plenty more ideas sitting in the hopper as well.

Hope you find this new resource helpful. Head on over and subscribe if you want to stay in the loop. Also, we are sure there are other bloggers out there with stuff to say, so if you would like to guest author a post (or a few), let me know.

Getting Started with HTML5

2010-01-04T14:07:30-0500

HTML5 has some interesting new additions. But let’s recognize the elephant in the room: HTML5 isn’t a final spec, nor will it be for quite some time. That said, there are many pieces that are stable, and can be used right now.

The Doctype

For a little background, HTML5 comes in two serializations: XML and HTML. The XML serialization of HTML5 is served as application/xhtml+xml, while the HTML serialization is served as text/html. Due to the added complications of serving application/xhtml+xml, we’re going to use the HTML serialization for all our demos here.

So here’s one of my favorite parts about starting a new HTML5 document: I can do it from memory.

<pre><!DOCTYPE html> <html> <head> <title>New Document</title>

Now that’s simple, isn’t it? Finally, a memorable doctype!

Will that Work?

But browsers don’t recognize the HTML5 doctype yet, right? While that’s mostly true, we need to remember one great fact: If a browser comes across a new or unrecognized doctype, it simply moves into standards mode (or strict mode in IE). So you can begin building pages with this HTML5 doctype right now, and they will just work! And when browsers do implement HTML5, you’ll be ahead of the game.

So what Now?

Now you have a few options. You could just go about the way you normally code pages, with no real changes. But that’s not really worth changing a doctype, is it? More appropriately we should learn and use some of the new tags HTML5 gives us to improve our coding semantics and efficiency. Next in this series, we’ll touch on the new structural tags HTML5 provides us, and how they can be used today. Stay tuned.

Getting Topical

2010-01-04T14:07:30-0500

Posting on this site has dwindled significantly, especially as John and I get busier. But it’s not for lack of fun and interesting stuff to talk about. Recently, I’m just not sure what to post.

The theme of this blog has always been general, and I’d like to keep that flexibility. That said, I think having a short-term focus would be helpful to help get some more ideas and knowledge out in writing. So we’re going to start having monthly themes around here.

So starting tomorrow, January will be the month of “HTML5 and CSS3.” I recently gave a workshop on the topic at Future of Web Design, so I have lots to share. There will be unrelated posts that crop up throughout the month, but we’ll try to stay on topic as much as possible.

Also, if you have ideas for topics, be sure to let us know. We aim to please, after all.

Harmony: Theme Management

2010-01-04T14:07:30-0500

Hard to believe it has been three months since we last talked about Harmony. Heck, it is hard to believe it has been three months period. The last three months have flown by for us, but we thought we would start the new year off on the right foot.

While development on Harmony has slowed considerably since the last post on user management, it has not stopped. We traveled the months of October and November away. And December? Well, December was full of a couple really cool client projects that we just couldn’t turn down, despite having an already full schedule.

Theme Management

Ok, that is enough excuses for now. How about we discuss themes? So what are themes? Well, themes are what make up the look and feel of your website. Harmony will support multiple themes for each site with one active theme. Each theme is comprised of template, stylesheet, javascript and image files.

One note is that theme files should not be confused with assets. Assets are resources that are linked to and help support the content. Files like pdf’s, images, zipped archives and such would go into the assets area. Theme files are only concerned with the look and feel of the site. Your logo would be a theme file. Your annual report would be an asset. This will be obvious when you use Harmony, but since you can’t right now I thought I would explain the difference. Hope that clears any possible confusion up.

As I stated above, each site can have multiple themes. This means you can create a theme for your site and then when you redesign, you can simply create a new theme and leave the original theme active while you work on the new one. Once you complete the new theme, you can activate it and your whole site’s look and feel will switch on a dime. This is nothing new as far as website management systems are concerned, but if you are building static html sites, it will be an eye-opening experience.

The Template System

For the template system, we have chosen liquid, which is based on Django’s template system and is very popular in the Rails ecosystem. If you interested, you can read more about liquid on the wiki. The great thing about liquid is that it is so extendable for programmers. We will have a lot of custom template tags and filters to make your development live a lot easier. Below is just a really small sample of some of the helpers we will provide. If you have ever used the Mephisto blogging system, some of them will look familiar as Mephisto uses liquid extensively.

# outputs two stylesheet link tags to stylesheets 
# named reset.css and common.css
{{ 'reset,common' | stylesheets }}

# outputs one stylesheet link tag to print.css with media set to print
{{ 'print' | stylesheets: 'print' }}

# includes the file named _header.liquid
# very similar to apache and php includes, and very handy!
{% include 'header' %}

# outputs a ul with an id of nav and li's for each navigation item
# this will be customizable to change the id, 
# include or exclude child pages, etc.
{{ site.navigation | nav }}

You can probably see that these will indeed be helpful, but that is just the beginning. I don’t know about you, but I can never remember the syntax for IE conditional statements. That is why I’m particularly excited about filters like ie_stylesheet:

# outputs stylesheet link tag to ie.css wrapped
# in IE conditional comment for versions of IE less than 7
{{ 'ie' | ie_stylesheet: '< 7' }}

Think of all the things that you do everyday that you have to lookup on google or a previous project, because you forgot the exact syntax. One of our goals is to make web development easier and more fun using Harmony than it would be using any other website management system or programming language. A lofty goal yes, but we like to set our sights high.

Icing On The Cake

Another thing we are excited about is that because all the theme files are stored in the database, we can process them before serving them. This means we can enhance the ability to do things with files that normally wouldn’t be possible in a more static development environment.

One simple example is css variables. Wouldn’t it be handy to set dark_green, light_green, header_orange as variables in css and just reuse those colors where needed? I always forget hex codes, but variables names wouldn’t be that hard.

Yeah, we know webkit has an initial run at css variables, but why should we wait for all the other browsers to come around? Because we can process your stylesheet when you save it, we can make things work programmatically that browsers don’t currently support.

It might be kind of hard to visualize what we are talking about above, but trust me, it will be cool. What are some other features we have thought would be cool?

One click downloads of popular javascript and css frameworks into a theme
Asset bundling – something automated for bundling stylesheets and javascripts together to minimize http requests and thus improve performance
Automatic JavaScript minifying – would be something optional
“Developer Mode” when editing themes that allows one window with css/html open for editing and another open with a live preview

What are your pain points?

These are just a few ideas that we have thought would be handy and I’m sure you have your own. What are things that you repeat all the time in web development? Where are your pain points? Give us more ideas. I’m sure once you all get your hands on Harmony, you’ll have even more, but I’m curious if, while reading this post, anything else popped into your head.

YardVote

2010-01-04T14:07:31-0500

Yesterday some friends from Holland, MI came down to hang out with Steve and I all day. They started a project called Yard Vote about a month ago and we decided to help them give the application some upgrades.

New Design

Steve worked out a new design for them that really features the mapping aspect and he created some killer icons. The previous version was fixed width and kind of narrow, so it was harder to see all the signs. Now with the full width map, you can really get a feel for the sign density in an area.

Email a Sign

When I started using YardVote I quickly found myself addicted, but the sign entry process from a phone was kind of slow. While Steve was working on the interface, I added the ability for Yard Vote to receive emails. In a few hours, I was able to glue together the workings to allow emailing yardvote@collectiveidea.com with the subject being the color of the signs and the body equivalent to the address. The email receiving can even update existing signs if you accidentally put in the wrong color.

It was a lot of fun to take a day off and help out our friends with their cool project. FYI: YardVote isn’t just for Michigan and Indiana either, as there are already signs marked in 26 states. Go ahead and add one yourself. Let’s see how many we can get before the election.

Scannability Equals Profit

2010-01-04T14:07:31-0500

No one reads on the internet anymore. Right? Time and time again it is proven that we just skim and scan, eyes darting around like a chicken with its head cut off. When are we as web workers going to fully recognize that?

I use Facebook pretty rarely, but today I received a message from a friend so I fired up Safari and logged in. I immediately was distracted by how perfect the messages area of Facebook is designed. See below.

You might be thinking, ok, this guy is crazy because that text is too blurry to read. If so, you missed the point. In order to really dive into why I think it is designed so well, I’m going to add some overlays so it is easier to reference things.

The screenshot above is around 660 pixels of real estate when live in Facebook. I shrunk it down a bit to fit here. Let’s start with columns 1 and 2. Facebook could have merged those columns together. I mean look at all the vertical space left unused for each message. The reason Facebook separated the image and details is when you merge them into one column you lower scannability. It’s definition time. I define scannability as the ability to quickly scan vertically and comprehend. Scanning is a very vertical thing. As your eyes shoot down the messages page, it is very easy to scan the images, then the names and then the message body. It would be much hard to for your brain to comprehend things if it had to process, text then image, text then image, text then…you get the point.

Speed Reading

Try something real quick for me. Reread the paragraph above, but as you go through the lines, don’t trace all the way from the beginning of the line to the end. Start on the second or third word and as you get two or three words from the end continue to the next line until you have read the paragraph. The amazing thing is, your brain sees and comprehends the words on each end of the line, even though you don’t look at them. I picked up this speed reading technique in the Four Hour Workweek by Tim Ferriss.

This is why Facebook, whether consciously or not, is only using a three hundred pixel column for the message body, instead of the four or five hundred pixels that are available. As columns of text get more thin, there are fewer words to deal with on each line, which makes it faster to scan vertically and comprehend.

Poor Scannability Example

Take Twitter for example. I love Twitter like a son, but I find their web interface almost unusable. Aesthetically, it is pleasing, but the line length of the tweets (around 400 pixels as of article posting date) is so long that I lose the ability to scan vertically through them. The length mixed with the fact that the username is inline in the tweet forces me to read my tweets. Yeah, that is right, I don’t like reading my tweets. I scan them for keywords and such and only read those that catch my eye or are by someone I hold near and dear. I do the same thing on your blog, that is, if I read your blog.

I believe scannability is one reason Twitterrific, Snitter and all the mobile Twitter clients are so popular. Remember? People don’t read anymore.

The Point

Yes, I do have a point. This is not just a rant. I think as screens started getting wider, web workers decided they should use the extra space. I mean, we can’t leave it blank, it’s above the fold (don’t get me started on that). Wrong. Just because the space is there, doesn’t mean it should be used. Next time you begin work on a website or web app, remember these three simple steps.

3 Simple Steps

Scannability
???
Profit