Showing posts with label Software Development. Show all posts
Showing posts with label Software Development. Show all posts
06 April 2014
Cool Software Things Volume I
Continuos Refactoring
Refactoring is touching the code , when it starts to smell. Long story short summary, your code starts to smell when it has duplications, long method names, long parameter lists, bloodless objects or objects which has more than one responsibility or methods more than one task or parameters has more than one meaning. Addition to that you cannot have message chain with so-called object orientence with so many delegations. And Don't forget Your code should be the documentation and documentation should be your code so writing comments are something bad, your code should be self explanatory and not require comments to explain how implementation is working.(Excluding commenting on interface. comments on interfaces are explaining the contract.). You may need refactoring if your code has one of those and here is How to do it? Answer 1, Answer 2
refactoring should be a continuos activity as you grow your product. Adding a new fix, adding a new feature, adding a new test should trigger refactoring request.
Right Software Methodology
So far I have been in the organisations applying Waterfall, SDLC, Agile. I believe software methodology is key interface in implementing software management. However What I observe is implementing software methodology is also quite important as selecting them. Companies should be aware taking the methodology as a template and applying to their own way of workings. I strongly believe In the wrong implementation of Agile you can end up with having less productive team than a flexible waterfall team. Methodology you choose should be lightweight, and you should not dictate the methodology by repeating terms and philosophy like a parrot all the time. This should be consumed naturally. The way you apply and needing should be the common sense.
For a brand new organisation my advise would be to apply the procedure below;
1. pick NONE.
2. continue working
3. struggle for a certain issue,
(you will definitely see people crying on certain things)
(your people will cry differently than the others, so don't copy paste)
4. search for an agile practice
5. apply the found practice or create a new one together
6. return 2
Delete Code
Comparing the test done, (unit test, integration test, black box test, white box test, functional test, verification test, production test, customer acceptance test) and code written, it is obvious that written code is only a small fraction of the all tests done. Moreover to that, we are observing that only small piece of the code written is actually working. Most of the code is over-designed for some never happening future feature requirement, or afraid to touch because it is not understandable.
When we bring all this together , I believe deleting code is a very valid skill. if you see things over engineered than sooner or later you will end up having your code smell. But if you think a piece of software is unnecessary but somehow that part is tight to another code or not necessary at all , than question it. This will save considerable amount of unit testing time and let other developers save their time to focus on the valid part when trying to understand the code or maintaining it.
Next: Api Design, But, Extending Runtime, Ramp up fast, Immutability, Water, Smallest thing that works
04 July 2010
HeidiSQL - a free MySQL front-end
a lightweight fast and flexible interface to Mysql.
I strictly suggest this nice tool for Mysql Users
for further info : http://www.heidisql.com/
I strictly suggest this nice tool for Mysql Users
for further info : http://www.heidisql.com/
20 March 2009
ALL I LEARNED
Hi,
I am dealing with JEE and Java Development since 2006 June, in a large-scale marketing&telco company.
Time to market companies have common property, this is speed.
This speed word, can harm software development soul therefore it is quite hard to be a soldier in such an army. But this teaches you; discipline should be your guide.
My experiences, mistakes, faults, successes teach me several rules, in this very short(or very long) time period.
I've decided to note tens of them on my web log. If you want to earn yourlife as a developer, at least you should read them.
1. Never give a deadline , until you understand what is your task.
2. Never start to code , until you pretty sure about your development plan.
3. Arrange meeting(s) to yourself for just thinking on exceptions after development ends, and while development continues.
4. Test it, Do Test it, Do Test What you create. Test Yourself.
Never, Never, Never Trust Your QA Member.
5. Documantate what is going on, with all details but with 0(zero) unnecessary information. Your document should not be documented at the end. It should be a living period. It should start at the first day and you will not say documentation is finished until you put your code to the production.
6. Never give any support until He or She(Analyst,Tester,Developer,Support Member,Operation Contact..) right to ask it.
7. Never forget to report, any unplanned task.(Mail,Defect,Question)
8. Feel free to remove any detail,that makes you un-disciplined
9. Be Cool, Never hurt any of your colleague. Please do not forget, any of us can make mistake. Mistakes are temporary, but words are long lasting.
10. Lastly, but certainly not the least; Keep Yourself UPDATE!!! Always search for innovation.
I know the question will come as; WHEN?
Believe, it is more expensive otherwise :)
I am dealing with JEE and Java Development since 2006 June, in a large-scale marketing&telco company.
Time to market companies have common property, this is speed.
This speed word, can harm software development soul therefore it is quite hard to be a soldier in such an army. But this teaches you; discipline should be your guide.
My experiences, mistakes, faults, successes teach me several rules, in this very short(or very long) time period.
I've decided to note tens of them on my web log. If you want to earn yourlife as a developer, at least you should read them.
1. Never give a deadline , until you understand what is your task.
2. Never start to code , until you pretty sure about your development plan.
3. Arrange meeting(s) to yourself for just thinking on exceptions after development ends, and while development continues.
4. Test it, Do Test it, Do Test What you create. Test Yourself.
Never, Never, Never Trust Your QA Member.
5. Documantate what is going on, with all details but with 0(zero) unnecessary information. Your document should not be documented at the end. It should be a living period. It should start at the first day and you will not say documentation is finished until you put your code to the production.
6. Never give any support until He or She(Analyst,Tester,Developer,Support Member,Operation Contact..) right to ask it.
7. Never forget to report, any unplanned task.(Mail,Defect,Question)
8. Feel free to remove any detail,that makes you un-disciplined
9. Be Cool, Never hurt any of your colleague. Please do not forget, any of us can make mistake. Mistakes are temporary, but words are long lasting.
10. Lastly, but certainly not the least; Keep Yourself UPDATE!!! Always search for innovation.
I know the question will come as; WHEN?
Believe, it is more expensive otherwise :)
02 November 2008
Clientside + Serverside = Web Service Development
Since 2006, i am dealing with web services and its technologies.
I faced with many cases, usage of webservice as a bulk of data tronsporter,
uddi tools, usage of endpoints, writing pojos which turns to autogenerated web service,using xfire,axis,axis2,servicegen etc.
Now i will mention about none of these. I will mention about social side of web services.
Social Side? Yess!! Sure It is.
The Ones, do not know the web service technology, i can simplify.
Dramatic attribute is interoperability. This is;(You have the common language) you are technology and company and engineer and tool independent. Here it is, You have a protocol, its standarts are open, if you use this, you can communicate via network resources.
Ok for this Two Task Needed;
1) A guy to implement server side. --> I will call him as heroic.
2) A guy to implement client side. --> I will call him as slave.
This is the article that i int to write many months ago howeever today is more suitable to mention about it.
I will talk about theese 2 roles, heroic and slave.
heroic is powerfull, becouse he knows the system,(because data inside his system will be returned) he determines the datatype to return, he designs. !!!
Question will be asked to him?He will documentate!! He will answer. You need the information on his head.So he is big. He is incredible.
Slave is very poor. He does not know anything. He even does not know the parameter(s) to send. Without Heroic he can do only nothing. Unless full documentation of code and system or javadoc or smthg like that supplied, he has only a web service uri. He is nothing. He need to ask question(s). What will be returned? What does it mean? Which return code means success? He will call, He will mail, He will disturb amazing man.
Lets make them communicate;
S: Hello, I am S, We should Call WS deployed on your server. I think you are responsible, Can you help?, I need to ask some question.
H: I am very busy, I think you have uri of the service. What you want more?
S: AA, yess!! yess!! i have the web service uri. Aprreciate for this :) But May i ask Which parameters to send, at least examples..
H: Aaargh , Hey Men, I do not have that much time right now, But i can send it to in 2 days time, if you can approve it to my boss(manager)
S: Thank you very much, You are great, Thank You, Thank You, You are Hero ...
H: ok..
After this talk Slave calls heraic s manager manager is not reacheable.
In two days time he can reach manager and manager approve(if slave is lucky) Heroic as a resource.
After 6 days (2 days weekend , 2 days approval, 2 days Heroic reponse)
s: Hello, We have talked last week, i can send to parameters but i get IO exception, Most probably its from Firewall settings.
H: yes yes, you should be defined to our firewall.
S: Ok but why you did not make it? Sorry.. How can we make it? May you help?
H: Oh noo.. Our Analysts is dealing with such staff, Please contact to ...
S: Thank you very much, You are great, Thank You, Thank You, You are Hero ...
H: ok..
As you see such conversations occur when web service development start.
But this is wrong.
Web Service development is different from web or middleware or database development.
Its a teamwork. Altough they can be from other countries or other companies, Client and Server is a team.They are one body. And the members(developers), should also be interoperable.
This is clear, Client Side Web Service Development is harder and help from server side is needed
My Methodology is;
Write Test of Web Service, (Make Test Fail)
Documantate What you will Write
Write Web Service(MAke Test PAss)
Update Documentation
Call it from 3rd party tool.
Javadoc it.
Warn Project Manager and Analyst About firewall and network settings.
Send it to test
And Warn Tester to Make Integration Test, and firewall and network settings for TEST enviroments.
Update Documentation After QAS test
My method is the ideal one (it can also be improved), But when i am client i cannot see such behavior. If I am communicating with web service
deployed to other country, situation is more dramatic, Almost dramatic as above. :))
If you divide web service development into 2 part, as Client And Server this means you fail.Development has one part. If you succesfully deployed your service, if it passes from performance tests,if your QA Member says it is ok, This does not mean it is ok. Because they are not testing your documentation. And Client one needs it. If he can not able to call your web service. This means you did nothing!!! Therefore You are building client side and server side together.
At last i can say, When your systems communicating each other , you developers, are also communicating . So you as a developer should support interoperability.
This communication is so important. For me, It is more important than tools you use.
Lastly, Regardless of writing server or client side, if communication fails,you fail.
Happy :)
I faced with many cases, usage of webservice as a bulk of data tronsporter,
uddi tools, usage of endpoints, writing pojos which turns to autogenerated web service,using xfire,axis,axis2,servicegen etc.
Now i will mention about none of these. I will mention about social side of web services.
Social Side? Yess!! Sure It is.
The Ones, do not know the web service technology, i can simplify.
Dramatic attribute is interoperability. This is;(You have the common language) you are technology and company and engineer and tool independent. Here it is, You have a protocol, its standarts are open, if you use this, you can communicate via network resources.
Ok for this Two Task Needed;
1) A guy to implement server side. --> I will call him as heroic.
2) A guy to implement client side. --> I will call him as slave.
This is the article that i int to write many months ago howeever today is more suitable to mention about it.
I will talk about theese 2 roles, heroic and slave.
heroic is powerfull, becouse he knows the system,(because data inside his system will be returned) he determines the datatype to return, he designs. !!!
Question will be asked to him?He will documentate!! He will answer. You need the information on his head.So he is big. He is incredible.
Slave is very poor. He does not know anything. He even does not know the parameter(s) to send. Without Heroic he can do only nothing. Unless full documentation of code and system or javadoc or smthg like that supplied, he has only a web service uri. He is nothing. He need to ask question(s). What will be returned? What does it mean? Which return code means success? He will call, He will mail, He will disturb amazing man.
Lets make them communicate;
S: Hello, I am S, We should Call WS deployed on your server. I think you are responsible, Can you help?, I need to ask some question.
H: I am very busy, I think you have uri of the service. What you want more?
S: AA, yess!! yess!! i have the web service uri. Aprreciate for this :) But May i ask Which parameters to send, at least examples..
H: Aaargh , Hey Men, I do not have that much time right now, But i can send it to in 2 days time, if you can approve it to my boss(manager)
S: Thank you very much, You are great, Thank You, Thank You, You are Hero ...
H: ok..
After this talk Slave calls heraic s manager manager is not reacheable.
In two days time he can reach manager and manager approve(if slave is lucky) Heroic as a resource.
After 6 days (2 days weekend , 2 days approval, 2 days Heroic reponse)
s: Hello, We have talked last week, i can send to parameters but i get IO exception, Most probably its from Firewall settings.
H: yes yes, you should be defined to our firewall.
S: Ok but why you did not make it? Sorry.. How can we make it? May you help?
H: Oh noo.. Our Analysts is dealing with such staff, Please contact to ...
S: Thank you very much, You are great, Thank You, Thank You, You are Hero ...
H: ok..
As you see such conversations occur when web service development start.
But this is wrong.
Web Service development is different from web or middleware or database development.
Its a teamwork. Altough they can be from other countries or other companies, Client and Server is a team.They are one body. And the members(developers), should also be interoperable.
This is clear, Client Side Web Service Development is harder and help from server side is needed
My Methodology is;
Write Test of Web Service, (Make Test Fail)
Documantate What you will Write
Write Web Service(MAke Test PAss)
Update Documentation
Call it from 3rd party tool.
Javadoc it.
Warn Project Manager and Analyst About firewall and network settings.
Send it to test
And Warn Tester to Make Integration Test, and firewall and network settings for TEST enviroments.
Update Documentation After QAS test
My method is the ideal one (it can also be improved), But when i am client i cannot see such behavior. If I am communicating with web service
deployed to other country, situation is more dramatic, Almost dramatic as above. :))
If you divide web service development into 2 part, as Client And Server this means you fail.Development has one part. If you succesfully deployed your service, if it passes from performance tests,if your QA Member says it is ok, This does not mean it is ok. Because they are not testing your documentation. And Client one needs it. If he can not able to call your web service. This means you did nothing!!! Therefore You are building client side and server side together.
At last i can say, When your systems communicating each other , you developers, are also communicating . So you as a developer should support interoperability.
This communication is so important. For me, It is more important than tools you use.
Lastly, Regardless of writing server or client side, if communication fails,you fail.
Happy :)
Subscribe to:
Posts (Atom)