DEV Community: Anu

How I did 12K commits in Github within 24 hrs

Anu — Sat, 13 Jul 2019 08:11:33 +0000

How I did 12K commits in Github within 24 hrs — Python Automation

So, I did 12K commits in Github within 24 hrs by running an automated python program.

This I would not say is a very useful tool to use, BUT IS SOMETHING MORE!!!!!

Something to play with, have some fun, go others — WOAAAHHHHHH :P

WARNING: THESE ARE NOT ACTUAL CONTRIBUTIONS — — THIS IS A HACK, HAVE FUN. :P

See my work at —

In every 2 hours, the commits will automatically be increased by 1000.

See my work. Give ⭐️ 👏

coolanant/24hrs-automated-commits

Just follow the link for more details.

Or directly use —

git-unlimited-commit

Hackathon — Organizing & finding Innovation

Anu — Thu, 04 Jul 2019 17:11:22 +0000

Hackathon — Organizing & finding Innovation

— Anant Rungta

Introduction
Objectives

2.1 Closed Innovation to Open Innovation

2.2 Approach of the company/Organization

Recipe of Successful Hackathon

3.1 Motivation and Aligned Targets.

3.2 Preparation Phase.

3.3 The Challenge.

3.4 Participation of Company.

3.5 Presence of Active and multidisciplinary people.

Conclusion
References

1. Introduction

The word hackathon is a composed of two words, “hack” and “marathon”, of which “hack” refers to programming and “marathon” to the limited timeframe of the event. Hackathon as a term was formed at the end of the 1990s when it was used to describe an event combining idea generation and programming to create new solutions for existing challenges in a limited timeframe. It is so strongly originated in the IT community, where multidisciplinary teams have collaborated intensively to create something new.

Hackathon strives to provide an answer to challenges organizations encounter in a modern world: rapid technology development, globalization, and mobility of skilled workforce just to mention a few. The core idea of these hackathons is to break the organization’s boundaries in innovation processes.

These are a special type of events based on co-creation and open innovation − the modern paradigm of innovation − that has become popular worldwide in the first decade of the new millennium.

2. Objectives

Hackathons as events have become popular, but are these arranged purely to practice open innovation? Organizations are eager to join the hackathon movement and are gaining tangible results from co-creation and open innovation.

2.1 Closed Innovation to open innovation

The closed innovation model is based on the presumption that all the key inventions and technologies should be developed strictly within the boundaries of organizations. Innovations and new technologies are to be used only for the organization’s own purposes and it would be a risk to let the innovations get out of the organization − even if these were not used for business means at all.

However, in the modern world globalization is part of everyday life, the development of technology is more rapid than ever, and highly skilled people are moving from one organization to another.

It can be argued that the baselines of closed innovation are no longer valid and the traditional model for innovation and value creation is outdated.

2.2 Approach of the company/Organization

Companies can approach hackathons from various angles. If the companies lack internal innovation, they might want to join the hackathon to get ideas that could be refined to innovations. If the companies do not have difficulties with innovation, they can approach the event from marketing or recruiting point of view.

Ideas are trivial in innovation since there are a lot more to do to get the ideas to innovations and innovations into the business.

Figure 1: Basic overview of how a hackathon works

3. Recipe for a successful hackathon

The further aim of this chapter is to provide development ideas, or a recipe for a successful hackathon, for the organizations that are either considering arranging a private hackathon or joining a public one. These ideas can also be utilized in organizations that consider their position and approach towards innovation or reflect their actions in hackathons that they have experienced.

3.1 Motivation and Aligned Targets.

According to research, one of the main success factors is to have a clear motivation and aligned targets. This step needs to be done before the decision to join any specific hackathon, and only after these are set and agreed, it is should be decided which kind of hackathon event would support the motivation and targets in the best possible way − this is as important a step as defining the targets. As it came up in the interviews, just joining the hackathon takes a lot of resources and is thus a significant investment from the organization. To get the most out of the investment, It is suggested that the organizations pay special attention to motivation and targets they have and choose the right kind of hackathon to support these. If the decision to join is made without a clear vision of the motivation and targets, the hackathon investment and experience can easily be a failure.

3.2 Preparation Phase

