28 Ways Medium could be better.

Things that Medium has accomplished since publishing this article are bolded.

  1. When publishing an article, I want as many people to read it right away. There should be a chronological feed that shows all the latest published articles.
  2. Collections should be more emphasized at the top of the front page.
  3. I should be able to “follow” my favorite collections so I can see an article once it is published.
  4. iPad publishing!
  5. I’d like to log in with e-mail sometimes instead of just twitter.
  6. It would be great if the images on the left were images from the Medium community to highlight cool people’s photos.
  7. Adding my article to a collection is hard, please make it easier.
  8. I want to embed video in posts! Even make the cover photo a video!
  9. Just like Google Docs, I’d like to collaborate with others in real-time. I.e. – I type something and they type something at the same time.
  10. Making a note on a mobile device is really hard.
  11. Notes should be easier to see! I have to look really hard to find and see if someone made a comment.
  12. There should be a native chat on Medium so I can talk to people outside of the comment section.
  13. Send me a text message when someone recommends or comments on my article.
  14. Get notified when someone posts about a certain topic.
  15. Be able to embed my blog on my website like Tumblr does.
  16. Like iBooks does, have a “night” and “day” feature that inverses the page from black/white so I can read articles in the night.
  17. Commenters should be able to control whether a post is public or private.
  18. Get a “badge” of sorts on my profile if I get an editor’s pick, get to the front page, or get more than 100 recs, ect.
  19. The invite-only concept of Medium, right now, makes people really excited to be able to post! It’s a great feeling of priveledge. It should stay that way.
  20. The text that says “Editors picks” and “most recommended today” should be bolded. Sometimes it’s hard to read.
  21. I’d like to see a history of articles I’ve read.
  22. Within collections, there should be a chat or wall so people with the same interests can have a discussion.
  23. Offline reading – be able to save an article as a .pdf or email me a .pdf so I can read it later.
  24. Paid pages – $0.99 a month to be able to read high quality articles, like for the New York Times or journalists.
  25. Location should be added to my bio. I’d like to see where people are located physically.
  26. A medium email account would be cool. [email protected] Going along with the native chat client I proposed earlier.
  27. The “Activity” page is cluttered. I wish it was better organized.
  28. A printable archive – turn my Medium posts into a physical book so I can give it to future employers to show them how awesome I am.

Tell me what you think. I’ll add it here. Follow me @_kyleryan

Addendum

  1. Everyone wants a search bar.
  2. Translation for posts. If you see a post in another language, have a built in way to translate and read it.
Go to the profile of Kyle RyanKyle Ryan
Next Story — The Importance of Upholding OO Design Patterns
Currently Reading - The Importance of Upholding OO Design Patterns

If you move fast and break things, you end up writing shitty code.

The Importance of Upholding OO Design Patterns

When I was 13 years old, I was introduced to coding C/C++ in a small window on my parent’s DELL computer. To me, code was a way to get things done. I got started by using the Arduino platform — a small USB micro-controller. If you wanted to have the board perform a task, you’d type some variables and functions into the IDE, and you’d see the results live… in front of you. There was rarely a program over 100 lines.

When I had my first real world internship, I expected code to be very organized. These are professionals I was thinking. While my code was wrought with legacy problems at home, I was sure that if a person was getting paid to code then their code must be clean right?

The opposite happened in this case.

Instead of having clean, modular, documented code, I dealt with a couple files that had no modularity to speak of. These were career software developers getting paid 6-figures to often write and deal with legacy code that had poor design and no modularity. Writing beautiful code is hard to create if your manager values results without valuing stable infrastructure.

When you move fast and break things, you write shitty code in the process.

When people wonder — a year later — why they cannot pinpoint an issue with code, it usually comes down to bad design or not taking care of legacy code issues.

This is what prompted Facebook to change their catchphrase. Move fast with stable infrastructure. Stable infrastructure is the cornerstone of any good product or service. If your infrastructure sucks, it’s really hard to build a great product.


When we think about mobile products, the Model-View-Controller (MVC) design pattern is key. While design patterns in OOP are often ignored, I firmly believe that MVC needs to be upheld in almost every mobile application (or a relevant design pattern) in order for you product to scale at a stable rate. When you code with a proper design pattern, objects communicate without inefficiency.

