Powered by Blogger.
🌏World roaming Software Technology Evangelist. Proud Indian, Bought up from Coimbatore, Tamilnadu, INDIA. Pointing towards share of Knowledge. 😎
  • Programming ▼
    • DotNet
      • C# Coding Standards
    • Cloud
    • Microsoft 365/ SharePoint
    • SQL
    • Angular / ReactJS / NodeJS
    • Salesforce
    • Magento
    • Python
    • Mobile App Development
    • Database
    • DevOps
    • Automation Testing
    • User Experience
  • Learning ▼
    • Roadmap
    • Trainings
    • E-Books
    • Quick References
    • Certifications
    • Self Improvement
    • Productivity
    • TED Talks
    • Kids Programming
  • Software Engineering ▼
    • Agile
    • Software Design
    • Architecture Samples
    • Best Practises
    • Technologies and Tools
    • Open Sources
    • Free Softwares
  • Leadership ▼
    • Program Management
    • Product Management
    • Project Management
    • People Management
  • Job Search ▼
    • Interview Tips
    • Career Handbook
    • Resume Templates
    • Sample Profiles
    • Cover Letter Samples
    • HR Interview Questions
    • Job Websites List
    • Coding Site Links
    • TedEx Talks
    • International Jobs
  • Emerging Topics ▼
    • Innovation
    • Machine Learning
    • Artificial Intelligence
    • Generative AI
    • AI Tools
    • Big Data
    • Data Science
    • Data Analytics & Visualization
    • Cyber Security
    • Microsoft Azure
    • Amazon Web Services
    • Cryptography
    • ChatBots
    • Internet of Things (IoT)
    • Mixed Reality /AR/VR
  • Misc. ▼
    • Travel
    • Photography
    • Health Tips
    • Medical Tips
    • Home Designs
    • Gardening
  • Favourite Links ▼
    • Saran Kitchen Hut
    • World of Akshu
    • Saran & Akshu - Other Links
Referred Link 
https://philmckinney.com/six-practices-of-successful-innovators/

successful innovators

Successful innovators seek out mentors.

One of the things successful innovators have in common is that they seek out wise mentors.  Mentors usually have reached a level of success in their professional experience. They may offer guidance and advice in both professional and personal areas.
Mentors are an important aspect of growing as an innovator.   The smart innovator knows he or she can’t go it alone.  A mentor can make the difference between taking the right path or veering off in the wrong direction.  Most successful innovators have at some point been guided by a mentor, a trusted advisor. In some cases, successful innovators have had multiple mentors at different stages of their career.  Steve Jobs, in the Walter Isaacson’s biography, acknowledged key people who influenced his career and life. In fact, Bill Campbell, who mentored Steve, mentored an entire hall of fame of successful innovators.
Early in my career, my mentor, Bob Davis, set the course for my career.  Without his influence, advice, and guidance, I would not have achieved the success I’ve had in my career.  My blog, podcast, and book are my efforts to share my experience and knowledge.  My desire is to build a community and encourage others in the innovation arena.  It’s my way to pay back Bob for his impact on my life.
When you find that great mentor and success ensues, you’re motivated to pay it forward.  Richard Branson credits success with Virgin Atlantic to the mentorship he received from Sir Freddie Laker.  As founder of Laker Airways, Sir Laker had the experience and expertise and was willing to share that.  Years later, Branson has launched Virgin Startup to help a new generation of entrepreneurs.

Successful innovators surround themselves with like-minded people.

Successful innovators engage with people who have similar values and goals.  They put themselves in an environment where they can talk about their ideas and grow in a creative sense.
A group known as “The Vagabonds”, were the innovators of their day.  Their ranks included Thomas Edison, Henry Ford, Harvey Firestone, John Burroughs and were joined by others.  They banded together to go on annual camping expeditions. They took a break from their busy lives, got outdoors, and enjoyed nature.  But they also engaged in the exchange of ideas. Wouldn’t you love to be sitting around the campfire listening in?   Here were a group of men with vastly different expertise and endeavors. Yet, they had the common ground of being innovative thinkers.
Finding an environment to share your ideas and encourage others is another step towards success.  Today, there are a number of ways to connect with other innovators of diverse backgrounds.  One venue I attend is the annual TED conference. It’s a great way to interact with others at the forefront of innovative thinking.  Are you in search of place for open exchange of innovation ideas? The Innovator’s Community is a private, online group that allows you to engage with fellow innovators.   

Successful innovators are not afraid to step out of the comfort zone.

