One of the most recent additions to the iPhone is the Photo Editor, directly in the iPhone. Added in the update that came from Apple over the summer, this new photo editor brings efficiency, and simplicity to photo editing, right in your phone. If you have a photo that you just took a moment ago of you with your friends, and you want to edit some features before posting it on a social networking site, it becomes simpler with this new addition, right in the Photos Application.

Open up the Photos application, and tap on a picture you would like to edit. Once your picture comes up, tap in the top right on the button named “Edit.” A user interface that deals with editing will show up, and you are ready to rock and roll. First off, many times we take pictures at weird angles, we take them sideways, upside down, to the right, to the left, and our phone doesn’t recognize them. In the bottom left, you will see an arrow that is pointing counter clockwise; this is the button that you want to press if you want to flip your picture around to the correct orientation. Keep in mind that this flips counter clockwise, and it doesn’t matter if you pass the orientation that you wanted. Just keep flipping!

Next up is the simple enhance tool. Sometimes colors get drowned out if we don’t have the right lighting in our pictures, and makes the photo look dull, and dreary. You don’t want your colors to look dull and dreary while you are celebrating your trip to New York and seeing Times Square! Tapping on the button that looks similar to a magic wand, your picture will begin to look brighter and fuller. With the tap of a button, the iPhone detects what points in the picture is, as we said earlier, “dull, and dreary” and enhances those colors to their predicted colors, if the light was in the correct intensity. However, if you are dissatisfied with the outcome of the enhance tool, if your picture is not handled well by the phone, you are able to tap on the wand again, and remove your auto enhance.

In the rare case of red eye in your picture, the new photo editor has a solution. Moreover, a one-tap solution. With a simple tap on the red eye correction tool, between the crop tool, and the auto-enhance tool, you bring up a screen where you are now able to tap anywhere on your photo where red eye exists, and remove it. As simple as that. Remember when you had to do crazy dragging, selection, and odd stunts to remove red eye? Not any more.

In the ever changing landscape of software programming, it is not surprising that developers and employees have a different set of preferences for desired skills.  However the number one language that developers want to learn according to a survey of developers by technical recruiter, Hacker Rank is Python. This is not a surprise considering that Python has been in demand for several years and programmers tend to really enjoy this language for clear syntax, good OOP support and great shortcuts. Python, named “the language of the year” in 2007 and 2010 in the TIOBE Index and has climbed to #4 status in May of 2018.

According to the study, employers want developers who:

-  Have problem-solving skills, such as the ability to break down large, complex problems.
- Are proficient in their programming language and debugging.
- Can design systems.
- Can optimize performance.
- Have experience in reviewing and testing code.
- Are proficient in database design

Surprisingly, formal education is not the deciding factor when it comes to what companies care about the most. People with computer degrees or certifications on a resume are not necessarily a first choice for hiring managers. Others that have years of experience even if those individuals are partially self-taught in the field stand to be taken seriously in the field.   For those individuals with a passion to learn and master a skill, there are ample opportunities with smaller to mid-sized companies.

Some interesting FAQ’s from the study:

    On average, developers know 4 languages, and they aspire to learn 4 more.
    Younger developers between 18 and 24 plan to learn 6 languages.
    Folks older than 35 only plan to learn and additional 3 languages.
    The top languages developers said they will learn were, Go, Python, Scala, Kotlin, and Ruby.
    There is a large gap between employers seeking developers that know React than there are folks that can do it.

So, Why Learn Python?
It is now the most popular introductory teaching language in U.S. universities.  Python is easy to use, powerful, and versatile, making it a great choice for beginners and experts alike. It allows you to think like a programmer and not waste time understanding difficult syntax that other programming languages can command. And, because of its rapid growth, many developers contribute to the Python community and share Python libraries making creativity that much more a reality

The original article was posted by Michael Veksler on Quora

A very well known fact is that code is written once, but it is read many times. This means that a good developer, in any language, writes understandable code. Writing understandable code is not always easy, and takes practice. The difficult part, is that you read what you have just written and it makes perfect sense to you, but a year later you curse the idiot who wrote that code, without realizing it was you.

