DEV Community: Erwan ROUSSEL

Golang development environment in Docker

Erwan ROUSSEL — Sun, 15 Nov 2020 19:16:24 +0000

Why

Installing development software was driving me crazy when I came up with this idea. If there is something I always install on my workstation, this is Docker ! So let's create an image then an environment to code in Go without having to install anything else than docker.

How it works

As it is described here : https://github.com/dimensi0n/goindock you have an image with a bunch of useful things installed in it and you have a dockerfile wich has a service based on this image as well as a mariadb based service and an adminer one.

What's inside

Alpine as Operating System
Docker in docker
Golang (latest version)
Fish shell and Oh-My-Fish
Git
Fully configured Vim for Golang

How to use it

Get the docker-compose.yml :

curl -fLo docker-compose.yml https://raw.githubusercontent.com/dimensi0n/goindock/main/docker-compose.yml

Up all that stuff :

docker-compose up -d

Then run the environment :

docker-compose run go

Once you've done that you are inside your new development environment, get or clone your project and you can start working on it :)

Ports

If you want your app to be exposed outside of your container, run it on the port 8080 (this is the one the container exposes), then you can go on https://localhost:8080 on your web browser

Use it with Vim

Vim comes fully configurated for Golang in this image.
You have syntax highlighting, Monokai theme.
You also have auto-completion with <Tab> key.

Run :PlugInstall on the first start to install theme and other things then run :GoInstallBinaries.

Compile your package with :GoBuild, install it with :GoInstall or test it with :GoTest. Run a single test with :GoTestFunc).
Quickly execute your current file(s) with :GoRun.
Debug programs with integrated delve support with :GoDebugStart.
Go to symbol/declaration with :GoDef.
Look up documentation with :GoDoc or :GoDocBrowser. Easily import packages via :GoImport, remove them via :GoDrop.
Precise type-safe renaming of identifiers with :GoRename.
See which code is covered by tests with :GoCoverage.
Add or remove tags on struct fields with :GoAddTags and :GoRemoveTags.
Call golangci-lint with :GoMetaLinter to invoke all possible linters (golint, vet, errcheck, deadcode, etc.) and put the result in the quickfix or location list.
Lint your code with :GoLint, run your code through :GoVet to catch static errors, or make sure errors are checked with :GoErrCheck.
Advanced source analysis tools utilizing guru, such as :GoImplements, :GoCallees, and :GoReferrers.
... and many more! Please see vim-go documentation for more information.

Use it with Visual Studio Code

Thanks to the Remote Container extension of VS Code you can now use a running container to work on. You just have to install the extension and then with the shortcut search for Remote - Container: Attach to a running container.

Conclusion

I hope this will be useful to you, I will probably create a nodejs one in order to work on my javascript projects. Don't hesiate to say what you think about this in comments and also don't hesitate to contribute to the project if you have an idea. You can create an issue or make a pull request 😉

🔌 The world in a computer, virtual representation of the reality (PyMatrix)

Erwan ROUSSEL — Fri, 23 Oct 2020 10:48:00 +0000

    ___               _   __      ___    __  ___  __     ( )       
  //   ) ) //   / / // ) )  ) ) //   ) )  / /   //  ) ) / / \\ / / 
 //___/ / ((___/ / // / /  / / //   / /  / /   //      / /   \/ /  
//            / / // / /  / / ((___( (  / /   //      / /    / /\

🔌 The world in a computer, virtual representation of the reality : https://github.com/open-incubator/pymatrix

Why

I was studying a text from Bergson about consciousness in my philosophy lesson when the guy in front of me could not believe that we could be inside a computer simulation. It was so unbelievable for him that even the arguments of the teacher could not convince him. That's why I decided to prove that everything can be a simulation. I created this small program with basic rules to "virtualize" our world.
I also decided to make it open-source for this Hacktoberfest month to share how simple it would be to create a basic simulation of our lives. If a 17 years old programmer achieved this in a few days, we can ask ourselves if someone could achieve the entire simulation of our world with all its complexity and all its rules in 2000 years.

How it works

At the beginning of the program, the size of the world is defined. The size also defines the limit of people the world can handle. If the limit is reached, the world crash. The first number of people is also defined (these people will spawn at the beginning of the program before everything starts). As in the real world, everybody receives an ID at birth, this ID allows us to track what people do.
This simulation has three main concepts : events, relationships and life cycle

Events

This world has four events that can be triggered by someone:

Go to work (W)
Go shopping (S)
Go back home (H)
Give birth to someone (B)