Successful innovators are not afraid to leave their comfort zones.  Sometimes this means venturing out on your own when the people around you don’t see your vision.  It could also mean getting out of your routine, the comfort of the office, or cushy job, and exploring what’s out there.   Maybe it’s trying something outrageous that you’ve never dared to do before.  Getting out of your comfort zone can open up new avenues and give you a fresh perspective.  
It wasn’t until his sixties that Harland Sanders developed his successful fried chicken franchise.  Before that, he had dabbled in cooking and serving his secret recipe fried chicken. But it wasn’t his main source of income.  Until his franchising success, he went through a range of jobs. Railroad worker, insurance salesman, ferry boat owner, lawyer, among other things.  Harland was always trying something new and different. Whether it was out of necessity or choice, Harland never sat back and got comfortable.
Jeff Bezos was in a successful position at investment firm D.E. Shaw when he decided to leave it, borrow money, and start Amazon.  Stepping away from financial security into the unknown with potential for failure did not concern him. What concerned him were his regrets if he didn’t take that chance.  

Successful innovators value alternative approaches and unique perspectives.

Another quality that successful innovators possess is that they try to see things from different perspectives.  They look for alternative approaches. They step out of their personal experiences and biases to examine what others are thinking and why.
In the eighteenth century, seafarers faced uncertain danger at sea.  Only half of the navigation equation was known. Sailors could determine latitude, but no one had figured out an accurate way to find longitude.  This caused loss of ships and lives due to the missing piece in the navigation puzzle. Astronomers, scientists, and mariners worked to find a solution.  The British government opened up an opportunity to the public to solve the problem. The government offered the Longitude prize for the person who could develop an accurate way to measure longitude.  
The unlikely winner was a clockmaker, not an astronomer, mariner, or scientist.  Even Isaac Newton doubted the unique approach of John Harrison. Harrison knew clocks and carpentry.  He developed an alternative approach to those proposed by leading scientists and astronomers. His maritime clock could maintain time accurately of a reference point despite conditions at sea.  Harrison faced criticism. His perspective was not well received. The Board of Longitude, who reviewed and awarded the Longitude Prize, were a smug bunch. Their doubts of Harrison’s solution delayed the process.  His innovation took many years to develop and refine. The naysayers only compelled him to perfect his marine clock. He stuck with it despite the obstacles. By applying his skills and knowledge in one area, he was able to solve a problem in a seemingly unrelated field.  
Seek out honest opinions and don’t be held back by assumptions.  Even if you’re a lone innovator not working with a team, you can still find people to give a fresh perspective.  Ask someone with a different background to review your product. Seek out a younger or older family member’s opinion.  Actively listen to others’ points of view to enhance your own understanding. Listening to diverse opinions will give you a better grasp of viewpoints in the greater population.  Talk to people who think differently from you.  Maybe it’s someone whose opinion you usually disagree with.  They may point out flaws in your approach that help you perfect your product or possibly decide to pivot.  

Successful innovators never stop asking questions.

Successful innovators have an innate curiosity.  This means they never stop asking questions.  By asking the right questions, they are challenging assumptions and exploring new ways of thinking about things.  They refuse to accept the premise that, “This is the way it’s always been done.” Their questions compel them to make radical changes to the way things are done.  As result, these successful innovators create major disruption to industries. Innovators remember specific questions they asked that led to their successful ventures.  In a study on successful innovators, Michael Dell told researchers(Harvard Business Review, Dec 2009) he wondered “why a computer cost five times as much as the sum of its parts.”  
I firmly believe that asking questions is the life breath of innovation.  Hence, I developed the Killer Questions to spark the thought process for innovation.

Successful innovators set aside time to think.

Both deep focus thinking and spontaneous thoughts generated through moments of relaxation can produce innovative ideas and solutions.  People who are too busy with daily tasks and meeting expectations, don’t have the freedom to allow their mind to wander.  The mind needs that free space to be creative. You have to give room for thoughts.  Successful innovators set aside time to think.  This means setting aside a time and a place. It can also mean taking a break from work to help your mind relax.  Some of the best ideas happen while relaxing or doing something enjoyable that is unrelated to work. Observing nature, like the Vagabonds did, away from daily tasks opens the mind to new perspectives.  
These six practices are by no means a comprehensive list. These are just some of the practices you can adopt and use as you strive towards your innovation goals.
Referred Link
https://www.telerik.com/blogs/creating-an-angular-7-app-with-aspnet-core-step-by-step-guide

AngularT Light_870x220

Finally, we have a new major version of Angular, which is version 7. The reason I use the word “finally” is not just because people were waiting for the latest major release of Angular, but also because there were quite a few rumors about the features Angular 7 would offer. Especially since the April Fool’s article published with the title "Top 4 Changes Coming In Angular 7.0."
The Angular team officially announced Angular 7 just a few days back, and Angular 7 has introduced some pretty awesome features, like improvements in Angular Material, Performance improvements, and CLI improvements to name a few.
In this article:
  • We will see how to create Angular 7 applications with ASP.NET Core SPA template
  • We will also see the features introduced with this major release
  • I will demo some of the Angular Material features introduced with Angular 7

Angular 7 With SPA Template

