Profile

Cover photo
Denys Zadorozhnyi
Lived in Kyiv
274 followers|2,068 views
AboutPostsPhotosVideos

Stream

Denys Zadorozhnyi

Shared publicly  - 
 
"Коля, у нас машины подъезжают, а не подкатываются!", сказала начальница службы такси в аеропорту Борисполь, глядя как Коля толкает свой незаведенный мерс пару метров на только освободившееся место своего коллеги. Растем типа ;) . Осталось английский подтянуть только. 
 ·  Translate
1
Add a comment...

Denys Zadorozhnyi

Shared publicly  - 
 
Нарешті приїхав 18-55 для nex5. Бо з фіксом вже ноги втомилися :)
 ·  Translate
1
Павел Пеников's profile photoDenys Zadorozhnyi's profile photo
4 comments
 
Лепестки диафрагмы 7
Круговая диафрагма ДА
Мин. Диафрагма 22-32

http://www.sony.ru/product/ddl-nex-5-nex-3-lenses-and-a-mount-adaptor/sel-1855#pageType=TechnicalSpecs
Add a comment...

Denys Zadorozhnyi

Shared publicly  - 
 
Additional touchpad taps/gestures with BetterTouchTool. I'm using this scheme :
Four finger tap = CMD-Click (opens URL in new tab)
Four finger click = CMD-W
Five finger click = CMD-Q

Unfortunately, "Three finger tap" is conflicting with original touchpad option to show "Lookup in dictionary" with double three finger tap.
1
Add a comment...

Denys Zadorozhnyi

Shared publicly  - 
 
True. I've done the opposite way. Gone from Android to iOS.

http://nfarina.com/post/8239634061/ios-to-android
1
Add a comment...

Denys Zadorozhnyi

Shared publicly  - 
 
Totally agree.

"Principles of Good Programming

The principles of good programming are closely related to principles of good design and engineering. The following programming principles have helped me over the years become a better programmer, and I believe can help any developer become more efficient and to produce code which is easier to maintain and that has fewer defects.

DRY - Don’t repeat yourself - This is probably the single most fundamental tenet in programming is to avoid repetition. Many programming constructs exist solely for that purpose (e.g. loops, functions, classes, and more). As soon as you start repeating yourself (e.g. a long expression, a series of statements, same concept) create a new abstraction. http://en.wikipedia.org/wiki/Don%27t_repeat_yourself

Abstraction Principle - Related to DRY is the abstraction principle “Each significant piece of functionality in a program should be implemented in just one place in the source code.” http://en.wikipedia.org/wiki/Abstraction_principle_(programming)

KISS (Keep it simple, stupid!) - Simplicity (and avoiding complexity) should always be a key goal. Simple code takes less time to write, has fewer bugs, and is easier to modify. http://en.wikipedia.org/wiki/KISS_principle

Avoid Creating a YAGNI (You aren’t going to need it) - You should try not to add functionality until you need it. http://en.wikipedia.org/wiki/YAGNI

Do the simplest thing that could possibly work - A good question to ask one’s self when programming is “What is the simplest thing that could possibly work?” This helps keep us on the path towards simplicity in the design. http://c2.com/xp/DoTheSimplestThingThatCouldPossiblyWork.html

Don’t make me think - This is actually the title of a book by Steve Krug on web usability that is also relevant in programming. The point is that code should be easily read and understood with a minimum of effort required. If code requires too much thinking from an observer to understand, then it can probably stand to be simplified http://www.sensible.com/dmmt.html

Open/Closed Principle - Software entities (classes, modules, functions, etc.) should be open for extension, but closed for modification. In other words, don't write classes that people can modify, write classes that people can extend. http://en.wikipedia.org/wiki/Open_Closed_Principle

Write Code for the Maintainer - Almost any code that is worth writing is worth maintaining in the future, either by you or by someone else. The future you who has to maintain code often remembers as much of the code, as a complete stranger, so you might as well always write for someone else. A memorable way to remember this is “Always code as if the person who ends up maintaining your code is a violent psychopath who knows where you live.” http://c2.com/cgi/wiki?CodeForTheMaintainer

Principle of least astonishment - The principle of least astonishment is usually referenced in regards to the user interface, but the same principle applies to written code. Code should surprise the reader as little as possible. The means following standard conventions, code should do what the comments and name suggest, and potentially surprising side effects should be avoided as much as possible. http://en.wikipedia.org/wiki/Principle_of_least_astonishment

Single Responsibility Principle - A component of code (e.g. class or function) should perform a single well defined task. http://en.wikipedia.org/wiki/Single_responsibility_principle