The program randomly decides on who should be triggered the event and when it should be. Humans think they make their own choices but in fact the program instills in them the choices they had to make.

Relationships

Every time somebody is at the same place as someone else, they create a link between them: a relationship. There are three types of relationships:

Acquaintance
Friend
Partner

A few things to know about the partner type:

You can have only one partner
Once you have a partner you can give birth to someone

Life cycle

The life cycle begins when someone is born. Since this event, this person is one year older every 0.1 seconds (I know that's fast but it would be boring if we had to wait 60 years to see people die, I would be probably dead when the first person of the matrix will be dead... So yes I prefer it to be fast). Once somebody is 60 years old, the chance to die is 60% (you can not die until you are 60 years old). Then this chance increases every year, so every 0.1 seconds, somebody has 1% more.

Read the matrix

I agree with you, at first glance, the output of the matrix is very strange. Let me explain this to you.
Every line of the matrix is composed of:

Coords.X:Coords.Y:ID:Event

So you can see who makes what and where.

For example :

10:20:1:W
  |   | |
  |   | |_______________________________________________ Go to work
  |   |___________________ The person who has the ID 1
  |
The place where he is

You could ask me, why did you do that? That's stupid you could just write :

The person who has the ID 1 goes to work on X:10; Y:20

That's right but at the speed of the matrix, you won't be able to read anything if it were not just letters and numbers. At this speed, I challenge you to read one word.

In the future

Since this project is open-source, here is what we could create with the matrix:

Transform it into a websockets server so we could create an interpreter to act on the matrix. Change it live, for example: give birth to someone or make somebody else die.
Create a graphical representation of the matrix, just a few points on a "squared sheet" with their id on top of them would be a good beginning.

What are your favorites open-source alternatives?

Erwan ROUSSEL — Wed, 06 Nov 2019 21:51:34 +0000

I am actually searching for open-source alternatives for the proprietary services that I often use. After brainstorming that's my non-exhaustive list (many of them come from the comments) :

Slack ➡️
Mattermost

Dropbox ➡️
Nextcloud
Owncloud
Bonus: Syncthing

Google Analytics ➡️
Matomo

Google Keep, Evernote ➡️
Paperwork
Joplin

Chrome ➡️
Firefox

Medium ➡️
Dev.to

Webstorm ➡️
Visual Studio Code
Atom
Bonus: Gitpod

Unity ➡️
Godot
Blender

Photoshop ➡️
Krita

Illustrator ➡️
Inkscape

Postman ➡️
Postwoman

Hubspot ➡️
Muatic

Disqus ➡️
Commento

LastPass ➡️
BitWarden
Keepass (offline)

Alexa/Google Home ➡️
Mycroft AI

Please give yours :)

How to introduce your project to the world? 💭

Erwan ROUSSEL — Fri, 25 Oct 2019 20:02:18 +0000

Hey,
I always wondered what did the big Open-Source projects (like Vue.JS, React, RoR, etc...) to become known when they just started.

Are there tricks to allow people to discover your project?

EDIT: Relevant comments/posts

Manuele J Sarfatti • Oct 25 '19 • Edited

Well, they are three very different projects.

React is a child of Facebook, which means it had from the start a high code quality and a wide audience.

RoR was released as open source in 2004 by the creators of Basecamp. There wasn't much else back then, and again, they were starting to build an audience.

Vue.js I honestly have no idea :D

But my take is that the general factors are the same as to why some videos become viral. A mix of quality, audience, and the right moment to push it.

==EDIT==

By the way, if you have a project which you think deserves attention publish it everywhere: here, on relevant subreddits, on Twitter, on Product Hunt etc... Best is if you already have a following. You can ask more famous individuals to promote it (retweet etc.) if they find it useful. And don't publish once! Keep working on it, keep publishing updates, be consistent and if it's actually good eventually you'll get a following.

An Answer to "How to introduce your project to the world?"

Sajjad Heydari ・ Oct 26 '19

#opensource #beginners

How to find motivation 💪

Erwan ROUSSEL — Sat, 19 Oct 2019 20:58:16 +0000

Introduction

A few weeks ago, I woke up every day and every day I told me: "You should code today you have got a lot of projects to finish, you have to do this" but I didn't find the motivation to code. That wasn't the first time, but I didn't know what to do in order to get back this motivation. So, I decided to look after some "motivation stuff" on dev.to and I decided to write something about it to help other people who have the same problem, and maybe it will help me in the future.