Let’s first see how to create an Angular 7 application with ASP.NET Core SPA templates using Visual Studio 2017. There are more ways than one to create an Angular 7 application with .NET Core, but let’s look at this one.
Make sure you have installed Visual Studio 2017 and the latest .NET Core SDK, as well as the latest version of Node.
In this approach, we will use the Angular template with ASP .NET Core.
Before starting, let us first update our Angular CLI to version 7. For this, open command prompt and run the command:
npm i -g @angular/cli
Once done, your CLI will be updated to version 7:
Angular CLI

Create the Angular Application Using .NET Core 2.1 Template in VS 2017

Once you have all these installed, open your Visual Studio 2017 -> Create New Project -> Select Core Web application:
ASPNET Core Web App
Click on “Ok,” and, in the next window, select Angular as shown below:
Visual Studio Angular
Visual Studio will create a well-structured application for you, which is currently in Angular 5.

Angular 7

If you open the package.json file in the ClientApp folder, you will notice the Angular version is 5.2, but we want to create an Angular 7 application.
So go to File Explorer and delete the ClientApp folder.
Click here to read more...

DATE AND TIME

Sat, November 24, 2018
9:00 AM – 5:00 PM IST
Add to Calendar

LOCATION

Microsoft
Prestige Ferns Galaxy
6/18, Bellandur Gate Road, Bellandur
Bengaluru, KA 560103
View Map


Agenda:

9.30 AM - 10.00 AM - Registrations
10.00 AM - 10.15 AM - Keynote, Deepak Rajendran, Microsoft
10.15 AM - 11.00 AM - Building modern conversations in Office365 with add-ins and actionable messages, Arunkumaran Varadharajan, Anjana Valsan, Kallu Sushma, Microsoft
11.00 AM - 11:15 AM - Break
11.15 AM - 12.15 PM - Power of Graph API & demo by Sathish Nadarajan, Microsoft MVP
12.15 PM - 1.00 PM - Immersive experiences on Microsoft Teams App Platform by Vishrut Shukla, Microsoft
1.00 PM - 2.00 PM - Lunch
2.00 PM - 3.15 PM - Hands on Labs - Teams Bot by Jayanthi & ShanthaKumar, C#-Corner MVP
3.15 PM - 3.30 PM - Break
3.30 PM - 4.45 PM - How to Elevate SPFX solution using Custom Web API with SharePoint Online by Manoj Mittal, Technical Architect at Mindtree Ltd
*Lunch will be provided

Registration Link 
https://www.eventbrite.com/e/global-office-365-developer-bootcamp-tickets-48086187080?aff=ebdssbdestsearch
Referred Link - https://insidebigdata.com/2018/09/23/infographic-big-data-2018-far/

Referred Link - http://bigdataanalyticsnews.com/mongodb-mistakes-to-avoid-the-best-practices-to-follow/

mongodb

