Showing posts with label Article. Show all posts
Showing posts with label Article. Show all posts

26 May 2014

How looks typical experience of looking for job for junior software developer (Based on my example)

WARNINGS:
This is NOT a professional advice.
It based on personal experience only and resources read on the internet.
It will contain lots of grammar mistakes.
Drink double espresso and energy drink as the article is long and boring.

Article moved to my personal blog :


22 November 2013

Goodbye Winamp!

Winamp.com announced something sad.
"Winamp.com and associated web services will no longer be available past December 20, 2013. Additionally, Winamp Media players will no longer be available for download. Please download the latest version before that date. See release notes for latest improvements to this last release.Thanks for supporting the Winamp community for over 15 years."

Legendary 2.x series .
..  One of must have application for Windows. It was a few issues ,but it was very stable and works smoothly.A legend!

Epic fail 3.x series .
..  It was a ugly monster. Example of  how to destroy all reputation in one update. It was so unusable,that most of my friend stays on 2.x ,but  I decided to find alternative and I start using Foobar2000.

Then 5.x series .
.. but i was already fan of Foobar2000 and was no reason for me to back.
I actually still use Foobar2000.

However.I haven't abandoned Winamp completely .
In 2011 It turns out,that they have very good application for Android. OK, On beginning, it was  annoying and buggy (as my applications for android),but after few updates it change into very good music player application for Android,which I like to use.

Shame,but  all living legends must die.
It happens to technologies like cassettes and it happens to software ... like Winamp.

I will miss this sentence:
"Winamp, it really whips the llama's ass!"

Goodbye Winamp and Thank you.

Yesterday, I read about what's like to fail. Question for today is.. how's feel people who spent life on project that is about to end?
Like people,who works on Winamp for 15 years ..
I really would like to know..to read they story ...

24 September 2013

Personal Security: How to detect Scam emails.

I start from
If you have any suspicion about content in  e-mail,then DO NOT TRUST.
 NEVER EVER click on any link in email  and do NOT type any card details.

WARNING!
In case if you look on this blog,because you accidentally click on link and gave any details.
DO NOT READ MORE.
CALL YOUR BANK STOLEN CARD HELPLINE ....and block your card.NOW!
THEN. .. continue read.