There are a lot of different OO design patterns, and design patterns in other paradigms, but MVC stands out for most consumer-based applications. You can see a list-description of other OO design patterns in the link below:

Of course, the MVC design pattern only works for limited types of software. As you might expect, MVC works well when you are using an OO language with an interface, logic, and user input. Not all of the software you write will require of work well with this pattern.

However, when it comes to writing mobile applications, MVC is incredibly useful to follow. MVC separates power into 3 distinct branches, with specific rules for each branch. You can read more about MVC in the link above, but the basic model goes as follows:

  1. The model handles all the business logic. It handles any requests you might have to a server, to device-based SQL interfaces, and logic functions.
  2. The view is what the use sees, interacts with, and manipulates.
  3. The controller manages the view, and then communicates user input back to the model to process. The model then tells the controller how to update the view, based on a response.

Stanford’s Swift / Objective-C classes in years prior have always used a really well put together diagram of the MVC design pattern, which I will include below this paragraph.

MVC solves the infrastructure problem that I talked about earlier. It compartmentalizes the role of different parts of code so that each department works together efficiently.


If you found this article at all useful, please click the ❤ below. I think this is something that many early, first-time programmers don’t learn to use properly. Use it! :)

Next Story — Urgency
Currently Reading - Urgency

Urgency

Why do we exist?

To feel comfortable?

To draw inside the lines?

To grow old in your hometown?

To stay cozy under the sheets?

To save a little money?

To not make mistakes?

To do the things your peers do?


I can’t do it. Quite the opposite.


I need to feel uncomfortable.

I need to draw outside the lines.

I need to grow old outside my hometown.

I need to make mistakes.

I need to do different things than my peers.


It’s an unconditional requirement of my existence.


So why live if we end up doing the same things they did?

Why live if we accomplish what they accomplished?

Why live if we follow a path dictated by others?

Why live if we only do things where the path ahead is clear?


This is a thesis — a thesis for the necessity of urgency today.

Next Story — Ebb & Flow
Currently Reading - Ebb & Flow

Ebb & Flow

If you know me, you know that I did a lot of work in solar energy & science between 2008–2012.

If you asked me 2012, I fully intended on going into a renewable energy field post-college.

When mobile started getting big, and growing, I transitioned my focus to software and mobile — especially iOS. At the time, I was getting more support for my work in programming than my work in science. This support then influenced a large part of my college education and probably my work after I graduate college.

The types of problems that need solving change as the supply and demand of our economy shifts. In 2012, it was very easy (and still is easy) for a teenager with little capital to build products for a large market using code. That is what excited me about mobile, and it is what continues to excite me about this sector. If you want to impact the daily life of a large amount of people today, mobile software ends up being a very good option. It will continue to be a good option for a while loner.

However, the problems that most people have cannot be solved through mobile software. One of those areas is energy. With access to energy, everything follows, communication, education, health care, and prosperity. Therefore it’s likely that creativity today can best be put to use by solving problems of energy. However, the conundrum is that having an influence on problems of energy requires a large amount of capital and resources. This capital and these resources are likely out of reach of a 19 year old. Software on the other hand is accessible to anyone with a computer and an internet connection.

Tesla’s & Elon Musk’s article below reminded me of these thoughts. Perhaps I will return to the energy problem one day.

For now, back to work…

Next Story — “It was a splendid population — for all the slow, sleepy, sluggish-brained sloths stayed at home …
Currently Reading - “It was a splendid population — for all the slow, sleepy, sluggish-brained sloths stayed at home …

“It was a splendid population — for all the slow, sleepy, sluggish-brained sloths stayed at home — you never find that sort of people among pioneers — you cannot build pioneers out of that sort of material. It was that population that gave to California a name for getting up astounding enterprises and rushing them through with a magnificent dash and daring and a recklessness of cost or consequences, which she bears unto this day — and when she projects a new surprise the grave world smiles as usual and says,

“Well, that is California all over.” 
Mark Twain, Roughing It

Sign up to continue reading what matters most to you

Great stories deserve a great audience

Continue reading