MongoDB is supposed to be a greatly-in-demand NoSQL database. As per experts, developers are used to making many mistakes while working on various MongoDB projects. Here are some of the mistakes to avoid.
Mistake No.1: Allowing Access from the Internet
If you allow access to your MongoDB database from the Internet, it would be a grave mistake. The default configuration of MongoDB used to leave the database fully exposed to the Internet. It implies that anyone could easily connect to your MongoDB database simply by using the server’s URL. A database must be accessible through your app only. It must actually be kept hidden in an exclusively private network which would be local and providing access to only your app’s server.
Even though MongoDB developers claim that this sort of vulnerability no longer exists and has actually been fixed in the latest versions, you must ensure that the configuration is changed after upgrading the database from the earlier version. You must focus on securing your MongoDB database. Maintaining a white-list of only those IP addresses which are having access to your MongoDB database is supposed to be a clever idea.
Mistake No.2: Having Just a Single MongoDB User
Another probable security risk would be having just one MongoDB database user instead of multiple users doing the entire job. This generally would take place when inexperienced developers or developers with lack of any interest in databases or developers without sound knowledge of the databases are there to take care of database management.
It is always a bad idea to have just one user for managing the database and then utilize the same user for accessing the database. You must understand that NoSQL would not automatically imply “secure” by default. Developers must be concerned about security breaches and overall security of the database while creating the database. Do not wait until the last moment for properly managing security issues and mitigating all possibilities of security breaches after shipping the product. You may seek assistance from professional DBA services such as RemoteDBA.com for perfect database management solutions.
Mistake No.3: Assuming Schema-Less Implies No Schema
MongoDB does not necessarily require a schema. You need to focus on your data structure. Do not be impatient and do not be in a hurry, instead think how you would be organizing your data and structure all important documents. Schemaless does not imply you have absolutely no Schema. RDBMS generally boast a pre-defined schema that is tables with columns and each comes with a data type and names. If you wish to insert an additional column, you need to include an extra column to the whole table.
But MongoDB actually does away with all this. We discover the absence of any enforced schema per document or collection. This would facilitate rapid developments and modifications could become quite easy. But do not be under the wrong impression that you could completely ignore schema design. If you have a perfectly designed schema, you could obtain the best performance and outcomes from MongoDB.
Mistake No.4: Premature Sharding
Sharding is supposed to be an optimization. Hence, you must avoid doing it way too soon as it could be a bad idea. Often just one single replica set could be adequate for operating a smooth and fast MongoDB that caters to all your specific requirements. Bad indexing and bad schema are supposed to be the real performance bottlenecks that users would be thinking of solving their issues with sharding. This process could be considered particularly when an obvious resource such as concurrency or RAM becomes a performance bottleneck on some particular machine.
Mistake No.4: Using Replicas as Backup
Remember replicas are not supposed to be backups. You would be requiring the right backup system for your database. You must not regard replicas as the actual backup mechanism. Think about what would be happening when you end up deploying the incorrect code which totally ruins the database. In such a case, replicas would be simply following the master and having the same kind of damage. You could be using a backdrop and even restoring your MongoDB in a number of effective ways, such as Mongodump, or filesystem snapshots or even MMS (Third-party service). It is crucial to have perfect fire drills. You must have the confidence that the backups made by you would be used actually in a real-life situation.
MongoDB Best Practices
If you fail to follow MongoDB best practices you could end up losing sensitive data, disrupting operations, and even dragging organizations out of business. All the MongoDB best practices discussed below are from experienced MongoDB professionals involved in creating security systems meant for databases and working closely with MongoDB users.
Enabling Access Control plus Enforcing Authentication
You should be enabling access control and specifying the authentication mechanism. You could consider using any of the existing external frameworks or the default MongoDB mechanism for authentication. Authentication necessitates that all servers and clients must provide valid credentials and only then they could be connecting to the system.
Encrypting Communication
You must necessarily configure MongoDB for using TLS/SSL meant for all the outgoing and incoming connections.
Restricting Network Exposure
Make sure that MongoDB operates in a trustworthy network environment. Consider restricting or limiting the interfaces where MongoDB instances actually are listening for incoming connections. You must only let trusted clients go ahead with accessing the ports and network interfaces where MongoDB instance could be available.
Auditing System Activity
You must be tracking access and modifications to the database configurations, as well as, data. MongoDB Enterprise actually includes an efficient system auditing facility which could be recording system events like connection events, user operations, etc. All these audit records would be permitting forensic analysis and allowing administrators to go about verifying proper controls.
Considering Security Standards Compliance
You could take note of the Security Reference Architecture of MongoDB for learning more about ways to utilize the core security capabilities for building compliant application infrastructure.
Conclusion
Many people do not like MongoDB. Actually, this is simply because they are misguided. The fact remains that many of you lack the basic understanding. If you avoid the common MongoDB mistakes and follow the MongoDB best practices discussed above, everyone would be benefitting from the simplicity and power of MongoDB. Moreover, never disregard security best practices. The most certain way of creating an insecure system would be to go on ignoring the topic altogether. Before deployment of any MongoDB instance having certain sensitive data, you must examine thoroughly the MongoDB security.
Referred Link - https://www.mountaingoatsoftware.com/blog/what-happens-when-during-a-sprint

 What Happens & When During a Sprint

Successful Scrum implementations involve a handful of important ceremonies. This includes sprint planning, the sprint review, the daily scrum, the sprint retrospective and more.
There’s often a lot of confusion about who participates, when these ceremonies are conducted, how long each can take, the purpose of the ceremony, and more.
To reduce the confusion, we’ve created infographics that answer each of these questions for sprints of 1-, 2-, 3- and 4-weeks.
Read to the bottom of this post to download a PDF with all four infographics.
A 2 week sprint

The Sprint Planning Ceremony

Sprint planning marks the official start of the sprint. Once this ceremony starts, so has the sprint.
The Scrum Master, product owner, and development team all participate. Others may attend on rare occasions when the product owner and team both agree it’s appropriate. For example, if the coming sprint will include developing functionality best explained by a subject matter expert (who is not the product owner), it can be useful to have that person attend. Usually, however, that type of discussion is best conducted outside the actual planning meeting.
The length of the sprint planning ceremony is proportional to the length of the sprint. A four-week sprint should be planned in no more than 8 hours. A one-week sprint should be planned in no more than two hours.
These are time boxes (maximums). I recommend teams target completing sprint planning in about half the allowable time box.
As input into the sprint planning ceremony, the Scrum Master will bring data on the team’s average velocity and most recent velocity. The product owner will bring the product backlog, or at least the highest priority items on the product backlog. On many teams, the product owner will also supply a draft sprint goal, which may be collaboratively revised through the planning process.
The outputs of sprint planning include a team that is smarter about and better prepared for the upcoming work. Additional outputs include a sprint backlog and an agreed upon sprint goal.

Daily Scrum

The daily scrum, also known as the daily standup, is a short, daily ceremony during which team members synchronize effort. Daily scrums enable team members to ensure the right things are being worked on by the right people at the right time.
Each day, each participant addresses three topics:
  1. What did I do yesterday to help achieve the sprint goal?
  2. What will I do today to achieve the sprint goal?
  3. What, if anything is impeding or blocking progress toward the sprint goal?