TO DO LIST ,WHEN EMAIL LOOKS SUSPICIOUS IN ANY WAY:
  1. Check who sent you email  (however ,it is quite easy to cheat ).
  2. To figure out ,where link will go you can move cursor over link and see (usually in web browser on bottom .If you can easily spot difference between normal bank url and dodgy one.
  3. NEVER EVER click on any link in email  and do NOT type any card details.
  4. Is e-mail looks different (even tiny detail like weird grammar ,few typo different skin for email) ,then thread this as potential scam.
  5. Is it any news in media about issue with your  Bank ?  In case,if you see news about  security problem with your bank,then wait until  they said that's sorted and follow advices.Always use known url.Do not use links from emails!
  6. No news? Check on website anti-scam website that provide Scam alert service like: http://www.ingraftedsoftware.com/aggregator/sources/3 and etc. 
  7. Copy message and paste to search engine  like  Bing/Google to figure out is message was reported as scam? 
  8. Still has doubt... call to bank's infoline or .. go to bank directly.

TIPS:
  1. Use email that for critical purposes only, (Email with banks, backup email for recovery from main email, BUT NOT FOR ANYTHING ELSE). (do not use any names that are relalted to you in any way.
  2. Keep copy of emails from your bank,so you can easly spot difference in case ,if you have any doubt.


Example of  recent scam e-mails from "banks".

" Dear Valued Customer,

Your Nationwide account needs an important verification
for security purpose, please kindly click here now to verify
your account for a faster easier and more efficient banking experience

Thanks
 Nationwide Building Society " 

or

" Starting from September 25 2013, 
Lloyds bank introduces new authentication
procedures in order to better protect private information of our account holders.
Please note that accounts that are not reviewed within 48 hrs are subject to termination.
To avoid service interruption click here to avoid services interruption

Thank You.
Lloyds Banking Group."
or

"Our record shows that you have a refund slated on your card account
due to charges made against your card account by us.
We do apologies for this mistake which was caused by errors from our system.
This transaction cannot be completed due to the errors present in your account information.
You are required to click on the LOGON below to fix this problem immediately.
Please note, it will take 3 working days to credit your account with the refund.
LOG ON HERE (<dogdy link)
Thanks
NatWest Card Services" 
or

"Dear Valued Customer,

We have encountered a generic error on our database server which compromised
some of our customers account due to the circumstance of the error.
We implore you to make sure your account was not compromised due to this error.
Kindly verify your information for safety purpose
Click Here to verify now
We are sorry for any inconvenience this may have caused. 

Yours Sincerely,
 Barclays Bank Plc. "

Stay safe! 

17 July 2013

What is a Inversion of Control Containers and the Dependency Injection pattern ? (including Useful link: article Martin Fowler )

Just in case.
This is about IT term. It is NOT about process of getting addicted from dugs.
Dependency injection is giving an object its instance variables (via constructor,method and etc) and remove dependencies from your code.
That would "inject" the "dependency" into the class.

This article has almost 10 years and is made by man is a agile knight and fighting for fame of agile development.

It is about  "Inversion of Control"   paradigm and his one of implementation the "Dependency Injection" pattern.It is worth to learn,when you start using spring framework and any containers that based on  "Inversion of Control"   paradigm.

If you have a clue what  Inversion of Control and   Dependency Injection are ,then  read these 2 micro article first.:

1)
http://stackoverflow.com/a/3140
It will you explain what    Inversion of Control  is.

2)
http://www.jamesshore.com/Blog/Dependency-Injection-Demystified.html
It will you explain what  Dependency Injection is.

After that , You should be read to read  Martin Fowler - Inversion of Control Containers and the Dependency Injection pattern. (You need above articles as Martin Fowler article is very academic ,which means write about simple things as complicated ,  confusing and mysterious  as is possible . )
(I suggest drink a strong coffee before you will read it.)

http://www.martinfowler.com/articles/injection.html

 A few quotes  from article (and 2 links):

" The Inversion of Control (IoC) and Dependency Injection (DI) patterns are all about removing dependencies from your code. " urini

" Dependency injection means giving an object its instance variables. Really. That's it. " James Shore

"When these containers talk about how they are so useful because they implement "Inversion of Control" I end up very puzzled. Inversion of control is a common characteristic of frameworks, so saying that these lightweight containers are special because they use inversion of control is like saying my car is special because it has wheels. "  Martin Fowler

" I've often heard the complaint that these kinds of service locators are a bad thing because they aren't testable because you can't substitute implementations for them. Certainly you can design them badly to get into this kind of trouble, but you don't have to. In this case the service locator instance is just a simple data holder. I can easily create the locator with test implementations of my services. " Martin Fowler

" A common reason people give for preferring dependency injection is that it makes testing easier. The point here is that to do testing, you need to easily replace real service implementations with stubs or mocks. However there is really no difference here between dependency injection and service locator: both are very amenable to stubbing. I suspect this observation comes from projects where people don't make the effort to ensure that their service locator can be easily substituted. This is where continual testing helps, if you can't easily stub services for testing, then this implies a serious problem with your design. " Martin Fowler

" If you use Dependency Injection there are a number of styles to choose between. I would suggest you follow constructor injection unless you run into one of the specific problems with that approach, in which case switch to setter injection. If you are choosing to build or obtain a container, look for one that supports both constructor and setter injection. " Martin Fowler

" The choice between Service Locator and Dependency Injection is less important than the principle of separating service configuration from the use of services within an application. " Martin Fowler
Interesting stuff.