Fear of Startup Entrepreneur

I had recently updated my views on the startup co-founder (https://goo.gl/baJJ4J), through which got a connection from a people in dilemma about how to go about a startup.

Here are my views and perceptions, from the experience I had working, as only Tech guy to number of startups (Retortsoft, Softoria, Cybertech Networks).

The first and the foremost thing to start an org is t

• have an idea, now plan
• list what ever comes in mind
• ask questions to yourself.
• be self critic and self motivator
• make notes at every step
• what is the idea about
• how it can be beneficial
• are there any companies or startups have similar concept
• how different I am
• how efficient and valuable I can be
• study based on competitors
• where others failed
• where I can fail
• what is that I have today
• what is that I might need to get this idea into business
• whom to share with
• there is no definite  answer to it.
• we have to trust, in one-self
• get connected to people in similar field
• get connected to people who are also looking for co-founders
• get connected to skill-set other than own-area
• share the idea and vision
• let the person in believe in you
• see how the other person can be helpful
• what are the areas you can contribute and others can.
• but sit hiding yourself, share the idea.
• fear of somebody stealing the idea
• it happens
• and it will happen
• dont let the fear stop you
• the person you shared the idea may run-away and start his own
• how long it will sustain
• if he is dedicated and follows the above to main points he might succeed
• but you in fear will never even move
• the idea is nothing unless taken into action
• and the action and pro activeness is what will convert into business
• what is the fear in the initial stage
• there have been many companies spawned out of people who were working there
• as the first point says it will happen
• never let yourself stop
• the stolen idea might be of 10points, and mostly it stays within that limit
• you been the owner of idea will have vision, you might go beyon that 10point which was shared.
• during the course of ideation itself you might know that idea might not work
• if you come to know the idea cannot be transformed into business?
• remember its again not lost effort, if it fails, come out of it.
• you learned the process, you were involved into bringing the idea now you can explore more new ideas and be more effective and strong
• your continuous effort and learning in any idea, will help to come up with different ideas and get connected with many new entrepreneurs.
• how should i work on my idea to a startup
• you need to have all the plan ready
• making an effort of putting a presentation itself will teach you a lot
• the presentation should consist of
• the idea and benefits
• the business model and its advantages
• how we go about it
• how to get the source data and who all are consumers
• what are the litigations involved
• what is the revenue generation model
• what is the effective time to start gaining profits
• what are the areas it can fail
• how will you take the failure
• if you are alone, what type of members you need to move it further.
• take to more people and get connected to some
• you never know if you are connecting to best one it comes with experience
• if you get slightest positiveness keep the relation, even if not co-founder
• its only people network which will help you
• a tech co-founder might even not know the required technology it requires, but that doesn't mean you cannot work with him.
• technology is changing every day, so once you have tech-cofounder get the proto-type ready
• the pro-types should be actually working model.
• we can explore on making it stable and saleable product.
• if it doesnt come out as expected and cannot move the ahead with planned vision
• change the idea, and re-work the whole process again
• by this time you have network, co-founder and environment
• so it wont be big trouble in launching another product then move ahead
• once the product has enough of good implementation, innovative ideas and standing out against the competitor
• rollout for getting funds
• remember again we need a proper presentation
• now instead of business model, it should be actual product
• and it should be capable of generating revenue.
• fear not for turning idea into startup
• fear not idea getting stolen
• fear not the failed idea, gone by, come back again and re-work

Here are few links which would keep your fear away, if you still fear get a job and wait, you need to have entrepreneur skills so as to not be layed-off.. 

• http://small-bizsense.com/10-famous-entrepreneurs-who-failed-in-business-before-becoming-successful/
• http://www.wikihow.com/Start-a-Small-Business
• http://www.lifehack.org/articles/work/start-up-mistakes-that-youre-probably-making.html
• http://yourstory.com/2015/08/startup-idea/
• https://www.entrepreneur.com/article/248802

What is DevOps

Prior to DevOps

---

Prior to DevOps application development, teams were in charge of gathering business requirements for a software program and writing code. Then a separate QA team tests the program in an isolated development environment, if requirements were met, and releases the code for operations to deploy. The deployment teams are further fragmented into siloed groups like networking and database. Each time a software program is “thrown over the wall” to an independent team it adds bottlenecks.


The problem with this paradigm is that when the teams work separately:

• Dev is often unaware of QA and Ops roadblocks that prevent the program from working as anticipated.
• QA and Ops are typically working across many features and have little context of the business purpose and value of the software.
• Each group has opposing goals that can lead to inefficiency and finger pointing when something goes wrong.
• DevOps addresses these challenges by establishing collaborative cross-functional teams that share responsibility for maintaining the system that runs the software and preparing the software to run on that system with increased quality feedback and automation issues.

DevOps 

---

DevOps is not based on stringent methodologies and processes: it is based on professional principles that help business units collaborate inside the enterprise and break down the traditional silos. The guiding principles of DevOps include culture, measurement, automation and sharing.

list of core DevOps attributes:

* Ability to use a wide variety of open source technologies and tools

* Ability to code and script

* Experience with systems and IT operations

* Comfort with with frequent, incremental code testing and deployment

* Strong grasp of automation tools

* Data management skills

* A strong focus on business outcomes

* Comfort with collaboration, open communication and reaching across functional borders

The Agile community, acronym CAMS - Culture, Automation, Measurements and Sharing.

DevOps  Skill High level Requirement

---

•   Source Code Repository Management

Popular source code repository tools are Git, Subversion, etc

•   Build Server

The build server is an automation tool that compiles the code in the source code repository into executable code base. 

Popular tools are Jenkins, SonarQube, etc

•   Configuration Management

Configuration management defines the configuration of a server or an environment. 

Popular configuration management tools are Puppet, Ansible, Chef.

•   Infrastructure

Baremetal, VMware vCloud and/or Amazon Web Services and Microsoft Azure virtual infrastructures. Virtual infrastructures are provided by cloud vendors that sell infrastructure or platform as a service (PaaS), have APIs to allow you to programmatically create new machines with configuration management tools.

OS can be Linux, Windows, Unix, Mac OS.

•   Test Automation

DevOps testing focuses on automated testing within your build pipeline to ensure that by the time that you have a deployable build, you are confident it is ready to be deployed. You can’t get to the point of continuous delivery where you’re fairly confident without any human intervention that your code is deployable without an extensive automated testing strategy.  

Popular tools are Selenium and Water.

•   Monitoring

monitoring solution that is highly effective because of the large community of contributors who create plugins for the tool, 

Popular tools Nagios, Icinga, 

•   Containers

quick and painless continuous delivery of your software to production, applications can reuse the libraries and share the data between containers.Popular tools docker, mesos, Kubernetes 

•   Pipeline Orchestration

A pipeline is like a manufacturing assembly line that happens from the time a developer says, “I think I’m done,” all the way to the time that the code gets deployed in the production or a late-stage pre-production environment.

This is the complete process of developing, testing, staging, deploying, monitoring

DevOps  History

---

The Incredible True Story of How DevOps Got Its Name
fredric@newrelic.com' By Fredric Paul • May. 16th, 2014 • Tech Topics
DevOps

Source: https://blog.newrelic.com/2014/05/16/devops-name/
Youtube: https://www.youtube.com/watch?v=o7-IuYS0iSE

Here’s the inside story, as recounted by Damon Edwards in his The Short History of DevOps YouTube video:

Basically, the timeline goes something like this:

2007: While consulting on a data center migration for the Belgium government, system administrator Patrick Debois becomes frustrated by conflicts between developers and system admins. He ponders solutions.

August 2008: At the Agile Conference in Toronto, software developer Andrew Shafer posts notice of a “birds of a feather” session entitled “Agile Infrastructure.” Exactly one person attends: You guessed it, Patrick Debois. And he has the room to himself: Thinking there was no interest in his topic, Andrew skips his own session! Later, Debois tracks down Shafer for a wide-ranging hallway conversation. Based on their talk, they form the Agile Systems Administration Group.

June 2009: At the O’Reilly Velocity 09 conference, John Allspaw and Paul Hammond give their now-famous talk entitled, “10+ Deploys a Day: Dev and Ops Cooperation at Flickr.” Watching remotely, Debois laments on Twitter that he is unable to attend in person. Paul Nasrat tweets back, “Why not organize your own Velocity event in Belgium?”


10+ Deploys Per Day: Dev and Ops Cooperation at Flickr from John Allspaw
October 2009: Debois decides to do exactly that—but first, he needs a name. He takes the first three letters of development and operations, adds the word “days,” and calls it DevOpsDays. The conference doors open on October 30 to an impressive collection of developers, system administrators, toolsmiths, and others. When the conference ends, the ongoing discussions move to Twitter. To create a memorable hashtag, Debois shortens the name to #DevOps. And the movement has been known as DevOps ever since.
(Disagreement about the spelling remains, however. The predominant usage is “DevOps,” but a vocal minority—including founder Debois—advocate “Devops.” And true to DevOps’ spirit of lively debate, a few argue for eliminating capital letters altogether, as in “devops.”)

In an InfoQ video interview from April 2012, Debois admitted that naming the movement was not as intentional as it might seem: “I picked ‘DevOpsDays’ as Dev and Ops working together because ‘Agile System Administration’ was too long,” he said. “There never was a grand plan for DevOps as a word.”

Calendar History

The Gregorian calendar today serves as an international standard for civil use. In addition, it regulates the ceremonial cycle of the Roman Catholic and Protestant churches. In fact, its original purpose was ecclesiastical. Although a variety of other calendars are in use today, they are restricted to particular religions or cultures.

The Gregorian calendar is the calendar currently used in the Western world. It is a modification of the Julian calendar, was first proposed by Neapolitan doctor Aloysius Lilius, and adopted by Pope Gregory XIII on February 24, 1582 (the document was dated 1581 on account of the pope starting the year in March).
The mean year in the Julian Calendar was a little too long so causing the Vernal equinox to drift earlier in the calendar year. This was why the Gregorian calendar was invented.
The Gregorian calendar improves the approximation by skipping 3 Julian leap days in every 400 years, giving an average year of 365.2425 mean solar days long, which has an error of about 1 day per 3000 years with respect to the mean tropical year but less than half this error with respect to the vernal equinox tropical year of 365.2424 days. On any timescale over 3000 years it is expected that changes in the Earth's orbit and unpredictable rotation make it improbable that long term accuracy can be gained by rule changes requiring any further regular skipping of Julian leap days.

Years are counted from the initial epoch defined by Dionysius Exiguus, and are divided into two classes: common years and leap years. A common year is 365 days in length; a leap year is 366 days, with an intercalary day, designated February 29, preceding March 1. Leap years are determined according to the following rule:
Every year that is exactly divisible by 4 is a leap year, except for years that are exactly divisible by 100;
these centurial years are leap years only if they are exactly divisible by 400.
As a result the year 2000 is a leap year, whereas 1900 and 2100 are not leap years. These rules can be applied to times prior to the Gregorian reform to create a proleptic Gregorian calendar. In this case, year 0 (1 B.C.) is considered to be exactly divisible by 4, 100, and 400; hence it is a leap year.
The Gregorian calendar is thus based on a cycle of 400 years, which comprises 146097 days. Since 146097 is evenly divisible by 7, the Gregorian civil calendar exactly repeats after 400 years. Dividing 146097 by 400 yields an average length of 365.2425 days per calendar year, which is a close approximation to the length of the tropical year. Comparison with Equation 1.1-1 reveals that the Gregorian calendar accumulates an error of one day in about 2500 years. Although various adjustments to the leap-year system have been proposed, none has been instituted.
Within each year, dates are specified according to the count of days from the beginning of the month. The order of months and number of days per month were adopted from the Julian calendar.

Months of the Gregorian Calendar

1. January	31	7. July	31
2. February	28*	8. August	31
3. March	31	9. September	30
4. April	30	10. October	31
5. May	31	11. November	30
6. June	30	12. December	31

* In a leap year, February has 29 days.
The motivation of the Catholic Church in adjusting the calendar was to have Easter celebrated at the time that had been agreed at the First Council of Nicaea in 325, i.e., at the Sunday after the 14th day of the Moon that falls on or after the vernal equinox - which fell approximately on March 21 at that time. By the time of this council, the drift of the equinox since the introduction of the Julian calendar had already been noticed. Instead of modifying the calendar, the equinox was standardised at March 21 instead of the original March 24 or March 25. However by the 16th century, the equinox had drifted noticeably further.
Worse, the reckoned Moon that was used to compute Easter was fixed to the Julian year by a 19-year cycle. However, that is an approximation that built up an error of 1 day every 310 years. So by the 16th century the lunar calendar was way out of sync with the real Moon too.
The fix for the equinox was to define that years divisible by 100 will be leap years only if they are divisible by 400 as well. So, in the last millennium, 1600 and 2000 were leap years, but 1700, 1800 and 1900 were not. That gives a correction of 3 days. (Additionally, 10 dates were deleted at the time of introduction; see below.) This 3rd millennium will have 8 days corrected.
The Gregorian calendar also fixed the first day of the year as January 1, which was already the first day used in Italy, Germany, and other places, but not universally (England, for example, began the year on March 25). On January 1, 1622 January 1 was declared as the first day of the year.
When the new calendar was put in use, to correct the error already accumulated in the thirteen centuries since the council of Nicaea, a deletion of ten dates was made passing from October 4, 1582 directly to October 15, 1582. This created some consternation, and the church was accused of stealing days of people's lives.
The 19-year cycle used for the lunar calendar was also to be corrected by 1 day every 300 or 400 years (8 times in 2500 years) along with corrections for the years (1700, 1800, 1900, 2100 etc.) that are no longer leap years. In fact, a new method for computing the date of Easter was introduced.

sources:
http://astro.nmsu.edu/~lhuber/leaphist.html,
http://www.knowledgerush.com/kr/encyclopedia/Gregorian_Calendar/

On Twitter

Want to get blogs on twitter; browse these first
Get yourself blogger login
- www.blogger.com

Get yourself twitter login
- www.twitter.com

Push the feed from blog to twitter
- http://twitterfeed.com/

Get twitter themes
- http://www.colourlovers.com/themeleon/twitter

Keep blogging, users follow twitter for updates ;)