teleren/devto huggingface dataset:
No social media in the mornings - Day 2
Tags: career, productivity, mentalhealth
Published: 2018-04-25 23:28:31

---
title: No social media in the mornings - Day 2
published: true
description: Second day without checking social media in the morning.
tags: #career, #productivity, #mental health
---

This another entry from my no social medial in the morning journal. For more details, I invite you to read my [what would your life be without social media in the morning](https://dev.to/josegonz321/what-would-your-life-be-without-social-media-in-the-morning-1g2l) article.

As a friendly reminder, my main goal is to inspire and motivate you. It's much easier than you think **as long as you take action!**

Let's continue the journey!

## Day 2

1. **Turning off the alarm.**
    It was one of those mornings. I hit the alarm and went back to bed. My eyes were heavy and wasn't feeling well. My stomach was still bothering me. 

    I passed out for another hour until my wife texted me. Now, I had to rush my morning routine. Not a good sign.

2. **Phone in pocket**

    The shower did very little to wake me up or put me in a better mood. I missed another running day, a chance to get my endorphin rush! 

    The phone went straight into the pocket as I rushed out of the room. At least I won the phone battle this morning. No social media check.

3. **Rushing**
    As I said goodbye to my wife, I rushed out the door. I wasn't exactly late but I wasn't on time either. I was a bit annoyed and grouchy. This morning's tea wasn't helping either. 🍵 

    In short, I was lacking presence. It was a total different experience from yesterday's morning.

4. **Another cloudy morning**

    It wasn't raining but today I noticed the gloomy and even depressive morning. Not a good way to start your day.

    Instead of listening to music or an audio book, I made a audio recording on how I was feeling. It's cathartic therapy. A strategy I learned from a mentor a few years ago.

    Usually these audio recordings help me out. But today, it wasn't an emotional or mental problem. It was a physical issue. My eyes were burning and my stomach was bothering me. A very bad combination.

5. **Work, work**

    Luckily, work was pretty normal today in the morning. A welcomed relieved to my already agitated morning.

## First time checking social media

- Twitter: sometime 1:00pm
- Email: sometime after 1:30pm
- Dev.to: 3:00pm
- Reddit: nope
- News: nah
- Crypto currency: 8:30am - on my way to work.

Hey, I did pretty good today on the social media check.

I came short on the crypto currency, again. It's OK. Usually, it a quick check to see the daily prices. I don't read any articles or news about it.

To be fair, I had a busy morning at work trying to set up a new authentication system into our software.


## Conclusion

A really rough day, but met my personal goal of not checking social media. I didn't ask for this day but it is what it is.

These are the type of days that really test you. And as such, I think you should welcome them as much as you welcome the good days. 

What does your journey say? 🙂

Thanks for reading. Till tomorrow!
Changelog: Adjustments to post page design
Tags: meta, changelog
Published: 2018-04-25 22:17:59

---
title: Changelog: Adjustments to post page design
published: true
description: If you're on desktop, you'll notice that we have added a sticky navigation bar to the post page.
tags: meta, changelog
---

The adjustment is only visible on desktop. If you're reading this post on your phone it will be less clear what I’m referring to.

If you're on desktop, you'll notice that we have added a sticky navigation bar to the post page. Articles and discussions will now be accompanied by more info about the author of the post, as well as navigation to other posts that are trending on [dev.to](/). It leans towards selecting"trending" articles which share tags with the post you are reading, but if the tag isn't as popular it will go more general.

This style is fairly common on the web, but it’s still a departure from our previous design. No design change is without its critics, but we think this _direction_ is a good one that will improve the reading and discovery experience. 

If you have thoughts about how we could tweak this, we'd gladly hear your ideas. We plan to continue experimenting with the trending articles and the design here as we try to improve the experience.
Happy coding ❤️
Dockerizing Java 10 Spring Boot app
Tags: springboot, java, docker, devops
Published: 2018-04-25 20:51:14

---
title: Dockerizing Java 10 Spring Boot app
published: true
tags: spring-boot,java,docker,devops
canonical_url: 
---

In my previous [article](https://dev.to/gimlet2/java-10--migration-story-41k7) I’ve been talking about using **Java 10** to build and run your [**Spring Boot**](https://projects.spring.io/spring-boot/) app. Now it is time to talk how to put it in Docker container. Better support of containerization was one of the main features of Java 10 release. So, let’s go!

That is fairly simple process, so just take a look on following code snippet:

{% gist https://gist.github.com/gimlet2/57c277353f1febbd9a17d28f59acdfd3.js %}

Here, as you can see, I use multi-stage Docker build file. Quick note: multi-stage builds are supported with **Docker 17.05** or higher but result image is backward compatible(at least from my experience). On the first stage it downloads **JDK** from Oracle’s, but it can make sense to store your own copy somewhere closer to your build server since it isn’t that small — a little bit less then 200mb. So, it is downloaded, unziped and ready to be used. But not so quick.

As you probably remember, **Java 9** gave us module system and **JDK** itself is also modularized. That means we don’t have to bring whole **JDK** to production but we could build our own striped version specifically for our app’s needs. There is jlink tool provided for that. Just take a look how it is used in the build process. The modules listed there should be enough to run a typical **Spring Boot** application. In my production case I had to put java.scripting, jdk.scripting.nashorn to the list as well.

On the second stage it copies results from previous one, defines some environment variables, exposes port, copy launch.sh and app’s artifact. Not a rocket science at all.

And here is launch.sh script I’ve just mentioned:

{% gist https://gist.github.com/gimlet2/31c97af8624d53b84d9db175b4e985ba.js %}

That is just a small helper to ensure that there are all important things provided, etc. But, sure, it is optional.

And that should be enough to put your app to the production. Please, put some comments down if you have some thoughts how to make it better!
Getting an employer to take a chance on you
Tags: discuss
Published: 2018-04-25 16:35:54

---
title: Getting an employer to take a chance on you
published: true
description: 
tags: discuss
---

How do you get an employer to take a chance on you. I have been doing desktop support for some times now and recently got into software development (about 1 year experience). I feel that everyone wants experience and no one is willing to take a chance on a new developer. How can I show employers that I am motivated and will work hard and won't let them down.
Hashing Passwords: One-Way Road to Security
Tags: hashing, cryptography, passwords, cybersecurity
Published: 2018-04-25 15:56:57

---
title: Hashing Passwords: One-Way Road to Security
published: true
description: Hashing is the foundation of secure password storage.
tags: #hashing #cryptography #passwords #cybersecurity
canonical_url: https://auth0.com/blog/hashing-passwords-one-way-road-to-security/
---

A strong password storage strategy is critical to mitigating data breaches that put the reputation of any organization in danger. Hashing is the foundation of secure password storage.

Learn about the theory behind hashing, its benefits, and its limitations.

[Read on #️⃣](https://auth0.com/blog/hashing-passwords-one-way-road-to-security/?utm_source=dev&utm_medium=sc&utm_campaign=dasec_hashing)

![Hashing Passwords: One-Way Road to Security](https://thepracticaldev.s3.amazonaws.com/i/uuk7p5if29okirq9del6.png)
We don’t need a social networking website. We need building websites to be more accessible.
Tags: socialnetworking, facebook
Published: 2018-04-25 15:49:20

---
title: We don’t need a social networking website. We need building websites to be more accessible.
published: true
description: 
tags: social networking, facebook
---

Some may know that I’ve been wanting to build an open source social networking website for a long time. The trouble with building a social networking site is there is so much to do. Especially if you want to build something that’s on par with the likes of Facebook.

No one wants to help build it with you and it’s hard to build all of it yourself. I really wanted to get something out there, especially with the news on Facebook recently. I thought to myself “this is it, I need to build this now”. I then start building and just get overwhelmed with the amount of work that needs to be done.

There are already open source social platforms out there already, but I thought I could build it better (I was so wrong about this). There are also decentralised social networking platforms that are great, but it isn’t accessible to everyone.

This got me thinking, what we need to do is make building a website easier and cheaper. We need a platform that similar to that of myspace where you can build your profile how you like, but more limited so we don’t have a huge mess with flashy gifs.

We then also need the ability to add a custom domain and connect that as easily as possible. People would then be able to have their own personalised website that is also their profile.

They should have full control over what is shown and what isn’t and they should be able to download that code fully to allow them to move to another server if they so choose.

These sites/profiles should be able to connect (or subscribe to) one another. I suspect in a very similar way to how WordPress and JetPack connect to one another.

I guess you could reskin WordPress as a more profile based website and have a platform like wordpress.com that allows users who are a less experienced sign-up and build their profile. More advanced users will download and its places on their server and then start building their profile.
Libro: Ruby on Rails Notes for Professionals
Published: 2018-04-25 16:07:31

---
title: Libro: Ruby on Rails Notes for Professionals
published: true
tags: 
canonical_url: https://yorodm.github.io/blog/ruby-on-rails-for-professionals/
---

# Libro: Ruby on Rails for Professionals

Un excelente libro producto del trabajo y conocimiento de cientos de usuarios de [Stack Overflow](http://www.stackoverflow.com). Como tantos otros libros disponibles en [GoalKicker](http://goalkicker.com) este es gratis, bajo licencia Creative Commons BY-SA y una de las cosas que debes leer si trabajas o estás interesado en aprender [Ruby On Rails](http://rubyonrails.org)

El libro cuenta con 72 capítulos (más bien pequeñas recetas) que cubren desde la instalación y arranque de un nuevo proyecto hasta el despliegue utilizando Docker. Si estás interesado puedes descargarlo[aquí](http://goalkicker.com/RubyOnRailsBook/)

También recomiendo que veas:

1. [Python Notes for Professionals](http://goalkicker.com/PythonBook/)
2. [Ruby Notes for Professionals](http://goalkicker.com/RubyBook/)
3. [Javascript Notes for Professionals](http://goalkicker.com/JavaScriptBook/)
4. [Linux Notes for Professionals](http://goalkicker.com/LinuxBook/)
A Peek into Github’s Learning Lab
Tags: softwaredevelopment, github, versioncontrol, opensource
Published: 2018-04-25 15:44:22

---
title: A Peek into Github’s Learning Lab
published: true
tags: software-development,github,version-control,open-source
canonical_url: https://medium.com/shecodeafrica/a-peek-into-githubs-learning-lab-c7422bf6aa7c
---

![](https://cdn-images-1.medium.com/max/1024/1*Z16CjNHE7dV_WVT82_GtbQ.png)<figcaption>lab.github.com</figcaption>

The team at Github recently pushed out an interactive guide to help developers master the art of using Git and getting more familiar to working around Github. Their goal is to **“_help new developers retain more information and ramp up quickly as they begin their software journeys”._**

The broad difference between the platform and every other tutorial or webcast that explores “Git and Github” is that it allows for **_User interaction_** ; where a bot walks you through series of fun practical labs giving feedback along the way all without having to leave the platform

### Here’s How It Works:

The following are treated as separate courses in the Lab:

1. **Introduction to GitHub** : Here an introduction to the most common, collaborative workflow for developers around the globe is done.
2. **Communicating using Markdown** : Users get to learn how to write documentations on GitHub and beyond with Markdown’s simple syntax.
3. **GitHub Pages** : Users are taught on how to host a website or blog directly from your GitHub repository.
4. **Moving your project to GitHub** : Get tips for migrating your code and contributors to GitHub.
5. **Managing merge conflicts** : Users get to learn why merge conflicts happen and how to fix them.

![](https://thepracticaldev.s3.amazonaws.com/i/rbad239klgw5ndjyiq01.gif)<figcaption>Sneak peek! Gif credit: Github Learning Lab</figcaption>

### **Getting Started**:

If you are totally new to Github, or looking to improve on your skills, this is a good shot, visit the learning lab [**here**](http://lab.github.com) 

- Upon start, a few account authorization steps are taken by the user to give Github learning lab install access to all of your repositories in your personal account (i.e automatically create a repository when starting a new course). You can choose to authorize access to all repositories, or grant it access to a single repository.
- When a new course is selected, permission is also requested from the user to install Github learning lab on the repository automatically created while registering for the course.The repository created is where you get to work with Learning Lab in issues and pull requests.
- Upon installation on selected repository, an automatic mail subscription is done hence commencing the series of tasks accompanied with the course.

Excited to try out Github Learning Lab or tried it out already? Let me know your thoughts on it!

* * *
One of the coolest parts about the web is being eroded
Tags: webdev
Published: 2018-04-25 14:42:02

---
title: One of the coolest parts about the web is being eroded
published: true
description: Even though most "work" still happens on desktop (debatable), clearly it's not the environment where most computer use takes place.
tags: webdev
---

Yesterday I made this tweet from [@ThePracticalDev](https://twitter.com/ThePracticalDev) Twitter account:

{% tweet 988846060029317120 %}

And then I left Twitter to get back to work. I'm not nearly as good about hanging around Twitter as I used to be—because I have better productivity habits. 😄

Anyway, some folks were confused by what I meant, or disagreed:

{% tweet 988847036114976768 %}

{% tweet 988848699395600385 %}

What I meant was not that our tools for inspection are getting worse. In fact, they are getting better, more powerful all the time. I love my Chrome web tools and Firefox et al are more than keeping pace. But that is generally more for desktop development. It's clearly harder to inspect the source of a page on mobile. It's such a pain in the ass if you don't already have a good setup that many devs probably have never bothered inspecting the source on mobile. Even though most "work" still happens on desktop (debatable), clearly it's not the environment where most computer use takes place.

It's all Steve Jobs' fault. I'm kidding—sort of. We know about his arguments with Woz about how many slots the Apple II should have had, and it never stopped. Apple has worked tirelessly to make their products—both hardware and software—into a black box. I'm all for a user-friendly shell, but it's absolutely a shame that getting under the hood is now for specialists and not for whoever wants to take a peek.

Others, like Google, have followed. Every new operating system seems to make inspecting the gears harder, and it's a shame. Is it _important_ that we maintain the ability for the average user to quickly dive into the source? Maybe, maybe not. I'd personally say yes and others would too, but either way it's a shame to lose this mindset. Code inspection feature that didn't _need_ to exist in browsers in the first place, but it became a standard thing and it's sad that it stopped being the norm across all devices.
Anybody know of a good "recommendation engine" API?
Tags: discuss, saas
Published: 2018-04-25 13:59:32

---
title: Anybody know of a good "recommendation engine" API?
published: true
description: 
tags: discuss, saas
---

We're in the process of improving the suggested articles/discussion around the site and I'm looking at implementation options.

The most appealing option I've found is [Recombee](https://www.recombee.com/), which seems well-designed and well-documented. We'll design this system so that we can swap this out for something else in the future, so I'm not itching to go after a lower-level API or library for the time-being. Recombee seems like a goldilox solution in terms of not being too low-level or high-level and the docs make sense.

But I'd love input if anyone has any thoughts on the matter.
Blazing Fast JAMstack E-Commerce w/ Hugo, Forestry & Netlify
Tags: javascript, webdev, showdev, go
Published: 2019-04-18 17:47:00

---
title: Blazing Fast JAMstack E-Commerce w/ Hugo, Forestry & Netlify
published: true
tags: javascript, webdev, showdev, go
canonical_url: https://snipcart.com/blog/hugo-tutorial-static-site-ecommerce
---

![Hugo Tutorial: How to Build & Host a (Very Fast) Static E-Commerce Site](https://snipcart.com/media/204274/hugo-ecommerce-tutorial.jpg)

Working in this field, I often have developer friends reach out to me with questions about e-commerce projects.

I was talking with one of them last week. He seemed a bit distressed:

“I have this client that is asking for the moon in terms of performance for his online store. I really don’t know how I can meet his expectations.”

I sat there and smiled back at him because I knew the answer to his problem right away.

Many factors will influence your [choice of stack](https://snipcart.com/blog/choose-best-static-site-generator) for e-commerce. But, when speed is the main one, look no further than Hugo.

This conversation inspired me **to dig up our old Hugo e-commerce demo and to give it a fresh twist**, so here I am.

Here’s what I’ll do in the tutorial below:

- Create a Hugo website
- Add e-commerce functionalities with Snipcart
- Pair the static site to a CMS (Forestry)
- Deploy on Netlify

First, let’s see what Hugo has been up to since our last visit.

Read the rest of this post [here](https://snipcart.com/blog/hugo-tutorial-static-site-ecommerce)
The JAMstack in 2020: Why (and How) to Get Started
Tags: javascript, webdev, showdev, programming
Published: 2019-01-16 20:19:31

---
title: The JAMstack in 2020: Why (and How) to Get Started
published: true
tags: javascript, webdev, showdev, programming
canonical_url: https://snipcart.com/blog/jamstack
---

![The JAMstack in 2020: Why (and How) to Get Started](https://snipcart.com/media/204771/jamstack.png)

When we first wrote this post, the [JAMstack](https://jamstack.org/) ecosystem was still in its infancy.

That was +/- 5 years ago.

Back then, the [Netlify](https://www.netlify.com/) founders came to us with a proposition. They had just come up with the term “JAMstack” to work around the negative connotation of “static web” and were asking if we would help to promote it.

“Yeah, sure” answered a very half-convinced, greener Snipcart team.

![jamstack? sure](https://media.giphy.com/media/DfdbTJZx6Yjra/giphy.gif)

Boy, are we grateful today to have witnessed firsthand the rise of this now vibrant community.
It’s fair to say that we’ve played our part in this movement—crafting nearly fifty JAMstack-related [blog posts](https://snipcart.com/blog/categories/jamstack) & [Github repositories](https://github.com/snipcart) with actionable, live demos.

The difference today is that this kind of content pops up everywhere! And don’t get me wrong, we’re all for it. It means the community is in good shape and growing stronger every year.

We plan to keep up providing [valuable resources](https://snipcart.com/jamstack-ecommerce-podcast) to new & seasoned JAMstack developers alike in 2020. It starts today with this update to our introduction post and what we think the year ahead has in store for devs.

I’ll cover:

1. What the JAMstack is
2. How to get started with it
3. How to sell the JAMstack to clients
4. What are the best resources to stay up-to-date
5. What the Snipcart team is expecting from the JAMstack in 2020

Ready to JAM?

## 1. What is the JAMstack?

### 1.1 Definitions

The JAMstack isn’t a specific set of tools, but a new, modern way of building websites & apps. Where does “J-A-M” come from, you may ask? From these three core concepts:

[**JavaScript**](https://snipcart.com/blog/why-javascript-benefits): Any dynamic programming during the request/response cycle is handled by JavaScript, running entirely on the client.

**APIs**: All server-side functions or database actions are abstracted into reusable APIs, accessed over HTTPS with JS. Be it SaaS, third-party services or custom-built.

**Markup**: Templated markup should be prebuilt at build time, usually using a site generator for content sites, or a build tool for web apps.

Great. But what does it all mean in practice?

Read the rest of this post [here](https://snipcart.com/blog/jamstack)