Questions can be phrased in any number of ways. For example, many teams find it beneficial for participants to describe what was accomplished rather than what they did.
Participants include the Scrum Master, development team, and, in my opinion, the product owner.
There is some debate within the Scrum community about whether the product owner should participate. Excusing the product owner from the daily scrum creates a separation within the overall team. Us-and-them feelings exist already in too many organizations. I don’t know why a Scrum team or its product owner would want to do anything to further enhance that negative attitude.
Each daily scrum is limited to 15 minutes. The intent is for it to be a brief update and synchronization effort. Unlike sprint planning, I don’t recommend trying to complete a daily scrum in half the recommended timebox. For most teams, 5-7 minutes is simply not enough time to raise any real issues or understand the work being accomplished. When teams shorten the daily scrums too much, the ceremony devolves into a series of rote updates, such as “Yesterday I did such-and-such. Today I’ll do this-and-that. Nothing is in my way.”
There are no formal inputs to the daily scrum. The only output is increased coordination of work by the development team.

Sprint Review Ceremony

The sprint review happens on the last day of the sprint. It should be attended by the product owner, Scrum Master, the development team and any appropriate stakeholders. The stakeholder participants may vary from sprint to sprint based on what has been delivered.
The sprint review is time boxed to a maximum of four hours for a four-week sprint. It is proportionately shorter for shorter sprints, down to one hour for a one-week sprint.
As input to the sprint review, the team should show all of the product backlog items that meet the team’s definition of done. This means that the team does not show work that is still in process. Sometimes, however, it may be worth making an exception to this rule.
The demo of finished functionality is the central activity of a typical sprint review. But most teams will also take time to discuss progress and problems. You can read about my recommended agenda for the sprint review.
The goal of the review is to solicit feedback on what was built during the sprint. The product owner considers all feedback and can make changes to the product backlog as appropriate. The output of a sprint review is therefore a revised product backlog.

Sprint Retrospective Ceremony

The sprint retrospective ceremony is a time for team members to consider how to improve their way of working. This means they may change aspects of how they do Scrum, such as the length of their sprints. But a retrospective can also cover general aspects of working together, such as whether to ban morning meetings or which topics are appropriate to discuss on Slack and which require a face-to-face conversation.
The sprint retrospective should be attended by the whole team--that is, the development team, Scrum Master, and the product owner. To do otherwise is create a schism within the team. A good agile team should avoid any behavior that leads to an us/them mindset.
There are no formal inputs to a sprint retrospective other than a willingness to improve. The output is a list of changes the team will make to how it works.
The sprint retrospective is formally timeboxed to 3 hours. A retrospective may occasionally take that long but most teams will conduct most retrospectives within an hour.

Product Backlog Refinement

Product backlog refinement refers to ensuring the items at the top of the product backlog are ready for the next sprint. This can include adding detail to existing items, estimating, deleting items, adjusting priorities, splitting product backlog items so as to better fit within a sprint, and creating new items.
While product backlog refinement itself is necessary, it is not mandatory that a team do refinement as a formal ceremony or that it be done every sprint. Most teams will, however, conduct regular product backlog refinement meetings, usually once per sprint or once per week.
Usual guidance is to spend no more than 10% of a team’s total available time on product backlog refinement both in meetings and in discussions that may result from those meetings.
Most teams will have the entire development team participate along with the product owner and Scrum Master. Unless a team will be estimating product backlog items during its refinement meetings, I find that perhaps half to two-thirds of the development is sufficient and reduces the overall meeting time burden on a team.
The only inputs to this ceremony are the items at the top of the product backlog. Outputs are product backlog items that are often split to be smaller and better fit within a sprint as well as greater understanding of some product backlog items.

Backlog Estimating

As noted above, many teams will estimate during product backlog refinement meetings. That is the ideal approach, and is possible if the entire development team participates in backlog refinement.
If only a subset of the development participates in backlog refinement, team members will meet once per sprint to estimate any new work for which the product owner may need an estimate.
For most teams, these estimating ceremonies should be very short. Most teams should not generate or receive a flood of new product backlog items each sprint. Work to be estimated should either be important, new product backlog items or existing items that have been split to better fit in the coming sprint.
I like to do product backlog estimating immediately following a daily scrum, a couple of days before the end of the sprint. That is late enough that most new items will have been identified but in time for the product owner to adjust priorities based on the new information conveyed by the estimates.
I do not recommend estimating during sprint planning. That is too late for the product owner to adjust priorities based on the estimates. It also leads to team members spending longer than they should on estimating. So, don’t estimate product backlog items during sprint planning.

Prioritization