My personal tips

Find a community

It might be strange but taking part in a developer community help me through this little period because they inspire me every time they do or share something. Here is a non-curated list of slacks communities: http://blog.honeypot.io/21-slack-channels-for-software-developers/

Do what you want to do

In fact, I didn't even found a comment on this but that's something I've learned during this period. It seems logical but you don't have to care about others, If you want to do something, go for it.

Never give up

Once again it seems logical but sometimes you need to read it or you need somebody to tell you this: "Don't give up", if you believe in something just do it, if you don't find something to believe in.

Find a project

If you don't have any idea of a project, learn something new, something it might be interesting to learn for you, a new technology, a new language or maybe something completely different like a new domain (Machine learning, etc...). If you are searching for a project, the best thing to when you need motivation is to work with other developers. You should maybe take a look at an Open Source project, OSS is always looking for new contributors and it might make you feel useful.

Comments I found on dev.to

Be happy about little things

Saalik Lokhandwala • Aug 31 '19

Small wins are super important to keep the momentum going on a project. I try to tell people about my project and sometimes involve them as collaborators. Anytime there is someone who's waiting to see what I'm working on, I find myself more motivated to work!

I think sharing work at all levels is really great for feedback, I'm definitely trying to get better at that myself.

Thanks for writing this!

Chris Achard • Aug 30 '19

Great post - starting small is more important than most people realize. Just start with something fun, silly, and unassuming! If you get really interested in it, then it will quickly grow anyway - so don't worry about that from the start.

Take a break

Emmanuel Obogbaimhe • Apr 9 '18

I recently experienced this (to a lesser degree still do). What I do is take a break from coding (apart from my day job which requires I code). Do something, different that relaxes your mind. When your ready to get back to it, don't jump directly into coding, first plan on what you want to do/make/learn. Get a clear plan mapped out and an approach. Also have multiple items that you can work on. If you get stuck on something for a while, jump to another item briefly, but make sure you return to what you were stuck on before (many times when people jump around they lose interest in what the were previously working on). All the best man!

My favorite

Isaac Lyman • Feb 5 '18

Some thoughts:

Don't compare your brand-new ideas to other people's finished products. (As the cliche says, don't compare your "insides" to other people's "outsides".) For every project that gets finished, there are a hundred more that never make it past mile 1.
Not every project is worth finishing. If you actually made the effort to take every idea to completion, you'd be exhausted and wouldn't have any time for the simpler things in life: family, friends, fun.
In order for me to keep the motivation to finish a project, it needs to align with two or more of my passions. "Getting rich" is not one of my passions, so I can't necessarily reach the finish line with an idea just because I think it will be a huge success. Music and rap lyrics and fiction, on the other hand, are my passions, so projects I undertake in those categories have a much better chance at success. When I get discouraged about the process, I remind myself how much I care about the goal.
Every project has boring and frustrating parts. Here's one of my favorite explanations of this: Being aware of the "mid-project slump" helps a lot. Get past that and you're on your way.
Don't go it alone. Find another person who cares about your project (or even just someone who cares about you) and keep them up to date on your progress.
Don't overdo it. If you try to work on a project for 10 hours a day, 7 days a week, you'll quickly pass a "punishment threshold" where your brain will convince you to procrastinate getting back to it because it's so exhausted. Limit yourself to reasonable hours and take days off. Leave yourself wanting more.

And the one that worked for me

Comment Not Found

Gitote, two weeks after

Erwan ROUSSEL — Fri, 07 Dec 2018 09:42:31 +0000

Two weeks ago I saw a post about this new open source end-to-end software development platform with built-in version control, issue tracking, code review : this post. I signed up to see what does this new platform look like. And after two weeks I can give my mind.

⚠️ I'm only 15 yo, my English isn't perfect and I want to improve it so if you notice a language error, say it in a comment. ⚠️

Good points

It is new and open source

I don't know if it's an argument but in my mind, that's very important.
I love open source alternatives. This is based on Gogs which is self-hostable.

Simple user interface

The first thing I noticed is the user interface, so simple and so easy to understand, okay some people can say it is a copy paste of the Github's design but that's not a problem for me.

Visibility

Gitote is made with the concerns of the social. There is an Explore page which is absolutely amazing I discovered a lot of good projects especially Just Another shell or Full Tilt Bash.

Negative points

No unit testing service

That's a big problem for me, I need unit testing but today if you want to use a unit testing service you will have to create a mirror on Gitlab/Github.
EDIT: Gitote is setting up a drone-ci instance.

