Vision and dreams are the blueprints of soul and achievements.
-Mohammed Ahmed F

Showing posts with label Chief Administrative Officer. Show all posts
Showing posts with label Chief Administrative Officer. Show all posts
Full Stack Web Developer opening in Chennai

Full Stack Web Developer opening in Chennai

Coovum Smart Systems (www.coovum.com) is hiring for its expanding team for the post of Software Engineer (Full Stack Web Developer).

About - Coovum is geared to harness the power of IoT, Robotics & AI with the world-class solutions by leveraging technologies and business growth into new market segments started in Jun 2015 with about 25 dedicated team members.

Qualification - Any diploma / degree in Computer Science.

No. of Positions: 3 Experienced & 2 Freshers.

Candidates with at least 1+ years of experience working in backend technology PHP, MySQL, REST API, JSON, Laravel framework only need to apply.

Interview Process for Experienced candidates:-
Online test.
Candidates will be tested on Data Structures, Algorithms, OS & Networks, Web Technology and Security.
Knowledge of Python, IONIC / PhoneGap / Hybrid App Development will be a plus.
Preference will be given to candidates with 2+ years of experience.

Interview Process for Freshers:-
Online test.
Candidates will be tested extensively on Data Structures, Algorithms, OS & Networks, Web Technology.
Knowledge of Python, IONIC / PhoneGap / Hybrid App Development will be a plus.
Preference will be given to candidates with highly demonstrated skills only.
Preference will be given to competitive programmers with a good rank on HackerRank platform.
Salary package:
Experienced - will not be a constraint for the right candidate.
Freshers - best in industry.

Date of Joining:
Experienced - candidates with 30 days notice period. Preference will be given to candidates already serving the notice period.
Freshers - 1st Dec 2017.

Apply on or before 16-11-2017 to mohammedahmed_f@yahoo.com
10 Mistakes done by the developers

10 Mistakes done by the developers

Learning from the top 10 mistakes developers make

I present to you a list of a few common mistakes new devs (and sometimes even experienced) usually do. I believe that learning from these mistakes would be of some help to you. So, here is my pick of the Top 10 mistakes.


10. Trusting user’s input
Never trust the inputs provided by the end user. Also don’t blame them, mostly they do it unintentionally. We all make mistake mistakes. This might not be of great concern to them but a piece of bad data could potentially bring down the application or cause compliance-related issues. Apart from naive non-technical users we also have users with a certain level of technical know-how which they could potentially use to circumvent the system and get their work done. These are the users who pose a threat to your application and application needs to be safeguarded against the malicious activities.

The only option to save from landing into trouble at a later stage is to build a strong validation with self-explanatory and human understandable error messages. Cryptic messages hardly help the naïve user accomplish any task. Validation should be done in both user interface and database level just to be sure that even if by some means front-end validation was turned off the application still does not accept trash values.

9. Manual unit tests
Code changes that you do, needs to undergo unit testing and further rounds of Quality Assurance testing. All tests or at least a few minimum number of tests need to be done to ensure that the changes you made in one unit of code do not have side effects on the others. This is a necessary evil. Having automated unit tests and integration tests save you a lot of manual efforts in validating side effects of the changes.

8. Skipping documentation
The evilest thing that you can do is skipping documentation. Off course you can read the source code and try to understand the functionality. Reverse engineering the functionality from the code is a daunting task. This is good enough for a tiny functionality but definitely not a go for the entire application.

"Requirement changes, code changes and more frequent - members of development team change."

Knowledge about the application might not be transferred 100%. Sometimes people just forget. You need not create dozens of documents, create only a few like requirement specification and technical document and make sure to keep them updated, this should be a part of a stringent process which needs to be followed at any cost and must be accommodated in the project planning. This would help at later stages when the application is in support/maintenance phase.

7. Forgetting about Audit and Error logging
Not all end user/stakeholder would be bothered about cross-cutting concerns like audit logs and error logging. A stakeholder would simply come with a one-liner requirement which you would have to drill down till it becomes good enough to work on and deliver a solution addressing the stakeholder’s problem.

Data change audit and error logging might never be a part of user’s requirement but is implicit that it needs to be maintained. One fine day user would simply approach support team and ask them to provide data related to access and roles or some business critical data required for compliance or audit purpose and then you would have nothing to share.

Error logging is also crucial, you might do defensive coding but you never know what might fail in such cases effective error logging comes in handy. Monitoring error logs and trying to work on resolving recurring error would help in making your application more stable.

6. Careless use of privileged access
First and foremost, full control and access should never be provided. The system cannot protect itself from malicious activities if you leak the superuser or privileged account passwords. Risks involved in the reckless usage of privileged access should be a part of learning for inexperienced new members of development or support team. There might be times when you would have to make a modification to production database and having privileged access can lead to many issues.

“With great power comes great responsibility”

I remember once unintentionally deleting data from the master table and the query was auto-committed. I went cold but soon realized I had taken backup of the data, phew! It is always good to provide limited access for data modification via an interface which keeps data backup. One should also note that this tool should also be capable of doing bulk operations, else you will find yourself doing manual updates for a very long time.

