Skip to main content

Object Oriented Programming .. complex or overrated

In Second year computer science major, I took a whole course on object oriented programming with Java, It was full of new concepts back then and the book was big, but now recently I have been reading a book called growing 'object oriented software guided by testing' .

it has been 3 years since I have graduated and worked in 3 different companies, and while reading that book, the idea that there are so many details and concepts in object oriented that we barely feel we are applying or use in enterprise or medium or small scale applications was on my mind the whole time.

OOP has taken its name from the basic unit of the design which is Objects. However in real applications objects play minor roles and most of the time as VOs (value objects) so the whole concept of objects becomes minor in you're everyday work, there is nothing new about it. Another point is that these objects code are usually IDE generated, for example in eclipse if you're programming Java it takes less than a  minute to write a big class and generate getters/setter (encapsulation).

that doesn't stop here, what makes you really question if OOP is overrated in our major and given more time to teach and learn, is that there are frameworks such as Spring for Java that completely hides the OOP role in programming. What spring does is that, by default, it takes care of initializing and injecting the dependent objects with the objects they depend on, all done by XML or annotations and so there is no need to calling constructors or even writing them.

Spring came to avoid the over head of object oriented, we don't need infinite number of objects to implement the design and do the work. an instance of every object is usually sufficient to handle the job.
here we execlude the VOs from the equation because they are really nothing more than data holders and will not play a critical role in our architecture or design decisions the way we may think.

in summary, I feel although it's important to have a strong foundation in OOP, having a whole course to do it is not needed, OOP concepts are everywhere in our major and they can be focused on when necessary and most of what you will get in a single course will not be recalled because it's not something you need to remember everyday.




Comments

Popular posts from this blog

Android RecyclerView - Adding Empty View

So RecyclerView was introduced to replace List view and it's optimized to reuse existing views and so it's faster and more efficient as stated in the documentation:

https://developer.android.com/training/material/lists-cards.html

While using it, I faced the issue of missing a useful functionality that is implemented in ListView.
that feature is setting an empty view in case there was no records.

In ListView it was as simple as this

View emptyView = findViewById(R.id.mylist_empty_view);
ListView  myList = ....
myList.setEmptyView(emptyView);

but this method doesn't exist for recycler view so we need a work around until android team fixes this.


and here are the screen shots of both list view and recycler view fix

List view :

Recycler view :



here is how I fixed it:



here is the content of empty_view, it can be anything.



Enjoy.

Android - Multiple themes for one application

Sometimes you want to have multiple themes for your app
one strong example is having the ability to switch between dark and light themes because during night, a white bright screen can really be annoying for users eyes

Android will do most of the work for you but it may be required to change icons between themes to fit colors
In this blog I'll show a simple app with both dark and light themes and how to change icons without having to do that from code and keep things clean and centralized.
first of all let's create our activity, it will look something like this :


In /rest/values/styles.xml, we inherit Theme.AppCompat
 <!--
        Base application theme, dependent on API level. This theme is replaced
        by AppBaseTheme from res/values-vXX/styles.xml on newer devices.
    -->
    <style name="AppBaseTheme" parent="Theme.AppCompat">
        <!--
            Theme customizations available in newer API levels can go in
            res/values…

Creating your own OAuth2 server and clients using spring security - part 1

In this series of posts, I'll try to put together a simple working example on how to create your own OAuth2 server.

if you want to know more on OAuth2 and when to use it as authentication and authorization protocol then you can search about it on google and i'll put some URLs later.

Now I assume you are familiar with java web applications using Spring and maven.

to get started we need to create the server side with all dependencies required and i'll list them here, i'll use maven 2 to ease downloading dependencies for us.


Steps:

1- Create new maven project with arch type webapp:



2- Add the required depenedencies for spring, spring security, spring-oauth2, hibernate & other libraries (required for this tutorial only you can use other libraries if you like)

https://gist.github.com/anonymous/d33a31ddc3ba84375cf3

3- I used hibernate to automate the creation of the schema required by spring OAuth2 to manage tokens (it's required to have schema created in db if you a…