Before a new sprint begins, the product owner ensures the top of the product backlog has been prioritized. According the Oxford American Dictionary, prioritize means “to put tasks, problems, etc. in order of importance, so that you can deal with the most important first.”
This means it is not sufficient for a prioritization to merely say, “They’re all required.” Or, as one product owner told me, “They’re called requirements for a reason--they’re required.”
In most cases, there will not be an official prioritization ceremony. Rather, this is something the product owner does alone following conversations with stakeholders to understand their needs and desires.
Prioritization should happen as late as possible in the sprint, while making sure it’s done before the next sprint. This will often mean doing it on the last day or two of the sprint.
Usually prioritization is not time consuming. This is because the product owner is typically fine-tuning priorities based on progress and learning from the current sprint rather than performing an outright re-prioritization of an entire product backlog.

When Do You Conduct These Ceremonies?

When does your team conduct these ceremonies? Are there other ceremonies you’d recommend other teams do? Are your participants the same as I’ve described? Please share your thoughts in the comments below.

Referred Link - https://www.linkedin.com/pulse/importance-having-bucket-list-sudha-khandelwal
Image result for Motivation
Do bungee jumping, see the northern lights, donate blood, give a Ted talk - some of the examples of the things that we usually want to do or dream of doing them in our lifetime. Most of us already have a mental list of things we wish to conquer or achieve.
Pretend you have what you want – well these may be fantasies right now, but if you are already thinking about them or, have written it all somewhere, chances are that you’ll get them as well.
Creating a wish list will help manifest them.
Origin
The dictionary meaning - bucket list: "a number of experiences or achievements that a person hopes to have or accomplish during their lifetime. Early 21st century: from the phrase kick the bucket ‘die’, popularized by the 2007 film The Bucket List." Though the term was in use before this movie as well but mostly got it’s momentum when the movie featuring Jack Nicholson and Morgan Freeman released. The two terminally ill men escaped from a cancer ward with a wish list of ‘to-dos’ in hand before they die.
Another example from a Bollywood movie - ‘Zindagi Na Milegi Dobara in which, three friends go for a vacation and do things of their choice. They not only fulfill their own wishes but also encourage their friends to overcome their fears too.
What goes into a bucket list
Everyone has a different list of his or her own aspirations. For example, mine includes sponsoring a child, scuba diving, visiting the Sphinx and many more. You might have something else on yours. Recently a Bollywood actor, Sushant Singh Rajput has published his bucket list publicly on his Social media. Some of the top items from his list were –
  • Get a flying license
  • Play football with Ronaldo
  • Click a selfie with Robert Downey Jr in Iron Man outfit
Interestingly some media people are now tracking when and how quickly he is ticking the items off his list.
Importance of bucket list
Creating a bucket list not only gives you a sense of clarity of your desires, but also gives you a sense of achievement when you accomplish each item. Some of the benefits -
  • It gets you excited, motivated – pushes you to go accomplish your goals
  • It helps you focus on things, which are important to you – It surfaces the things which you truly desire, instead of the things which you are ‘supposed to do’
  • Pushes the boundaries of your comfort zone – we miss out on so many things because of being in our comfort zone, get out of it and you will see a new world of infinite possibilities
  • Makes you more interesting – You have clues to start a conversation. The confidence shows in your voice when you have experiences of fulfillment to share
  • Might make you fitter and livelier - if you have some adventure activities on your list like marathons, skydives, etc.
  • It helps you dream big and achieve big – There are absolutely no boundaries on what you can think of doing, hence it helps you open up to newer possibilities
It is an ongoing process
Bucket lists are continuous in nature. New things keep getting added when you keep ticking off the activities. Many people create it once and forget all about it. Well creation is just the first step forward, but to see your dreams turn into reality – you have to keep visiting it regularly. Keep thinking of the ways to do it.
Read More here..

Below are the major new features that were announced and that will be included  in SharePoint 2019:

Modern Team Sites
Modern Communication Sites
Modern Lists
Modern Libraries
Modern Pages
Modern SharePoint Development Platform
Support to the latest One Drive Sync Client
Improved Hybrid Support
Improved support for PowerApps and Flow
Improvements on Large File Support, Character Restrictions and File/Folder Names
The following features are not going to be available, possibly in future Feature Packs:

Hub Sites
Site Designs and Site Scripts
Site collection app catalog
Power BI web part
Most of the modern web parts available in SharePoint Online
As expected, some of major features in Office 365 will not be available and will remain as cloud only offerings:

Office 365 Groups
Planner
Microsoft Teams
Microsoft Forms
Delve (possible to integrate with SharePoint 2019 in a hybrid scenario)
PowerBI (possible to integrate with SharePoint 2019 in a hybrid scenario)

Read the continued article on the below link:
https://blogit.create.pt/miguelisidoro/2018/08/04/sharepoint-server-gets-modern-sharepoint-2019-is-here/

and here

https://blogs.technet.microsoft.com/christianheim/2018/07/24/sharepoint-2019-public-preview-generally-available/


SharePoint Framework

Started with the SharePoint Framework
https://www.youtube.com/watch?v=N1Z5XDLZ0J8

SharePoint Yeoman Generator
https://www.youtube.com/watch?v=ap8uf6dNAFs

Using Office UI Fabric React Components
https://www.youtube.com/watch?v=RnXD10a-2ww

Image result for self improvement