The best way to learn how to write readable code, is to collaborate with others. Other people will spot badly written code, faster than the author. There are plenty of open source projects, which you can start working on and learn from more experienced programmers.

Readability is a tricky thing, and involves several aspects:

1. Never surprise the reader of your code, even if it will be you a year from now. For example, don’t call a function max() when sometimes it returns the minimum().
2. Be consistent, and use the same conventions throughout your code. Not only the same naming conventions, and the same indentation, but also the same semantics. If, for example, most of your functions return a negative value for failure and a positive for success, then avoid writing functions that return false on failure.
3. Write short functions, so that they fit your screen. I hate strict rules, since there are always exceptions, but from my experience you can almost always write functions short enough to fit your screen. Throughout my carrier I had only a few cases when writing short function was either impossible, or resulted in much worse code.
4. Use descriptive names, unless this is one of those standard names, such as i or it in a loop. Don’t make the name too long, on one hand, but don’t make it cryptic on the other.
5. Define function names by what they do, not by what they are used for or how they are implemented. If you name functions by what they do, then code will be much more readable, and much more reusable.
6. Avoid global state as much as you can. Global variables, and sometimes attributes in an object, are difficult to reason about. It is difficult to understand why such global state changes, when it does, and requires a lot of debugging.
7. As Donald Knuth wrote in one of his papers: “Early optimization is the root of all evil”. Meaning, write for readability first, optimize later.
8. The opposite of the previous rule: if you have an alternative which has similar readability, but lower complexity, use it. Also, if you have a polynomial alternative to your exponential algorithm (when N > 10), you should use that.

Use standard library whenever it makes your code shorter; don’t implement everything yourself. External libraries are more problematic, and are both good and bad. With external libraries, such as boost, you can save a lot of work. You should really learn boost, with the added benefit that the c++ standard gets more and more form boost. The negative with boost is that it changes over time, and code that works today may break tomorrow. Also, if you try to combine a third-party library, which uses a specific version of boost, it may break with your current version of boost. This does not happen often, but it may.

Don’t blindly use C++ standard library without understanding what it does - learn it. You look at std::vector::push_back() documentation at it tells you that its complexity is O(1), amortized. What does that mean? How does it work? What are benefits and what are the costs? Same with std::map, and with std::unordered_map. Knowing the difference between these two maps, you’d know when to use each one of them.

Never call new or delete directly, use std::make_unique and [cost c++]std::make_shared[/code] instead. Try to implement usique_ptr, shared_ptr, weak_ptr yourself, in order to understand what they actually do. People do dumb things with these types, since they don’t understand what these pointers are.

Every time you look at a new class or function, in boost or in std, ask yourself “why is it done this way and not another?”. It will help you understand trade-offs in software development, and will help you use the right tool for your job. Don’t be afraid to peek into the source of boost and the std, and try to understand how it works. It will not be easy, at first, but you will learn a lot.

Know what complexity is, and how to calculate it. Avoid exponential and cubic complexity, unless you know your N is very low, and will always stay low.

Learn data-structures and algorithms, and know them. Many people think that it is simply a wasted time, since all data-structures are implemented in standard libraries, but this is not as simple as that. By understanding data-structures, you’d find it easier to pick the right library. Also, believe it or now, after 25 years since I learned data-structures, I still use this knowledge. Half a year ago I had to implemented a hash table, since I needed fast serialization capability which the available libraries did not provide. Now I am writing some sort of interval-btree, since using std::map, for the same purpose, turned up to be very very slow, and the performance bottleneck of my code.

Notice that you can’t just find interval-btree on Wikipedia, or stack-overflow. The closest thing you can find is Interval tree, but it has some performance drawbacks. So how can you implement an interval-btree, unless you know what a btree is and what an interval-tree is? I strongly suggest, again, that you learn and remember data-structures.

These are the most important things, which will make you a better programmer. The other things will follow.