teleren/devto huggingface dataset:
New to GO, documenting my learning process.
Tags: go, beginners, writing, tutorial
Published: 2017-12-14 01:24:23

---
title: New to GO, documenting my learning process.
published: true
description: Trying a new learning approach for a new language. Asking for advices. 
tags: #golang, #go, #beginners, #writing, #tutorial
---

Hi all, 

disclaimer: english isn't my first language, non/technical stuff usually ends up in non-sense sentences. 

**little background, skippable**

The language I'm most experienced in is c# and SQL. At least, these are the ones that gives me the best salaries. Following vb.net, javascript, java, vfox pro, vbscript (for office and msaccess tricks) and so on.

I love programming, but recently I've realized that every time I've learned a new language is by demand. Always has been this way. 

Probably, the only time in history I learned a new language by pure curiosity was QBASIC in 1997. After that I learned c++, powerbuilder, fox pro as part of highschool. Java in university and and my first job was in Java too, but .Net was the most required by market for junior developers, so I took that endless road.

**the point**

Recently I went to the go tutorial and ran the baby steps, and while on that, I was speaking out my mind about some actual differences against all the languages I know. While on this, my girlfriend (who usually ignores me when I'm on my stuff) felt curious and two weeks later shared with me the interest into learn some development. 

I've never documented my learning process for any language. I would like to start a (kind of) tutorial for Go/Html/javascript as my I learn. 


To accomplish this, I'm thinking into using the [Feynmann learning technique] (https://mattyford.com/blog/2014/1/23/the-feynman-technique-mode). 

The plan is not to create only a tutorial for dummies in the popular way, but actually document the learning process and create something useful for someone who had *never-ever* tried programming, like the 1997 myself.


...
Have any of you saw or did or know some techniques to document the learning process?

Have any of you know some awesome way to teach newbies a new language from scratch (even programming concepts) that look like the writer was actually learning as he typed?

Am I explaining my self enough?
Increments welcomes trelloに行ってきた
Tags: increments, trello, workq
Published: 2017-11-16 02:18:58

---
title: Increments welcomes trelloに行ってきた
published: true
description: Increments welcomes trelloに行ってきた
tags: Increments,trello,workq
---


![#trello storyを聞く #workq](https://thepracticaldev.s3.amazonaws.com/i/idpmbd4xsa8dvn5dzdrt.jpg)

# 目的

1. 現在、自社内で考察中のサービスメイキングの参考になることがあれば良いな
2. Trelloがいかにして生まれ、いかにして今の状態があるのか？を知りたいという好奇心
3. Trello Teamがどのように機能しているのか？などの雰囲気を知り自社Teamにも活かしたい


# サービスで大事なこと

1. 感情：共感(Empathy)
2. 機能：連携(Integration)
3. デザイン：Simple

## シンプルに課題解決することをを意識する

そうしないと…

1. UI/UXに影響が出てユーザーの導入コストがあがる
2. 共感を得るコストも上がる

## 機能追加要望は真に受けない

1. 言われたとおりにやらない
2. ユーザーの苦しみにフォーカスする（課題の本質を見る・知る）

# その他

- Michael氏が日本のアウトプットコスト高い文化的特徴を認識されていた笑った。
Running on Fumes: Some Small Productivity Tricks
Tags: productivity
Published: 2017-12-15 18:13:13

---
title: "Running on Fumes: Some Small Productivity Tricks"
published: true
tags: productivity
canonical_url: 
---

The past week of work has been unusually long and tedious. Just wanted to share a few small tips I’ve been using to power through it:

## 1) Listen to the same thing on a loop

I picked this up from Tim Ferriss. Apparently, several top performers listen to the same song on repeat when they need to stay focused. I find that one song gets old pretty quickly, so I loop an entire album instead – right now, _The Shape of Colour_ by Intervals. It’s energizing, has zero lyrics, and all the tracks sound similar enough that they flow together into one 34-minute opus (turning on cross-fade helps too).

## 2) Ignore the time

Nothing makes a long day worse than thinking about how much longer it’s going to be. I’ve removed the clock from the menu bar on my computer and keep my phone out of sight.

3) Write down what you need to do in small steps

Separate _what_ you need to do from _how_ you actually do it. This gets all the racing high-level thoughts out of your head so you can [prioritize and execute](https://www.amazon.com/Extreme-Ownership-U-S-Navy-SEALs/dp/1250183863/ref=sr_1_sc_1). You’ll be surprised how much more efficient and effective this makes you, especially if you’re tired. 
  - For the developers: if you’re having a hard time with a complex function, use comments or [pseudocode](https://dev.to/cannikin/make-your-pseudocode-your-real-code-96n) to outline it first. If anything, you’ll probably write cleaner code with this approach!

## 4) Switch tasks for a few minutes if your brain really gets fried

Guess where this post came from…

## 5) Don’t let yourself totally stop working

Even though I’m taking a break by writing this, I’m still producing something. Keep up the little bit of momentum you do have. The sooner you finish what you need to do, the sooner you can put it away and forget about it. Fight to the finish.
Code snippets or nah?
Tags: discuss, snippets
Published: 2017-12-13 21:03:57

---
title: Code snippets or nah?
published: true
description: Should I be more open to using code snippets?
tags: discuss, snippets
---

Code snippet tools seem wildly popular in many text editors and IDEs. While I haven't worked on any heavy projects, I don't find much appeal in using code snippets. I can understand the productivity benefits that they can provide, but I feel as though it can take away from the enjoyment of understanding what you're writing to some extent.

Am I missing something or being naïve about this? I would love to read thoughts from people who use them in a more professional environment or work on things daily!
I'm the maintainer of Babel, ask me anything! 
Tags: ama, javascript, babel, opensource
Published: 2017-12-13 17:38:39

---
title: I'm the maintainer of Babel, ask me anything! 
published: true
description: I maintain Babel, one of the largest open source JavaScript projects, and I work as a JavaScript Engineer on the Behance team at Adobe. Ask me anything!
tags: ama, javascript, babel, opensource
cover_image: https://thepracticaldev.s3.amazonaws.com/i/vrp4rx1q8hls6aue1wcm.jpg
---

Hello friends 👋! I'm Henry, an engineer on the [Behance](behance.net) team at Adobe in NYC. I started with an interest in [data visualization](http://tppstats.herokuapp.com/) but then moved to tooling.

I luckily got an interview at Behance because of my contributions to [JSCS](http://jscs.info). I helped to merge it with [ESLint](https://eslint.org) and along the way discovered [Babel](https://babeljs.io) and learned about "compilers". Now I get to spend about 50% of my time working on Babel at work. I am looking forward to the time when projects are able to work on OSS part/full time though!

Recently I gave some talks on [what it's like to be a maintainer](https://github.com/hzoo/maintaining-an-oss-project), [how Babel is more than just the code itself](https://github.com/hzoo/so-how-does-babel-even-work), and [dealing with burnout and the community](https://github.com/hzoo/maintainer-heal-thyself). I did [post](https://twitter.com/left_pad/status/938041651452416004) I was going to spend less time on it to focus on health, so hopefully some people/companies will step up!

I enjoy playing [ping pong](https://twitter.com/left_pad/status/878788335862460416), [board games like 7 wonders](https://twitter.com/left_pad/status/917564949693640704), video games (a lot of [Mario Odyssey lately 😊](https://twitter.com/left_pad/status/927917767394652160))

Ask me about OSS (its myths, its community, and its relationship to community/faith) or about the nature of Babel: it's difficult role in the ecosystem trying to glue it all together: spec compliancy with TC39, code speed/size complaints, JS fatigue, and handling it all as a group of volunteers.
Early access to ready-made, tested API collections for Postman
Tags: nocode, api, postman, producthunt
Published: 2017-12-13 15:09:07

---
title: Early access to ready-made, tested API collections for Postman
published: True
description: tested API collections for Postman
tags: No-code, API, Postman, ProductHunt
---

[Zeroqode](https://zeroqode.com/) is about to launch Postman Collections - a directory of ready-made, tested [API collections](https://blog.zeroqode.com/early-access-to-ready-made-tested-api-collections-for-postman-48d5056c50f5) that can be imported into Postman App with 1 click. Free of charge :)
Get early access and sign up here: [Postman collections](https://www.producthunt.com/upcoming/postman-collections)
The Debugging Golden Rule
Tags: programming, practices, beginners
Published: 2017-12-13 13:51:28

---
title: "The Debugging Golden Rule"
published: true
description: "Developers need to remember the Debugging Golden Rule."
tags: programming, practices, beginners
canonical_url: https://jason.pureconcepts.net/2014/05/debugging-golden-rule/
---
> Don't question others until you've questioned yourself.

Developers, especially new developers, often forget this when debugging. We jump into the debugger. We add tracing statements. We review the commit log.

Such actions can be misguided. Before debugging the code we must follow a moral code. Debugging needs a [Golden Rule](http://en.wikipedia.org/wiki/Golden_Rule). A rule to remind developers of a few important facts of debugging.

## 99% of the time it's you
I had an excellent TA for my introductory Computer Science course. He gave great advice for improving your craft. Some of which became the foundations for [routines of a good developer](https://jason.pureconcepts.net/2009/12/good_developer_routines/ "Routines of a Good Developer").

In one of our more difficult labs he expressed his frustration with the class:

> Listen up! Stop asking me, "What's wrong with `gcc`?" `gcc` has been widely used for over three decades. You have been programming for half a semester. `gcc` is not broken!

I remember his words anytime I start questioning others. A far majority of the time, the bug is in _my_ code.

## Avoid tunnel vision
Debugging is the art of asking the right questions. If you start by questioning others, you will likely waste your time asking the wrong questions.

We've all done it. A recent upgrade revealed a bug in the code. Now you have a bug in your brain: *it's the upgrade*.

Of course you should question the upgrade. But question other changes too.

## You still have to fix it
Let’s say you prove the language has a bug, Internet Explorer behaves differently, or the developer before you broke the build. What then?

Well, *you* still have to fix it. Even when it is not you, you still must develop the fix. No point in focusing on blame.

Following the _Debugging Golden Rule_  keeps developers grounded, focused, and part of the solution. Remember it the next time you find a bug in the code.
How to build a successful developer community
Tags: discuss, community, dev, hackathon
Published: 2017-12-13 13:47:58

---
title: "How to build a successful developer community"
published: true
description: Tips on how to build a dev community
tags: #discuss, #community, #dev, #hackathon
---
#####So i'm planning to start a developer community here in cameroon (africa). It will be basically about sharing experience, learning and making some events... also i'm planning to create free hackathon, trainings.
I will like to have some of your tips on how to build a great dev community, what to do, how to organize etc. ;)
Should a Junior Developer start with a remote job?
Tags: discuss, remote, junior
Published: 2017-12-13 13:05:10

---
title: Should a Junior Developer start with a remote job?
published: true
tags: #discuss #remote #junior
cover_image: https://s3.amazonaws.com/aircto-blog/2016/09/challenging-your-mindset-2ndskiesforex.jpg
---

I've been asking myself this question a lot recently. I'll be looking for a Junior Android Developer position in the near future and I'm really tempted by the option of finding a remote position. But having a mentor close by is really important for me at this stage. 

Some people have told me that being remote shouldn't be a problem, as long as the company promotes a lot of communication online via chat, email and video calls to encourage engagement between seniors and juniors along with code reviews and pair programming.

What are your thoughts on this, Mr./Mrs Reader?
W(AI) now 
Tags: ai, facebook, discuss
Published: 2017-12-13 12:19:18

---
title: W(AI) now 
published: true
description: About the AI hype these days
tags: AI, Facebook, discuss
---
AI concepts were available since the late 1970 in computer languages. I found out about AI in Java (me-sa Jar-Jar) like 20 years ago and even then there were free libs to support it. Why did it take this much time for AI to gain momentum and to become #1 thing that people lie about in their CVs? Did we needed that much time to grasp the concepts of it? Or was it something completely else. Voice recognition software was commercially available since the late 90s. What's the big deal now, why now is this topic so popular in Software development. Why are people so hyped up about it now. It makes me wonder, maybe we did not have that much knowledge about every one person dead or alive (thanks Facebook), or maybe the algorithms were not sophisticated, or maybe the general public was not interested in Amazon guessing what their Christmas wish is. One can just ponder.
Whatsapp Chat from CLI Using Puppeteer
Tags: javascript, whatsapp, cli, console
Published: 2017-12-13 07:33:15

---
title: "Whatsapp Chat from CLI Using Puppeteer"
published: true
description: "(GoogleChrome puppeteer)[https://github.com/GoogleChrome/puppeteer] is interesting project to create browser automation tools, testing tools or web scrapping. I was wondering to use it for something useful and an idea popped in about creating CLI application that can be used to send and receive messages on Whatsapp. So I went on to creating (Whatspup)[https://github.com/sarfraznawaz2005/whatspup], a name based on both Whatsapp and puppeteer.

**Features**

- Send and receive messages
- Read Receipts
- Switch between users to chat with
- Popup notifications for new chat messages
- Privacy settings for popup notifications
- One-time authentication, no need to scan QR code again and again
- Windowless/headless (hidden) mode
- Colorful chat messages

(You can check it out here)[https://github.com/sarfraznawaz2005/whatspup]
"
tags: javascript,whatsapp,cli,console
---
Using Sass in a React app development
Tags: reactsass
Published: 2017-12-13 05:30:22

---
title: Using Sass in a React app development
published: true
description: Using Sass in a React app development
tags: React Sass
cover_image: https://thepracticaldev.s3.amazonaws.com/i/3715ef9hxvyheupd5z64.png
---
# Customizing Create React App : *CSS*

## CSS → Sass
Getting started customizing [create-react-app](https://dev.to/koheishingaihq/how-to-get-started-with-react-9jj) .

### Install npm module : *node-sass-chokidar*
```bash
# Current path : ~/create-react-app
npm install node-sass-chokidar --save-dev
```

### Install npm module : *npm-run-all*
```bash
# Current path : ~/create-react-app
npm install npm-run-all --save-dev
```

### Edit package.json : *script*
```diff
# Current path : ~/create-react-app/package.json
-    "start": "react-scripts start",
-    "build": "react-scripts build",
+    "start-js": "react-scripts start",
+    "start": "npm-run-all -p watch-css start-js",
+    "build": "npm run build-css && react-scripts build",
+    "build-css": "node-sass-chokidar src/ -o src/",
+    "watch-css": "npm run build-css && node-sass-chokidar src/ -o src/ --watch --recursive",
```

### Add custom sass file to the project
```sass
/* File path : ~/create-react-app/src/Custom.sass */
body
  background: powderblue
```

```diff
# File path : ~/create-react-app/src/App.js
import './App.css';
+ import './Custom.css'
```

→ Running `npm start` compiles `.sass` files to `.css` under `/src` directory.  
→ Open http://localhost:3000 to see `create-react-app` .

> Demo : [koheishingaiHQ.github.io/create-react-app-with-sass](https://koheishingaihq.github.io/create-react-app-with-sass)

![create-react-app-with-sass-screen-shot](https://c1.staticflickr.com/5/4465/36878306283_8811ec8516_b.jpg)
Creating a React app with Create React App
Tags: react
Published: 2017-12-13 05:07:42

---
title: Creating a React app with Create React App
published: true
description: Creating a React app with Create React App
tags: React
cover_image: https://thepracticaldev.s3.amazonaws.com/i/3715ef9hxvyheupd5z64.png
---
# Using Create React App
> Official : [create-react-app](https://github.com/facebookincubator/create-react-app)  

## Quick Overview
```bash
# Current path : ~/.
npm i -g create-react-app
create-react-app create-react-app
cd create-react-app/
npm start
```
[![asciicast](https://asciinema.org/a/151496.png)](https://asciinema.org/a/151496)

Then open http://localhost:3000 to see `create-react-app` .

> Demo : [koheishingaiHQ.github.io/create-react-app](https://koheishingaihq.github.io/create-react-app)

![create-react-app-root](https://c1.staticflickr.com/5/4509/37268153700_b95567ae0f_h.jpg)
How should markdown be saved and rendered?
Tags: discuss, webdev, javascript
Published: 2017-12-13 04:48:24

---
title: How should markdown be saved and rendered?
published: true
description: Trying to figure out how markdown should be saved and rendered?
tags: discuss, webdev, javascript
---

I'm trying to figure out the best approach for saving markdown to a database and then rendering.

Should the raw markdown be saved as a string into the database and then returned and converted to HTML before rendered on the front end? Or should the markdown be converted to HTML and then saved as a string into the database? Then it could just be passed onto the front end as raw HTML.

My setup:

- MongoDB for db
- Node for backend
- Ember.js for frontend

Would love to know what approaches are being used out there.
BKDR v2 - My Journey Into ReactJS
Tags: react, javascript, php, codeeditor
Published: 2017-12-13 03:42:16

---
title: BKDR v2 - My Journey Into ReactJS
published: true
description: My Journey Into ReactJS
tags: #react #reactjs #javascript #php #codeeditor
---
![alt text](https://thepracticaldev.s3.amazonaws.com/i/1i37ai080cygcw8agyug.jpg "BKDR Code Editor")

When I originally created my in-<a href="https://codecanyon.net/item/backdoor-browser-based-code-editor/13725356" target="_blank">browser code editor</a>, I wrote it all in CoffeeScript. Worse, I wrote it in one big file. What started as a simple cool idea, kept getting bigger with every feature or new idea. Eventually, I knew I could not continue working this way. Request for new features were becoming more difficult to organize, and scaling became an issue.

This was all due to not having a plan. It was a fun, cool idea that became something more, and when I realized it, it was too late in the process. So regardless of not wanting to, I knew I needed to start over.

### What's Next?

Around the time when I was contemplating on how and what to use to rebuild my code editor, React and Angular where trending. Angular 2 was in beta, and was different enough from Angular 1, that it made me hesitant on any attempt to learn it. Additionally, React was a lighter framework from my brief understanding. So I decided on React.

One thing I didn't want to do was learn React WHILE remaking my web app. It just seemed like an unwise decision that would eventually come back to haunt me. I needed another project to really flex my sandbox adventures. Of course, knowing me, I created a <a href="https://mocfolio.com" target="_blank">social network</a> (like that was the easier option).

### Class In Session

In the end, I was able to take away so many valuable lessons. For example, jQuery sometimes becomes a reflex when you confront a situation. But in React, you need to change your mindset. We're so use to manipulating the DOM with JavaScript and jQuery. However, one of the greatest benefits of React is it's ability to update state changes within components.

Within a component, HTML or other components can be returned within the render method. Every time the state is updated or replaced, it triggers the component to re-render. This is handled through the virtual DOM before being updated in the actual DOM. Redux also adds another great element to React with it's store. Basically it's ability to have a centralized source of data that can be updated via dispatch. This was a huge feature in creating my web app. For simpler projects, this may be overkill. It really all depends on your needs.

### The Result

After spending about eight months learning React, I started on version 2 of [Backdoor](http://bkdr.pro) (which I rebranded as [BKDR](http://bkdr.pro)), in March of 2017. Now, 10 months later, I'm about to release my beta within the next couple of days, fully built in React and handling the server side in PHP. I estimate I wrote over 30+ components, all nicely organized and optimal to scale properly.

If you'll like to stay posted on my Backdoor progress, you can visit [BKDR.org](http://bkdr.org).
Dev.to new design edits !
Tags: discuss, webdev
Published: 2017-12-12 23:06:06

---
title: Dev.to new design edits ! 
published: true
description: What I think about dev.to new design edits
tags: #discuss #webdev 
cover_image: https://thepracticaldev.s3.amazonaws.com/i/1rx0ho4znz2qgfrxcbw5.PNG
---

Believe it or not, I was inspecting the notification svg element of this website , then I refreshed and the design of the website changed.It was a funny moment lol.
So I like the new design , it feels like a cartoon (it's just my feeling).I really believe that this website should stay different like the way it is because I have a really good impression as a user in this website and I like contributing in it because it's simple, minimal and there are a lot of interactions in it.
How it's different from other websites? this question needs some minutes to think about but the first answer that comes to my mind is : I just feel that. 


**what do you think about the dev.to new design**
What's the proper etiquette for forking an abandoned repo?
Tags: discuss
Published: 2017-12-12 20:55:46

---
title: What's the proper etiquette for forking an abandoned repo?
published: true
description: 
tags: discuss
---

I came across an inactive repo that I'd like to work off of. I opened an issue to see if they have any plans to come back to the project, with no answer.

I'm wondering what I should think about going forward in terms of attribution or any other considerations if we re-release the code as our own project.