Improve yourself 1 percent everyday, at the end of the year you will be 3.5 times better.

Here are 5 simple ways I follow to change everyday: 1. Keep a diary where you can regularly write/reflect on yourself everyday, this clears confusion, helps you understand yourself better. It has changed my life. 2. Apply what you have learnt, even a small thing can produce amazing results. I studied psychology started applying that learning to myself, it changed me. 3. Observing people around you, learning from them. I try to pick one good habit from each person I meet, try to implement it. It could a small thing like the way the person smiles. 4. Getting into uncomfortable situations gives the most learning, failing is even better. The more uncomfortable you feel the more you are learning. 5. Doing new things everyday, doing the same things differently, this helps us learn, grow & change.
Newer Posts
Older Posts

Search this Site

Translate Articles

Total Posts

Total Pageviews


Contributors

My photo
Jay Srinivasan
Professional: I'm a Software Techie, Specialized in Microsoft technologies. Worked in CMM Level 5 organizations like EPAM, KPMG, Bosch, Honeywell, ValueLabs, Capgemini and HCL. I have done freelancing. My interests are Software Development, Graphics design and Photography.
Certifications: I hold PMP, SAFe 6, CSPO, CSM, Six Sigma Green Belt, Microsoft and CCNA Certifications.
Academic: All my schooling life was spent in Coimbatore and I have good friends for life. I completed my post graduate in computers(MCA). Plus a lot of self learning, inspirations and perspiration are the ingredients of the person what i am now.
Personal Life: I am a simple person and proud son of Coimbatore. I studied and grew up there. I lost my father at young age. My mom and wife are proud home-makers and greatest cook on earth. My kiddo in her junior school.
Finally: I am a film buff and like to travel a lot. I visited 3 countries - United States of America, Norway and United Kingdom. I believe in honesty after learning a lot of lessons the hard way around. I love to read books & articles, Definitely not journals. :)
View my complete profile

Certifications

Certifications

My Favorite Links

  • Saran & Akshu Links
  • Saran Kitchen Hut
  • World of Akshu
  • Ashok Raja Blog

Subscribe To

Posts
Atom
Posts
All Comments
Atom
All Comments

Contact Form

Name

Email *

Message *

Connect with Me