With the necessary time given, there are various important factors to be considered in the preparation phase that correlates with the success of the event itself. First, the challenge for the participants needs to be considered well to align with the targets set. If the motivation and targets are on open innovation, this should be of the highest importance of all the preparations: without a proper challenge for the participants, it is impossible to imagine that the challenge would lead to any plausible ideas to refine further. Without an interesting challenge, the image the company creates of itself during the event will not be good in marketing or recruiting purposes either.

3.3 The Challenge

The motivation and targets should guide the definition of the challenge. If the focus is solely on marketing and recruiting, it is important that the challenge would be both highly interesting and easy to approach. The objective of the challenge is thus to create a desirable image of the organization and to attract as many people to take part in the challenge as possible. However, if the motivation is purely on inbound open innovation the companies should link the challenge to their innovation process so that it would support the internal innovation accordingly.

3.4 Participation of Company

Many of the companies had marketing accessories that they gave away for the participants: t-shirts, hoodies etcetera. According to the interviews, this had a major role in creating a positive image of the organizations. Practical preparations include also tasks to support the actual challenge.

There is a lot of practicalities that need to be taken care of when preparing for the hackathon. The preparations do take more time than would be expected. Based on these interviews, three various areas of preparations came up that correlate with the success of the hackathon: preparing the challenge to support the targets set for the event, preparing the stand at the venue to back up the previous and preparing the various types of practicalities that need to be taken care of. These preparations are to be done with proper time and severity to support the targets set for the event.

3.5 Presence of Active and multidisciplinary people

The need for the right people in the event was guided by the potential of the hackathon, and the potential, in this case, seemed to be exactly the same as the sources for motivation: recruiting, marketing and open innovation. Personnel who could answer the questions from both the business and technology aspects and help the participants to tackle the possible obstacles they faced with the challenge.

This means the organizations had to be both easy to approach and active in approaching the participants to support them actively.

4. Conclusion

The development mission of this thesis was to introduce the ingredients of a successful hackathon from the view of open innovation and provide a holistic, practical recipe for organizations’ use. The provided recipe is to serve as a practical tool for organizational development for those organizations that are planning to arrange an internal hackathon or take part in a public hackathon in the future.

There were three separate motivations that organizations had on joining the hackathon, i.e marketing, recruiting and open innovation.

Marketing was the most popular motivation with half of the interviewed organizations having it as their main interest in joining and the other half as a secondary reason. That means that every organization had marketing somehow on the mind. Open innovation as motivation was divided into inbound and outbound open innovation.

The theories on the topic are mostly based on studies of large organizations and the theories have been generalized to apply all organizations whether it is large or small, modern or traditional. These findings were supported by analyzing the targets that organizations had set for the event since the targets correlated straight with the motivation.

It is possible for the organizations to continue the innovation process around the ideas that are born in public hackathons. According to this thesis, it requires a clear plan on how to take the next steps. This plan must be done before the actual hackathon event so it can be communicated to the participants and the process continues seamlessly. If the organizations start the planning only after the hackathon event it is too late since the gap between the idea and the refinement actions easily grows too big.

Basically, this thesis brings together a lot of information regarding both innovation and hackathons providing interesting insights. The thesis provides clear development ideas for organizations to use in practice. However, a lot of interesting and important questions of the combination of hackathons remains untouched − there is still plenty of room in the sandbox.

References

Top 5 Cool Github Projects

Anu — Wed, 03 Jul 2019 16:03:33 +0000

https://medium.com/@romedy65i/top-5-cool-github-projects-aeef002d0a6d

Npm package — get-all-emoji
Github Readme Markdown — Chrome Extension
E-commerce website — made using React, Redux, Firebase, GCP
React Course for beginners
Alexa Skills — with APL

Create your own chrome extension — and deploy to Chrome Web Store

Anu — Tue, 02 Jul 2019 22:10:11 +0000

Create your own chrome extension — and deploy to Chrome Web Store

Github Readme Markdown

Web Extensions

Intro

First of all, I’ll tell you it is very easy. There is only one important file, that is — manifest.json. Everything there is to know about this file —