I don't know but I have to find other negative points

Conclusion

I don't say you should use it instead of Gitlab/Github/Bitbucket but you should still try Gitote. I forgot to mention that I am remote intern at Gitote but I said all the things I thought about it good or bad.

There is not a lot of people for now on Gitote but I think the popularity is only a matter of time.

2 ways to learn how to code

Erwan ROUSSEL — Mon, 19 Nov 2018 16:50:28 +0000

After two years of programming, I can see two ways to learn to code.

⚠️ This is my opinion, if you don't agree with me don't hesitate to give your mind in a comment ⚠️

Practical way

When I started programming two years ago, I was 13, I still wanted to code without reading documentation or without to know basics.

That's how I started to learn HTML, then I learned PHP, in the beginning, I learned the Copy/Paste Oriented Programming. But over time I learned a lot of things through practice. I started to stop copy paste and to test the libs I was using by testing all methods/functions/class which was in those libraries. And that's how I discovered the practical way to learn to code.

Good points

Fast to learn
Very fun

Bad points

You can skip something important
It is difficult to debug something when you didn't read the documentation.

Theoretical way

Lately, I discovered the theoretical way. I wanted to learn how to use React. So I went to the getting started and the documentation offers to way to learn React, I decided to try practical way and... I didn't understand anything. Since a few months, I need to know how it works behind the code to use something so I decided to read the theoretical guide and I understood everything.

Good points

You know how it works
Easier to debug

Bad points

It takes a lot of time
It is sometimes boring

What I prefer

Like I said, since a few months I need to know how it works behind my code to understand how to use something. That's why I started to read a lot of documentation and to code less.

What should you use

I can't say you should use this one because it's personal. To answer this question, you have to try those two ways to know what you should use.

Github vs Gitlab

Erwan ROUSSEL — Fri, 26 Oct 2018 19:20:49 +0000

When Microsoft bought Github, everybody wanted to move to Gitlab. After 5 months on Gitlab, I can do the comparison.

Philosophy

Github and Gitlab are two different git repository managers. I think I don't need to present them because almost everybody already knows this two services.

Gitlab is a professional git repository manager. You have a lot of tools to deploy, test your applications. It can also be self-hosted, which is a very good point.

Github is more like a social network, and almost every big open source libraries, framework or tools are on Github.

Use cases

Gitlab

For me, Gitlab is a very professional git repository manager. It means if I were a professional programmer, I'll use Gitlab to host my git repositories. For many reasons like :

Free private repositories
Docker Registry / Free Docker registry
Powerful CI tools

Github

If you want to code an opensource project, Github will be a better option. Github is more like a social network. It means you will have more visibility on Github whereas Gitlab. There is also one good point for Github :

Community

Yes, the open source community didn't move from Github to Gitlab that's why I said, GO GITHUUUUUB if you want to code an open source project.

My mind

I think twice are very good choices. It only depends on what you want to do.
Gitlab is very useful but I come back to Github to have better visibility for Filtrify. Sorry, Gitlab ^^

I'm testing gitote.in, I should write something about it in a few weeks

How to contribute to an Open Source Project

Erwan ROUSSEL — Sun, 21 Oct 2018 13:46:35 +0000

This is October, so many people want to contribute to an Open Source Project, especially with the #hacktoberfest challenge. But when you start, it's difficult to understand how to do it. That's why I decided to write this post.

Do you want to contribute to an open source project? Here's how!

1st - Read the README

If you already did it, you are lucky, if not, READ IT! It is called README not DONTREADME.

2st - Feature, fix ?

If you have a feature idea, just create an issue to describe the feature and don't forget to say that you can code it!

If not, take a look at the issues, maybe you can fix something.

3rd - Read the CONTRIBUTING file

All the things you have to do are written in the CONTRIBUTING file. Read it carefully. You have chosen your project! You are very happy and you want to contribute!

4th - Fork the project and code!

You just have to click on the little button at the right corner of the repository page. Example :

You'll need to learn how to use Git -> Git Learning Guide

Then clone your project.
Add your modifications.

5th - Commit and create your Pull Request (PR)

Now, you have to commit your modifications.

Then, click on the Pull request button on the official repository page :

Click on New Pull Request and then click on Create pull request

Give your pull request a title and a comment (According to the CONTRIBUTING file)

And finally, click on Create Pull Request.

You made your first Pull Request !!!

I hope it will help you ^^

Thanx to Quantum Sheep