teleren/devto huggingface dataset:
The Calm Before the Conf
Tags: learning, ruby, rubyconf2018, rubyconf
Published: 2018-11-13 01:08:24

---
title: The Calm Before the Conf
published: true
tags: Learning,Ruby,rubyconf2018,rubyconf
canonical_url: http://christine-seeman.com/2018/11/the-calm-before-the-conf/
---

![](https://media.giphy.com/media/r0yVLlbnQ5i5a/giphy.gif)

I’m attending my first RubyConf tomorrow in L.A. This really is my first technical conference that I have ever attended. It is awesome that my employee is putting the time and money into growing me, and I really hope that I can use this as a learning experience, as well as growing my knowledge about the Ruby community. I was a Java engineer for 12 years, and maybe attended 1 or 2 meetups, for me there wasn’t that much community there, also I was encouraged to learn more but none of my employers ever sent me to a conference. In the 5 months that I have been a Ruby engineer, I have been encouraged so much more to reach out, and get connected. 

I did write some goals for the conference, and for me what I am going to try and take out of this is:

1. Learn more about Ruby data structures.
2. Attend a talk on Ruby design patterns
3. Find an open source project to contribute to
4. Learn more about Ruby testing philosophies and frameworks

With my own Ruby learning, I have started up [Flawless Ruby](https://avdi.codes/downloads/flawless-ruby-course/) offered Avid of Grimm of Ruby Tapas (which I am also planning on checking out). Wrapped up [Practical Object-Oriented Design](https://www.poodr.com/) by Sandi Metz, which has kicked off my wanting to bone up further on Ruby design patterns. Also I am continuing on [Learn Ruby the Hard Way](https://learnrubythehardway.org/), but feel kind of stalled in it. It is almost too basic for someone who comes from a development background. I like how he is trying to use route learning, to get you to really remember the code and lessons, but the pacing is pretty slow. Right now next on my reading list is [The Ruby Way](https://www.amazon.com/Ruby-Way-Programming-Addison-Wesley-Professional/dp/0321714636). I plan on digging into some Rails learning next, but I wanted to have my Ruby foundation solid first before diving into something else. Then after rails, I know my front end skill are in sore need of some help. I think I might just go with some basic JavaScript skill first and then maybe some Vue.  Any suggestions for where to start for increasing your front end knowledge when for back-end engineers?
Static Site Generators for Documentation
Tags: staticsites, documentation
Published: 2019-03-02 18:26:47

---
title: Static Site Generators for Documentation
published: true
tags: staticsites, documentation
canonical_url: https://www.kahlillechelt.com/2018/11/13/static-site-generators-for-documentation/
---

We are using some internal libraries at work that are not very well documented. As a result it is really difficult and time-intensive to onboard onto the project. It became clear to me that not having good documentation can come at a very high cost when it comes to long-term productivity for a team with changing team members.

As a result I started to work on documenting the inner workings of our application and it does feel satisfying to bring it to paper.

With documentation on my mind I attended our local JavaScript meetup [KarlsruheJS](http://karlsruhejs.org/), which I also co-organize. Interestingly it featured a talk about [VuePress](https://vuepress.vuejs.org/) a static site generator based on VueJS which is specifically tailored towards creating documentation. I was smitten instantly!

[After tweeting about my excitement](https://twitter.com/kahliltweets/status/1057937401191059456) about VuePress KarlsruheJS member Carsten [directed my attention towards Docusaurus by Facebook](https://twitter.com/Jupiterrrr/status/1058267113138409472), which is (obviously) a React-based static site generator for documentation. And since [my co-worker Emma is totally into Gatsby](https://twitter.com/EmmaWedekind/status/1051767104108732416) I took a closer look there too and also found a Gatsby theme for documentation as well.

My docs are not ready to be hosted yet but it is good to know that there are some solid ways to get a documentation site up quickly. Since our project is written in React I will not go with a Vue-based solution though. It will be either Docusaurus or Gatsby.
Write a script to find "Perfect Numbers"
Tags: challenge
Published: 2018-11-13 00:41:32

---
title: Write a script to find "Perfect Numbers"
published: true
tags: challenge
---

Inspired by [this tweet](https://twitter.com/fermatslibrary/status/1045294993747976192):
{% tweet 1045294993747976192 %}

Write a script to find "Perfect Numbers."  Here's the list of numbers up to 19 digits 😈:

> 6, 28, 496, 8138, 33550336, 8589869056, 137438691328, 2305843008139952128

Look forward to seeing everyone's solutions!
Keyboard Curiosity
Tags: mechanicalkeyboards, discuss
Published: 2018-11-13 00:22:55

---
title: Keyboard Curiosity
published: true
description: What keyboard do you use when programming?
tags: mechanicalkeyboards, discuss
cover_image: https://thepracticaldev.s3.amazonaws.com/i/g0jfuj0skp5lpspj6qpi.jpg
---

What types of keyboard is your "daily driver"?
Do you use a mechanical keyboard? Built-in laptop keyboard?
Do you use different keyboards for work/personal use?

Personally, I use a [Vortex 75 Race 3](http://www.vortexgear.tw/vortex2_2.asp?kind=47&kind2=225&kind3=&kind4=1042) (pictured above). I like how compact and portable it is and am a big fan of the Cherry MX Clear switches. 

At home, I am hacking on a PCB from [OLKB](https://olkb.com/) called the [Planck](https://olkb.com/planck/pcb). I had to buy all of the switches/caps/case separately but it was a fun project and ortholinear keyboards are fun to learn.

Would love to see what the community uses!
Special Feed for Dev.to
Tags: jekyll, webdev
Published: 2018-11-05 02:53:29

---
title: Special Feed for Dev.to
published: true
tags: jekyll, webdev
series: November Daily
canonical_url: https://www.anonjr.com/2018/11/Special-Feed-for-Dev.to.html
---

Back in January 2017 I started following what looked like a small and promising community of programmers (and those in adjacent fields) over at [Dev.to](https://dev.to/). At the time I had the site's whole feed pumping into my Feedly list, I'd commented on a few posts, and I was starting to think about either revitalizing this blog or picking some other platform for posting.

In the end I decided to try and revitalize this site, beginning with [a bit on the tech](https://www.anonjr.com/2017/07/A-Pretzel-A-Jekyll-Some-Pages-Cranky-Git.html) behind a couple of projects.

One of the things I'd considered at the time, and mentioned in [Projects Projects Projects](https://www.anonjr.com/2018/11/Projects-Projects-Projects.html), is setting up a custom RSS feed for just the articles I wanted to submit at Dev.To. I plan on publishing a wide variety of articles here, and I know not all of them will be right for the community there, so I want to make sure I'm filtering out the rest. I tried just running my regular RSS feed to my profile there, but it left a lot of cruft on my dashboard in the _drafts_, and even if I deleted the drafts they would just show up again on the next refresh.

Which brings us to this bit - I've got a second RSS feed now with just the articles that I want to send over there.

In the front matter I have a `repost` variable like so:

![(side note: need to fix the highlighting/rendering of markdown code in posts...)](https://www.anonjr.com/img/2018-11-04-frontmatter.png "(side note: need to fix the highlighting/rendering of markdown code in posts...)")<figcaption>
(side note: need to fix the highlighting/rendering of markdown code in posts...)
</figcaption>

Originally I was going to set up a "to-dev.to" tag, and go that way, but that didn't seem useful for the people who were visiting my site.

And there's now a `todev.to.xml` that filters through the posts for just those that I want to republish.

![](https://www.anonjr.com/img/2018-11-04-devtoxml.png)<figcaption>
</figcaption>

At my next opportunity, I'm going to try and pump it through the [Compress layout](https://github.com/penibelst/jekyll-compress-html) and see if that can get the size down without breaking anything. Though now that I think about it, I'd have to either adapt it to work with [Pretzel](https://github.com/Code52/pretzel) or do the Pretzel-to-Jekyll conversion first.

So there's the short version. I'm sure there's a more efficient way to do this, but I probably won't worry too much about it until I do the conversion to Jekyll. I don't plan on adding any more features before then.

(Hot damn! that makes 4 for 4 on my "[Almost NaNoWriMo](https://www.anonjr.com/2018/11/Almost-NaNoWriMo.html)"!)
Forçar Redirect de HTTP para HTTPS
Tags: apache, serverhosting, ssl, website
Published: 2021-04-14 12:15:39

---
title: Forçar Redirect de HTTP para HTTPS
published: true
date: 2018-11-12 21:13:48 UTC
tags: apache,serverhosting,SSL,website
canonical_url: https://andersonbraz.com/forcar-redirect-de-http-para-https
---

Neste post eu mostro como resolver um inconveniente que ocorre em servidores de hospedagem da web que utilizam o Apache como suportação do serviço.

## Introdução

Hoje as pessoas são informadas em todas as mídias que: se um site não tiver um cadeado na côr verde, na barra de endereço do navegador/browser, este não é confiável. Daí você descobre junto ao seu provedor de hospedagem que para ter este cadeado você precisa obter um serviço de chave SSL.

Correto! Você adquire o serviço mas descobre que se um usuário leigo digitar o endereço de alguma url do seu site usando apenas "http://", mesmo com o serviço de SSL contratado, ele vai acabar na cilada de não visualizar o tal cadeado verde ao entrar na sua página.

## Como Resolver?

Criar uma condição para que todas as requisições HTTP sejam forçadas ou redirecionadas para HTTPS.

Parâmetro a ser incluído no arquivo .htaccess na raiz do seu domínio:

```
RewriteEngine On
RewriteCond %{HTTPS} off
RewriteRule (.*) https://%{SERVER_NAME}/$1 [R,L]

```

## Conclusão

Um detalhe de ajuste tão simples capaz de resolver aqui o que parecia um problemão. Seja Feliz!

\*\* ESTA SOLUÇÃO É APLICADA APENAS PARA WEBSERVER EM APACHE

## Créditos

Photo by [Markus Spiske](https://unsplash.com/@markusspiske?utm_source=unsplash&utm_medium=referral&utm_content=creditCopyText) on [Unsplash](https://unsplash.com/?utm_source=unsplash&utm_medium=referral&utm_content=creditCopyText)
Programming gives an equal chance to everybody
Tags: career, beginners, motivation, learning
Published: 2018-11-12 20:53:08

---
title: Programming gives an equal chance to everybody
published: true
description: Programming brings more equality to the world than you can imagine
tags: career, beginners, motivation, learning
cover_image: https://thepracticaldev.s3.amazonaws.com/i/otkxp3nx4jjr2tlvfg9j.jpg
---

>Programming brings more equality to the world than you can imagine.

###Starting point
Not everyone is born rich, not everyone is born in a rich country, not everyone has access to the goods we take for a grant, but there is one thing which does not depend on our precondition and environment, and this is curiosity. People of all nations, gender, colors, have some or no education, they all can be curious, can be intelligent, problem solvers. They all share something in common, and they have the potential to become IT engineers. Not all of them of course, do a study or show interest in the IT industry. Some people with a technical predisposition, never get into the tech jobs, some become another sort of engineers: electric, mechanical, etc. But currently, there is no higher demand for engineers, than for IT engineers. 
###Equal chance for everybody
Become an IT engineer was never easier! All sort of education material is available online you don't need to go into the [traditional education system](https://dev.to/damnjan/failing-it-education-12oi) to obtain it.  And guess what, **IT’S FREE!** You need some internet connection to obtain the amount of education material you won't be able to listen, watch and read for your entire life. You have to read it somewhere, and that’s your computer, tablet or phone, those devices never got cheaper as they are today, they are affordable to the wide range of the population. So you don't need to be born rich or having so many starting capital, you don’t have to put tons of money into the school system, you open a web page and learn. 
###No matter where you came from
Here is the point when you might better understand if you are coming from undeveloped countries than the folks from first world countries. **Being a software developer not just come with an equal chance for learning, but also for earning.** This brings a huge difference compared to the other professions. Software engineers can easily find a job, and they can work remote, which means they are competitive on the global market. If you’re competitive on the global market, your income does not depend on local standards and incomes. You become valued based on your skills, not based on your physical location. 

There is no job in this world, currently, which gives fairer chance regardless of our starting points.
How to change the theme in your Jekyll application
Tags: jekyll, programming, webdev, tutorial
Published: 2018-11-12 20:50:56

---
layout: post
title:  How to change the theme in your Jekyll application
description: "A step by step guide to changing theme in your Jekyll application."
tags: jekyll, programming, web development, tutorial
published: true
---

_Originally posted at https://endaphelan.me/technology/programming/changing-theme-in-jekyll-application_.

Follow these steps and you will be able to change the theme in your Jekyll application.

Create a new orphan branch and ensure it is empty.

```bash
git checkout --orphan newtheme
git rm -rf .
git clean -dfx
```

Now let's add the theme's repository as an upstream remote and pull the files into our branch. I am using Moon theme by [Taylan Tatlı](https://taylantatli.github.io/).

```bash
git remote add upstream https://github.com/TaylanTatli/Moon.git
git fetch upstream
git pull upstream master
```

Install Gem dependencies and run your application to see if the previous steps were successful.

```bash
bundle install
jekyll serve
```

All okay so far? Good. Now it's time to merge your blog posts, configuration and other custom files.

This will bring in your posts from `master`:
```bash
git checkout master -- _posts
```

You can safely merge these files and folders:

- `README.md` and other custom Markdown files.
- `_posts` directory.
- `_drafts` directory.
- `CNAME` file.
- Favicon files.
- Other custom files and directories such as pictures.

Some old files will conflict with ones from your new theme. The safest thing to do here is to copy the file to a new name and merge it manually.

```bash
git show master:_config.yml > _config.yml.old
```

Accidentally overwritten a theme file? No problem:

```bash
git checkout upstream/master -- index.md
```

I recommend manually merging these files:

- `_config.yml`
- `Gemfile`

Now replace `master` with the `newtheme` branch:

```bash
git checkout newtheme
git merge -s ours master --allow-unrelated-histories
git checkout master
git merge
```

Run the application again to see if your changes have come through:

```bash
jekyll serve
```

Push your changes:

```bash
git push
```

Leave no evidence of the crime by deleting the `newtheme` branch.

```
git branch -d newtheme
```

## Credits

This solution is adapted from Daniel Pelsmaekerwith's <a href="https://stackoverflow.com/a/37186333" target="_blank">answer</a> on StackOverflow to work with the latest versions of Git, Bundler and Jekyll.
Recommend a Dev.To-er!
Tags: bestofdev, discuss, meta
Published: 2018-11-12 20:29:21

# Who are your **must follows** on Dev.To?

## Make a recommendation! Or plug your own writing!

---

My "following" list is not nearly as long as I would like it to be. Bonus points if you can recommend people who primarily write about design, UX, the history of computing, or JVM languages!
Alternate to Nose for Newbie Tester
Tags: help, python, beginners
Published: 2018-11-12 20:17:51

---
title: Alternate to Nose for Newbie Tester
published: true
description: I'm looking for an alternative to Nose for testing as a newbie Pythonista
tags: help, python, beginner
cover_image: https://thepracticaldev.s3.amazonaws.com/i/kg5s2xpwu2jsz0vj8sfb.jpg
---

Aloha Y'all

I have recently started learning Python and I'm working my way through Learn Python the Hard Way. In the sections for testing, he shows you how to use Nose for testing and setting up your test environment. The problem is that it looks like Nose is no longer being supported. And, in a nutshell, I keep running into trouble as I'm using it.

Since it's an outdated tool, I thought it would be better if I learn testing with a tool that is up to date and popular.

**What simple alternatives to Nose do you like/use?** Extra points for keeping in mind I will be testing very simple projects. Thanks!
Game Off 2018 (5)
Tags: lua, gamedev, gameoff2018, pixelart
Published: 2018-11-12 20:04:51

---
title: Game Off 2018 (5)
published: true
description: Selector on the grid and planting mecanics
tags: lua, gamedev, gameoff2018, pixelart
---

Hey!
I have not posted some new devlog this week-end... because I've not work in the game! So let's back on dev!

Today I've add a little selector sqare to be sure on wich tile we select! I've also add the take seed mecanics and the plating seed mecanics! And a little HUD (I'm not sure on it so if you have some feedback, I'm open!)

So let's see that on a gif!


![World](https://thepracticaldev.s3.amazonaws.com/i/txuc56pcg3rsnvatbsj2.gif)

It's all for today!
Have a nice day!
Where to start refactoring.
Tags: discuss, rails, refactoring, help
Published: 2018-11-12 16:14:38

---
title: Where to start refactoring.
published: true
description: 
tags: discuss, rails, refactoring, help
---

One of the first apps I built for my company is still in use today and occasionally gets new features. It's both an awesome and terrifying feeling to know that something I built is active and used daily. I've learned a lot since I built that app and I've been able to fix and update a lot of the things I did "wrong" in the beginning.

However most of the "fixes" have been on a line or a query or just splitting a long method into 2. The code base itself needs a facelift and a reorganization. I can see the problems but I don't know where to start in terms of moving large blocks of code around. My test coverage is pretty good so I'm not worried about breaking things as much as I'm worried about doing it efficiently and in small enough chunks that if we get busy on other projects I can easily come back.

Anyone have any tips or stories about refactoring they would like to share?
Facebook.com is Down
Tags: facebook, devops
Published: 2018-11-12 18:04:05

---
title: Facebook.com is Down
published: true
description: Woah.
tags: facebook, devops
---

https://www.facebook.com/

![image](https://user-images.githubusercontent.com/5464072/48366301-684c5900-e67b-11e8-8903-c2c6d9c96e91.png)
Compromise and Test
Tags: agile, management
Published: 2019-08-19 17:24:37

---
title: Compromise and Test
description: What to do when a decision isn't obvious?  Try both and test the results.
published: true
tags: agile, management
canonical_url: https://kellen.piffner.com/2018/11/12/compromise-and-test/
---

<figure>
![Person gesturing at laptop](https://kellen.piffner.com/img/compromise-and-test/rawpixel-669602-unsplash.jpg "Let's argue about computer things")
<figcaption>
<cite>
<a href="https://unsplash.com/@rawpixel?utm_medium=referral&amp;utm_campaign=photographer-credit&amp;utm_content=creditBadge">Photo by rawpixel on Unsplash</a>
</cite>
</figcaption>
</figure>

In my [previous post](https://dev.to/gettingappsdone/the-choice-of-priorities-53kf) I talked about what to do when presented with a question of priorities. I argue that the answer is to do "both". But what about when those two priorities are mutually exclusive? "Do we make the button green or orange?" You can't really do both in this case, right?

When two people disagree on a choice like this, it often means there's a fundamental difference in understanding of the topic itself. Maybe they 'weigh' the priorities differently. In the example of "green" vs. "orange", maybe they're really arguing "positive" vs. "bright".

The first step in any disagreement is to get people talking it through. With luck, they can work it out just by sharing their own understandings of the subject. But fairly often the opinions will be strongly held, and difficult to change. So then what?

The answer is exactly the same as the question priorities: **Do them both.**

In this case, it's not a question of difficulty, but of cost. Doing them both costs twice as much, but often will lead to a better overall solution. This is the same idea behind [A/B testing](https://en.wikipedia.org/wiki/A/B_testing) where you put both options out there and let the data decide.

Even for simpler things, where 'common sense' dictates one is probably better than the other, data (or customer feedback) can often reveal completely different understandings.

And beyond ending up with a better solution, this is another way to get arguing team members to compromise and work together, which is almost always more valuable than getting a button color just right.