Blog Archive

  • ►  2025 (48)
    • ►  June (7)
    • ►  May (26)
    • ►  April (1)
    • ►  March (3)
    • ►  February (1)
    • ►  January (10)
  • ►  2024 (134)
    • ►  December (3)
    • ►  November (8)
    • ►  October (11)
    • ►  September (2)
    • ►  August (1)
    • ►  July (39)
    • ►  June (8)
    • ►  May (4)
    • ►  April (9)
    • ►  March (6)
    • ►  February (33)
    • ►  January (10)
  • ►  2023 (16)
    • ►  December (12)
    • ►  August (2)
    • ►  March (1)
    • ►  January (1)
  • ►  2022 (14)
    • ►  December (1)
    • ►  August (6)
    • ►  July (3)
    • ►  June (2)
    • ►  February (1)
    • ►  January (1)
  • ►  2021 (16)
    • ►  December (1)
    • ►  November (2)
    • ►  October (2)
    • ►  August (1)
    • ►  July (2)
    • ►  June (2)
    • ►  May (2)
    • ►  March (2)
    • ►  February (1)
    • ►  January (1)
  • ►  2020 (36)
    • ►  December (1)
    • ►  November (15)
    • ►  October (2)
    • ►  September (1)
    • ►  July (1)
    • ►  June (2)
    • ►  May (4)
    • ►  March (2)
    • ►  February (6)
    • ►  January (2)
  • ►  2019 (14)
    • ►  December (3)
    • ►  November (1)
    • ►  September (2)
    • ►  August (1)
    • ►  June (1)
    • ►  May (3)
    • ►  March (2)
    • ►  January (1)
  • ▼  2018 (61)
    • ▼  November (3)
      • Six Practices of Successful Innovators by philmcki...
      • Creating an Angular 7 App with ASP.NET Core: A Ste...
      • Global Office 365 Developer Bootcamp @ Bangalore -...
    • ►  October (4)
      • Big Data in 2018
      • MongoDB Mistakes to Avoid & the Best Practices to ...
      • What Happens & When During a Sprint by Mike Cohn
      • MS SharePoint - Comparison of Online vs On-Premises
    • ►  September (4)
      • The Importance of having a Bucket List by Sudha Kh...
      • SharePoint 2019 Introduction and SharePoint Framew...
      • How can you become 3.5 times better than yourself ...
    • ►  August (5)
    • ►  July (4)
    • ►  June (4)
    • ►  May (7)
    • ►  April (7)
    • ►  March (5)
    • ►  February (1)
    • ►  January (17)
  • ►  2017 (55)
    • ►  December (1)
    • ►  November (7)
    • ►  October (7)
    • ►  September (8)
    • ►  July (4)
    • ►  June (7)
    • ►  May (4)
    • ►  April (4)
    • ►  March (1)
    • ►  February (2)
    • ►  January (10)
  • ►  2016 (45)
    • ►  December (1)
    • ►  November (5)
    • ►  October (2)
    • ►  September (7)
    • ►  August (3)
    • ►  July (3)
    • ►  June (1)
    • ►  May (3)
    • ►  April (5)
    • ►  March (3)
    • ►  February (3)
    • ►  January (9)
  • ►  2015 (88)
    • ►  December (5)
    • ►  November (2)
    • ►  October (6)
    • ►  September (6)
    • ►  August (3)
    • ►  July (6)
    • ►  June (7)
    • ►  May (12)
    • ►  April (6)
    • ►  March (11)
    • ►  February (10)
    • ►  January (14)
  • ►  2014 (159)
    • ►  December (16)
    • ►  November (13)
    • ►  October (42)
    • ►  September (12)
    • ►  August (19)
    • ►  July (3)
    • ►  June (17)
    • ►  May (10)
    • ►  April (12)
    • ►  March (7)
    • ►  February (4)
    • ►  January (4)
  • ►  2013 (192)
    • ►  December (7)
    • ►  November (2)
    • ►  October (3)
    • ►  September (10)
    • ►  August (25)
    • ►  July (17)
    • ►  June (22)
    • ►  May (22)
    • ►  April (24)
    • ►  March (17)
    • ►  February (22)
    • ►  January (21)
  • ►  2012 (204)
    • ►  December (21)
    • ►  November (35)
    • ►  October (47)
    • ►  September (27)
    • ►  August (6)
    • ►  July (21)
    • ►  June (16)
    • ►  May (7)
    • ►  April (9)
    • ►  March (4)
    • ►  February (3)
    • ►  January (8)
  • ►  2011 (70)
    • ►  December (8)
    • ►  November (5)
    • ►  October (3)
    • ►  September (2)
    • ►  August (7)
    • ►  July (3)
    • ►  June (30)
    • ►  May (3)
    • ►  April (3)
    • ►  March (1)
    • ►  February (3)
    • ►  January (2)
  • ►  2010 (30)
    • ►  December (1)
    • ►  September (4)
    • ►  August (1)
    • ►  July (1)
    • ►  June (1)
    • ►  May (4)
    • ►  April (6)
    • ►  March (5)
    • ►  February (2)
    • ►  January (5)
  • ►  2009 (40)
    • ►  December (4)
    • ►  November (6)
    • ►  October (4)
    • ►  September (5)
    • ►  August (4)
    • ►  July (3)
    • ►  June (4)
    • ►  May (8)
    • ►  March (1)
    • ►  February (1)
  • ►  2008 (6)
    • ►  December (1)
    • ►  September (1)
    • ►  May (1)
    • ►  April (2)
    • ►  February (1)
  • ►  2007 (7)
    • ►  December (1)
    • ►  November (2)
    • ►  October (1)
    • ►  July (1)
    • ►  May (2)

Recent Posts

Followers

Report Abuse

FOLLOW ME @INSTAGRAM

Popular Posts

  • Stay Wow - Health Tips from Sapna Vyas Patel
    Referred URL https://www.facebook.com/sapnavyaspatel WATCH WEIGHT LOSS VIDEO: http://www.youtube.com/ watch?v=S_dlkjwVItA ...
  • Calorie Count chart For food and drinks
    Referred URL http://deepthidigvijay.blogspot.co.uk/p/health-diet-calorie-charts.html http://www.nidokidos.org/threads/37834-Food-Calorie-...
  • SharePoint 2010 Interview Questions and Answers
    Referred URL http://www.enjoysharepoint.com/Articles/Details/sharepoint-2010-interview-questions-and-answers-148.aspx 1.What is SharePoint...
  • 150 Best Windows Applications Of Year 2010
    Referred URL : http://www.addictivetips.com/windows-tips/150-best-windows-applications-of-year-2010-editors-pick/?utm_source=feedburner...
  • Web Developer Checklist by Mads Kristensen
    Referred Link -  http://webdevchecklist.com/ Web Developer Checklist Get the extension  Chrome  |  Firefox  |  Edge Menu Bes...
  • WCF and REST Interview Questions
    What is WPF? The Windows Presentation Foundation (WPF) is a next generation graphics platform that is part of...
  • Remove double tap to unlock feature on samsung galaxy core2
    Double tap to unlock is a feature of Talkback, so if your will disable Talkback, double tap to unlock will also be disabled. To disable doub...
  • Difference Between Content Editor and Script Editor webpart
    Referred Link -  http://jeffas.com/content-editor-vs-script-editor-webpart/ Content editor web part is a place holder for creating rich ...
  • SPFolder related operations in SharePoint
      1) Get SPListItem(s) of a particular SPFolder SPList splist; SPFolder spfolder; //Get the required folder instance SPQuery spquery = new ...

Comments

Created with by BeautyTemplates | Distributed by blogger templates