{
_// Required_
 "[**manifest\_version**](https://developer.chrome.com/extensions/manifest/manifest_version)": 2,
 "[**name**](https://developer.chrome.com/extensions/manifest/name#name)": "My Extension",
 "[**version**](https://developer.chrome.com/extensions/manifest/version)": "versionString",

_// Recommended_
 "[**default\_locale**](https://developer.chrome.com/extensions/manifest/default_locale)": "en",
 "[**description**](https://developer.chrome.com/extensions/manifest/description)": "A plain text description",
 "[**icons**](https://developer.chrome.com/extensions/manifest/icons)": {...},

_// Pick one (or none)_
 "[**browser\_action**](https://developer.chrome.com/extensions/browserAction)": {...},
 "[**page\_action**](https://developer.chrome.com/extensions/pageAction)": {...},

_// Optional_
 "action": ...,
 "author": ...,
 "automation": ...,
 "[**background**](https://developer.chrome.com/extensions/background_pages)": {
_// Recommended_
 "[**persistent**](https://developer.chrome.com/extensions/event_pages)": false,
_// Optional_
 "[**service\_worker**](https://developer.chrome.com/extensions/background_pages)":
 },
 "[**chrome\_settings\_overrides**](https://developer.chrome.com/extensions/settings_override)": {...},
 "[**chrome\_ui\_overrides**](https://developer.chrome.com/extensions/ui_override)": {
 "bookmarks\_ui": {
 "remove\_bookmark\_shortcut": true,
 "remove\_button": true
 }
 },
 "[**chrome\_url\_overrides**](https://developer.chrome.com/extensions/override)": {...},
 "[**commands**](https://developer.chrome.com/extensions/commands)": {...},
 "content\_capabilities": ...,
 "[**content\_scripts**](https://developer.chrome.com/extensions/content_scripts)": [{...}],
 "[**content\_security\_policy**](https://developer.chrome.com/extensions/contentSecurityPolicy)": "policyString",
 "converted\_from\_user\_script": ...,
 "current\_locale": ...,
 "declarative\_net\_request": ...,
 "[**devtools\_page**](https://developer.chrome.com/extensions/devtools)": "devtools.html",
 "[**event\_rules**](https://developer.chrome.com/extensions/manifest/event_rules)": [{...}],
 "[**externally\_connectable**](https://developer.chrome.com/extensions/manifest/externally_connectable)": {
 "matches": ["\*://\*.example.com/\*"]
 },
 "[**file\_browser\_handlers**](https://developer.chrome.com/extensions/fileBrowserHandler)": [...],
 "[**file\_system\_provider\_capabilities**](https://developer.chrome.com/extensions/manifest/file_system_provider)": {
 "configurable": true,
 "multiple\_mounts": true,
 "source": "network"
 },
 "[**homepage\_url**](https://developer.chrome.com/extensions/manifest/homepage_url)": "http://path/to/homepage",
 "[**import**](https://developer.chrome.com/extensions/shared_modules)": [{"id": "aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa"}],
 "[**incognito**](https://developer.chrome.com/extensions/manifest/incognito)": "spanning, split, or not\_allowed",
 "input\_components": ...,
 "[**key**](https://developer.chrome.com/extensions/manifest/key)": "publicKey",
 "[**minimum\_chrome\_version**](https://developer.chrome.com/extensions/manifest/minimum_chrome_version)": "versionString",
 "[**nacl\_modules**](https://developer.chrome.com/extensions/manifest/nacl_modules)": [...],
 "oauth2": ...,
 "[**offline\_enabled**](https://developer.chrome.com/extensions/manifest/offline_enabled)": true,
 "[**omnibox**](https://developer.chrome.com/extensions/omnibox)": {
 "keyword": "aString"
 },
 "[**optional\_permissions**](https://developer.chrome.com/extensions/permissions)": ["tabs"],
 "[**options\_page**](https://developer.chrome.com/extensions/options)": "options.html",
 "[**options\_ui**](https://developer.chrome.com/extensions/optionsV2)": {
 "chrome\_style": true,
 "page": "options.html"
 },
 "[**permissions**](https://developer.chrome.com/extensions/declare_permissions)": ["tabs"],
 "platforms": ...,
 "replacement\_web\_app": ...,
 "[**requirements**](https://developer.chrome.com/extensions/manifest/requirements)": {...},
 "[**sandbox**](https://developer.chrome.com/extensions/manifest/sandbox)": [...],
 "[**short\_name**](https://developer.chrome.com/extensions/manifest/name#short_name)": "Short Name",
 "signature": ...,
 "spellcheck": ...,
 "[**storage**](https://developer.chrome.com/extensions/manifest/storage)": {
 "managed\_schema": "schema.json"
 },
 "system\_indicator": ...,
 "[**tts\_engine**](https://developer.chrome.com/extensions/ttsEngine)": {...},
 "[**update\_url**](https://developer.chrome.com/extensions/autoupdate)": "http://path/to/updateInfo.xml",
 "[**version\_name**](https://developer.chrome.com/extensions/manifest/version)": "aString",
 "[**web\_accessible\_resources**](https://developer.chrome.com/extensions/manifest/web_accessible_resources)": [...]
}