5. Configuration menace
Scattered configurations in different files and database is a menace. Change in a configuration which affects multiple applications would have to be replicated in many files and databases. This probably is not much of an issue if you have a handful of applications but would soon become an overwhelming task when you have hundreds of application in an enterprise environment. Moreover, naked passwords in config files are yet another threat. If configurations are database driven then it reduces the later hazels also safeguards sensitive configuration entries.

4. Hard-coded time bomb
Hard coding values in the program are definitely a bad practice. Strange issues could occur because of the hardcoded value which silently sits there in your source code. One such incident is when you make use of hard-coded values for some maximum number, assuming that the maximum will not be hit. Such cases could take months or years to raise an error. Combined with no error logging and you will be in a very bad situation. Try to avoid hard-coded values. Move them to configuration variables if needed or try to completely avoid situations which would require them.

3. Prevent Burnouts
Working continuously without any breaks will just lead to burnouts. You should always take breaks at regular intervals. When you are overworked even doing simple things take a whole lot of time.

Set small achievable milestones for yourself and don’t forget to reward yourself for it. Chocolates, cakes, quick games just about anything that makes you happy and feel free. Learning how to prevent burnouts will make you more productive.

2. Code / Suggest for building resume
Having a strong resume with a listing of all new technologies is great but don’t just do it for inflating the resume. Learn them but use them only if you see the benefit and high maintainability over the existing things. Sometimes adding new tech options would not even be required.

Increasing the complexity should at least pay off in providing ease of maintainability. So I strongly believe that when you suggest some solution, check if it makes the application easy to maintain and makes everybody’s life easy.

1. Finding comfort zone in just one technology
Being a ninja in one technology is awesome and is always beneficial. But don’t stay limited to one technology. Try to expand your knowledge, sure there is a learning curve but challenging yourself helps you become a better technologist – a person who uses various technologies as effective tools and provides business enabling solution.

Times change, technology may become obsolete but your learning should never stop. Always try to explore new technologies and try weighing the pros and cons before using it as a solution for solving a problem.

I would like to hear about your views on these points. If you have any experiences to share, go ahead and post a comment. Remember…

The only real mistake is the one from which we learn nothing. ~ John Powell

This article was originally published on Skill Hive Blog
Free Aptitude Test Practice resource

Free Aptitude Test Practice resource

Folks,

It was a pleasure to add PracticeReasoningTests to our Aptitude Practice Website List upon request to add, from Mr. Edward Mellett, Founder & CEO of PracticeReasoningTests.com






It is always our pleasure to add and recommend free resources for the betterment of the student's fraternity.

PracticeReasoningTests.com

-Admin.

Your queries will be answered via Quora

Dear Readers,

Feel free to ask your queries. I will answer them on Quora!

You can ask me anything related to Computer Science / Applications, CS Education, Career in IT Industry, life or personal problems, blogging, & start-up a company!

Feel free to ask! Click on the above image to check my answers or to ask one!

Remembering Dr. APJ Abdul Kalam Sir


Born in India, Learned in India, Served for India, Died in India.

Department of Awesomeness pays its respect to the 11th President of India and a Teacher Dr. A. P. J. Abdul Kalam Sir.

Dr. A. P. J. Abdul Kalam, The People's President of India.

Famous Quotes of Dr. APJ Abdul Kalam Sir:

“Failure will never overtake me if my determination to succeed is strong enough.”

“Don’t take rest after your first victory because if you fail in second, more lips are waiting to say that your first victory was just luck.”

“Man needs difficulties in life because they are necessary to enjoy the success.”

“If you want to shine like a sun. First burn like a sun.”

“Be more dedicated to making solid achievements than in running after swift but synthetic happiness.“

“For me, there are two types of people: the young and the experienced.”

“You have to dream before your dreams can come true.”

“Climbing to the top demands strength, whether it is to the top of Mount Everest or to the top of your career."

“Let us sacrifice our today so that our children can have a better tomorrow.”

"Look at the sky. We are not alone. The whole universe is friendly to us and conspires only to give the best to those who dream and work."



Mohammed Ahmed F
Chief Administrative Officer,
Department of Awesomeness.

Business Development Officer in Chennai

Wanted Business Development Officer with excellent communication skills and innovative marketing strategies.


Company Profile: It is a leading provider of smart technologies that focuses on providing innovative solutions 

combining sensors, wireless, embedded and computing systems for manufacturing, retail, healthcare, security, and logistics industries.

Note: Marketing is a commitment, not a campaign.

Job Title: Business Development Officer.

Responsibilities: Identifying list of potential clients, sending proposal, give presentations to clients, following and sealing the deal.

No. Of Positions: 03.
Qualification: B.Com. / BBA
Experience: 0 to 2yrs experience.
Location: Anna Nagar, Chennai
Last date to apply: 21/05/2016.

Send your resume to mohammedahmed_f@yahoo.com

Mohammed Ahmed F