Minimize Coupling - Any section of code (code block, function, class, etc) should minimize the dependencies on other areas of code. This is achieved by using shared variables as little as possible. “Low coupling is often a sign of a well-structured computer system and a good design, and when combined with high cohesion, supports the general goals of high readability and maintainability” http://en.wikipedia.org/wiki/Coupling_(computer_programming)

Maximize Cohesion - Code that has similar functionality should be found within the same component. http://en.wikipedia.org/wiki/Cohesion_(computer_science)

Hide Implementation Details - Hiding implementation details allows change to the implementation of a code component while minimally affecting any other modules that use that component. http://en.wikipedia.org/wiki/Information_Hiding

Law of Demeter - Code components should only communicate with their direct relations (e.g. classes that they inherit from, objects that they contain, objects passed by argument, etc.) http://en.wikipedia.org/wiki/Law_of_Demeter

Avoid Premature Optimization - Don’t even think about optimization unless your code is working, but slower than you want. Only then should you start thinking about optimizing, and then only with the aid of empirical data. "We should forget about small efficiencies, say about 97% of the time: premature optimization is the root of all evil" - Donald Knuth. http://en.wikipedia.org/wiki/Program_optimization

Code Reuse is Good - Not very pithy, but as good a principle as any other. Reusing code improves code reliability and decrease development time. http://en.wikipedia.org/wiki/Code_reuse

Separation of Concerns - Different areas of functionality should be managed by distinct and minimally overlapping modules of code. http://en.wikipedia.org/wiki/Separation_of_concerns

Embrace Change - This is the subtitle of a book by Kent Beck, and is also considered a tenet of extreme programming and the agile methodology in general. Many other principles are based on the concept that you should expect and welcome change. In fact very old software engineering principles like minimizing coupling are related directly to the requirement of making code easier to change. Whether or not you are an extreme programming practitioner, this approach to writing code just makes sense. http://www.amazon.com/gp/product/0321278658"

via http://www.artima.com/forums/flat.jsp?forum=106&thread=331531
1
Add a comment...

Denys Zadorozhnyi

Shared publicly  - 
 
ААА! http://itunes.apple.com/us/app/icleanmemory/id439277582?mt=12
На другому місті в рейтингу платних програм після OS X Lion. Ну як так можна? Ще й рейтинг майже 5 зірок. Хто всі ці люди?
 ·  Translate
1
Add a comment...
Have him in circles
274 people

Denys Zadorozhnyi

Shared publicly  - 
1
Add a comment...

Denys Zadorozhnyi

Shared publicly  - 
 
Wow. Amazon is so kind.

"Amazon’s biggest feature by far, has been their Free App Of The Day promotion. Publicly their terms say that they pay developers 20% of the asking price of an app, even when they give it away free. To both consumers and naive developers alike, this seems like a big chance to make something rare in the Android world: real money. But here’s the dirty secret Amazon don’t want you to know, they don’t pay developers a single cent."

via https://shiftyjelly.wordpress.com/2011/08/02/amazon-app-store-rotten-to-the-core/
1
Add a comment...

Denys Zadorozhnyi

Shared publicly  - 
 
Is this only because of the battery weakness on Android phones ?

"Gogo tells AllThingsD that iPhones make up nearly two-thirds of the mobile devices using its inflight Wi-Fi service. "

via http://daringfireball.net/linked/2011/08/01/gogo
1
Add a comment...

Denys Zadorozhnyi

Shared publicly  - 
 
Tip! Do not add Macintosh HD to the exclusion list in Spotlight!

Somehow Mac App Store is relying on Spotlight. You'll see updates for the purchased apps ONLY in Purchase section of Mac App Store with weird message like "You have updates available for other accounts" when you try to update it.
1
Add a comment...

Denys Zadorozhnyi

Shared publicly  - 
 
Угу. Беліз, Бруней, Сурінам. А у нас офіційні (начебто) iPad2 продають без AppStore.

"We are pleased to announce the expansion of the App Store to 33 new territories:

Algeria
Angola
Anguilla
Antigua and Barbuda
Azerbaijan
Bahamas
Bahrain
Barbados
Belarus
Belize
Bermuda
Bolivia
British Virgin Islands
Brunei
Cayman Islands
Cyprus
Dominica
Ghana
Grenada
Guyana
Iceland
Montserrat
Nigeria
Oman
St. Kitts and Nevis
St. Lucia
St. Vincent and The Grenadines
Suriname
Tanzania
Trinidad and Tobago
Turks and Caicos
Uzbekistan
Yemen"
1
Add a comment...
People
Have him in circles
274 people
Places
Map of the places this user has livedMap of the places this user has livedMap of the places this user has lived
Previously
Kyiv
Links
Contributor to
Story
Introduction
Interested in Android, iOS development
Bragging rights
Author of Parkdroid app
Basic Information
Gender
Male
Other names
Денис Задорожний