At least we know, there is nothing more than this. Now while making an extension, we don’t need to use every code written above.

Now we’re gonna make the Github Readme Markdown Chrome Extension whose link I gave in the beginning.

( Go have a look at it. )

Step 1: Creating a manifest.json file

{

“manifest\_version”: 2,

“author”: “https://github.com/Anant016",

“name”: “Github Readme Markdown”,

“icons”: { “48”: “./demo.png”, “128”: “./demo.png” },

“version”: “1.0”,

“description”: “Show options, how to edit while Readme.md is being edited in browser”,

“content\_scripts”: [

{

“matches”: [

“https://github.com/\*/new\*?readme\*"],

“js”: [“showoption.js”],

“run\_at”: “document\_end”

}

]

}

In this, we can specify author that will be you, the name of the extension, It’s icons , i.e how it will be displayed. the basic description which will be shown, when you publish the app to the store.

In matches attribute, we specify the URL, with some regular expression and when this URL matches, it will run the showoption.js file

Step 2: Creating showoption_.js file_

buttton = document.createElement(“button”);

buttton.innerHTML = “See Markup”;

buttton.setAttribute(“type”, “button”);

buttton.setAttribute(

“class”,

“flex-item-equal nav-link flex-md-auto preview tabnav-tab js-blob-edit-preview js-blob-edit-tab”

);

buttton.setAttribute(“data-togggle”, “popover”);

buttton.setAttribute(“title”, “Headings\n# The largest heading\n## The second largest heading\n######“ );

var a = document.querySelector(“.tabnav”);

if (a == undefined || null) {

} else {

a.appendChild(buttton);

}

That’s it. You have your extension.!!!!!! :)

Testing —

Visit chrome://extensions/
Click on Load Unpacked button and select the folder in which those 2 files are present.
And there you are. Just See if it works.

Publishing —

Visit Chrome Developer Dashboard
You’ll have to pay 5$, one time fees, to upload up to 20 packages on Google Web Store.
After Paying you can publish your extension by following the simple procedure and uploading a .zip file for your extension.

If you like my content, do give it a few claps. I would appreciate it.

Why Use ReactJS

Anu — Tue, 02 Jul 2019 12:23:40 +0000

https://medium.com/coolanant999/why-use-reactjs-8298367f6e0c

Create your first React App — Your Online Portfolio — and deploying

Anu — Tue, 02 Jul 2019 12:22:03 +0000

https://medium.com/coolanant999/create-your-first-react-app-your-online-portfolio-and-deploying-3bc6fe2701d9

DEV Community: Anu

How I did 12K commits in Github within 24 hrs

How I did 12K commits in Github within 24 hrs — Python Automation

So, I did 12K commits in Github within 24 hrs by running an automated python program.

Hackathon — Organizing & finding Innovation

Hackathon — Organizing & finding Innovation

Table of Contents

1. Introduction

2. Objectives

2.1 Closed Innovation to open innovation

2.2 Approach of the company/Organization

3. Recipe for a successful hackathon

3.1 Motivation and Aligned Targets.

3.2 Preparation Phase

3.3 The Challenge

3.4 Participation of Company

3.5 Presence of Active and multidisciplinary people

4. Conclusion

References

Top 5 Cool Github Projects

Create your own chrome extension — and deploy to Chrome Web Store

Create your own chrome extension — and deploy to Chrome Web Store

Intro

Now we’re gonna make the Github Readme Markdown Chrome Extension whose link I gave in the beginning.

Testing —

Publishing —

Why Use ReactJS

Create your first React App — Your Online Portfolio — and deploying