Survive, this is the more powerful fuel you can have, the need to survive is a basic instinct that is there and when it’s pushed, it works and put people on motion.
People often move or react by different reasons, some have positive connotation (motivation, love, ambition…) or negative (fear, risk of accident, ambition…), anyway.
In modern professional live, the situation is quite similar. Depending how small is your comfort zone, you will have situations where you need to survive. You and the colleagues around you are under the same situation. You can look around and see:
- People who are in the comfort zone 8 hours a day, and they have no intention of go away from there. The day they are pointed to change, they burn out or survive.
- People who have cycles, being some periods of time on the comfort zone and then accepting challenges.
- People who is used to be out of the comfort zone, and are willing to continue in that way of life. They understand that situation as “another day in the office”, they cannot understand what others are doing.
This third group of people, when you combine them with the right skills and with the right motivation, then the result makes the difference.
In modern professional live, the reasons to survive are different:
- People hate to talk to others, they move to back-office positions or developer roles.
- People willing to do not stress, they will take service support or administrative jobs.
- People with lack of analytical skills, they will look for jobs where they can put in place their other intelligences.
Look for the needs of the people around you: what they hate, what the love, what they fear…
Read this article, it talks about the different phases of a professional career.
I see so many interesting comments and details on the article: 3 phases of a career, how to balance it with your live, comments about how to move from one place to other.
It’s really a nice and clear analysis.
The only thing I can add is, that if you are changing from one company to other, you should try to do the last big jump when you are around 42-45 years old. This was a suggestion commented to me by an HR person doing recruitment for her company.
American Productivity & Quality Center provides business
benchmarking, best practices, and knowledge management research. Their mission is to help organizati
ons to improve productivity and quality by discovering effective methods of improvement, broadly disseminating findings, and connecting individuals with one another and with the knowledge they need to improve.
Very useful information to learn about trends, facts, and relevant business data.
You have a portfolio of applications, and you receive the request of modernize it.
You do an analysis of the situation and then you have to decide what to do with each one of the assets you have.
The industry has developed a nomenclature to enable common understanding of what you can do. Here some of these actions you can perform to transform each one of your assets:
- Retain: take no action on the application. Sometimes there is not value or it is not the right moment to modernize.
- Re-host: move from one environment to other. It could be that you want to move to an infrastructure could or to other data center… (typically known as lift & shift).
- Convert: you keep the same functionality but change the platform where it is implemented or the language code. For instance there are so much companies unifying the platforms in one direction, so they can save some dollars on OPEX, and only need expertise on a platform.
- Refactor: You alter the application design while you keep the functionality. For instance I’m upgrading from joomla 2.5 to joomla 3.x to enable new design.
- Revise: you refactor the application and develop new business capabilities.
- Rebuild: review the applications business requirements, align them with the new needs (it can be an increase or decrease of processes), finally develop the application from scratch.
- Service enable: with this action, you expose the business capabilities or processes externally through services.
- Consolidate: Merge multiple applications to small amounts of units.
- Upgrade: typically used for COTS.
- Replace: you will find so many customized solutions that really can be replaced by a COTS that implement processes in a more standard manner.
- Retire: you do not need it, remove it!
On mobile applications time response is one of the key aspects of this ecosystem.
Some of the key points that influence on time response are:
1.- the type of application: native application or modified application from another application layer.
2.- The telecommunication channel used for the device (3G, 4G or Wifi connection).
3.- Testing of the solution: this is key for the solution, you not only need to test the functionality, you need to test Google web services, and other third party services to understand bottlenecks), test # of redundant users, etc… so many of the
4.- Architecture / platform decision, this will represent the main issue and one of the key decisions for the rest of the project. People working on robust business cases and a clear medium term road map do not use to fail on this point, but for the others the situation can be different.
If you are going to build a solution for mobile devices you will have to make so many questions about the type of user, #redundant people, peaks of use, look & feel. Sometimes the functional part is the easy part.
I need to remember this link, a good place for finding solutions for mobile issues.
This official announcement, talks about the fact that the default search experience for signed-in users will be delivered under SSL.
What is the impact? People working on their web sites use to utilize this data to optimize their sites; with this move this data will not be available for them (as the majority search with their google user). The searches done without a logged in user will be visible.
What is going to be the next step?
- Is Google going to sell this data through Google analytics?´I guess so
- Is google to reserve the confidentiality of the searches done by its users? I guess no.
Information is value and it means money, in this case for Google.
Google continues writing rules (because they can do it) and by the moment as soon as almost all people uses their services (initially by a cheap price), they have the right to obtain a return of their investment.
You can accept it or try to play to other game.
The security on mobile applications continues being a big question for me, mainly due to the lack of security.
I found Confide, which lemma is:
Spoken words disappear after they’re heard. But what you say online remains forever.
With confidential messages that self-destruct, Confide takes you off the record.
With the time, all have used applications that fall into a situation where you leave them or you cannot use anymore. Below is my particular obituary of applications.
1.- Personal use:
- I used to access to Google reader, and not it’s closed. I had to find an alternative (Feedly, 2013).
- Now I have seen that my yahoo will be closed (2014). The reasons are the same: “we want to focus on other and better applications for you”.
2.- Professional live:
- Access through Citrix, 2006.
- Lotus Notes (coming soon).
- Blackberry (coming soon), the company I work with announced that they will not distribute BB anymore. It is a sad news for me that started using it in 2004.
3.- Small business:
- Webnode, by basic business reason it was replaced by Prestashop in 2013.
- Blogger, replaced by WordPress.