teleren/devto huggingface dataset:
Nevertheless, Judith Coded
Tags: wecoded
Published: 2019-03-07 21:49:19

---
title: Nevertheless, Judith Coded 
published: true
tags: shecoded
---

## I've been a software engineer for 10 years

## You would recognize my work if you have done online learning 

## I advocate for women in tech and believe that TOGETHER WE RISE

So I read my post from last year and thought to myself, "yeah, I still feel exactly like that". I'll give you the gist of it:

* It's a mission - pay it forward
* Be Assertive Not Aggressive
* Help Other Women
* Advice (to everyone) Mentor, provide resources and communicate

## It's a mission - pay it forward
Womanup and give your time to other women. We know us best. Reach out to the new girls and give up your secrets. If someone had done that for me 10 years ago it would have saved me a lot of time and frustration. And who knows, maybe you'll make a friend along the way.

## Be Assertive Not Aggressive
You will get taken advantage of by way of things you don't know. Learn to ask questions. Don't be intimidated if you have to say, "I don't know." You don't know - until you know. And remember, YOU ARE NOT AN IMPOSTER! The Lord got you to this place and she doesn't make mistakes.

## Help Other Women
My philosophy is to focus on creating an environment of sisterhood that uplifts other women coders. I don't focus on the issues of how to change the patriarchal attitude that exists in some tech environments but how to change what I do to help other women succeed. You will never be part of "the brotherhood" so jump on in and join "the systerhood". 

## Mentor, provide resources and communicate
If you've read everything above, I don't have to explain this. It is so important I had to say one more time just in a different way.

There is so much more I could tell you: how I'm the senior member of an otherwise all male team; how I've been fired more than a handful of times for fighting back for myself and other women in tech; how I chose UI/UX development because the web should be for everyone - young, old, those with challenges, people with more, people with less. 

## **I will leave you with what I often tell my children:**

*You are a child of the universe,
no less than the trees and the stars;
you have a right to be here.
And whether or not it is clear to you,
no doubt the universe is unfolding as it should.*
**that is from the desiderata by Max Ehrmann**
SignalR core python client (IV): Improving syntax
Tags: core, python, syntax, signalr
Published: 2019-03-07 20:14:33

---
title: SignalR core python client (IV): Improving syntax
published: true
description: Dealing with syntax
tags: core, python, syntax, signalr
series: SignalR core python client
cover_image: https://www.campusmvp.es/recursos/image.axd?picture=banner-asp-net-core-750x300.png
---

As Loongle (github user) suggested into this [issue](https://github.com/mandrewcito/signalrcore/issues/2) placed on github. Library syntax should migrate to an approach similar to javascript.

```typescript
    this.hubConnection = new signalR.HubConnectionBuilder()
      .withUrl('http://localhost:55563/imessage/chart', {
        accessTokenFactory: () => this.tokenService.get().token
      }).build();

```

```python
hub_connection = HubConnectionBuilder()
    .with_url(server_url, {
        "access_token_factory": lambda : tokenfactory().token
        })
    .build()
```

Library examples obviously will change, and it will look like :

### Chat

```python
hub_connection = HubConnectionBuilder().with_url(server_url).build()
hub_connection.on("ReceiveMessage", print)
hub_connection.start()
```
### Chat with auth

```python
hub_connection = HubConnectionBuilder()\
    .with_url(server_url, {
        "access_token_factory": lambda: signalr_core_example_login(login_url, username, password)
    })\
    .build()

hub_connection.on("ReceiveSystemMessage", print)
hub_connection.on("ReceiveChatMessage", print)
hub_connection.on("ReceiveDirectMessage", print)
hub_connection.start()
```
### Streamming


```python
hub_connection = HubConnectionBuilder().with_url(server_url).build()
hub_connection.start()
time.sleep(10)
hub_connection.stream(
    "Counter",
    [10, 500]).subscribe({
        "next": lambda x: print("next callback: ", x),
        "complete": lambda x: bye(False, x),
        "error": lambda x: bye(True, x)
    })

```

I will include this changes and the catch block soon (Im open to any suggest). Im doing this change before message pack, It´s a tiny change i prefer doing this changes now because changes in basic syntax too late are a pain.

The sense of this post its a question. What kind of syntax do you prefer?. Placing this on the next´s version library .. Its a good decision in next migration? Changes probably will come this weekend  so post below if you think that im not on the right way (: 

## ToDo 
* message pack

## Links
[Github](https://github.com/mandrewcito/signalrcore)
[Pypi](https://pypi.org/project/signalrcore/)

Thank you for reading, and write any thought below :D
Battlesim: Using the PWA Starter Kit
Published: 2019-03-07 20:09:21

---
title: Battlesim: Using the PWA Starter Kit
published: true
description: 
tags: 
cover_image: https://thepracticaldev.s3.amazonaws.com/i/qezerl9ogqefepdacnra.jpg
---

I recently created an app called [Battlesim](https://battlesim.alexlockhart.me/). This app is used to play a table top miniatures game that simulates historical warfare. I created this app using the [PWA Starter Kit](https://pwa-starter-kit.polymer-project.org/) which is essentially a project archetype for creating progressive web apps. It uses Service Workers and web manifests to turn a normal website into an app that can be used offline and installed to your device.

This starter kit is very helpful in bootstrapping a near-vanilla web project. This method of creating a progressive web app allows you to have complex features and dynamic content and serve the app as a statically hosted site. No complex server side application or hosting infrastructure. Just HTML, CSS, and JavaScript statically delivered, using the modern features of the web platform to provide powerful user experiences.

My strategy for developing this app was to first utilize the web platform to create an offline first experience. In this example all user created content get's stored in the browser storage. The user can be offline, come to the site, interact with the various features and create their own content, all without any interaction with the server. After the initial installation of the service worker it never interacts with the server again other than to receive code updates.

The next step in my strategy was to enhance the experience by providing a sharing feature where I use Firestore to share data between users. References to this shared data are stored on the users device and the data itself is stored in Firestore so that other users can access the same data. This means that multiple users can join the same battle and have a shared user experience.

I am slowly evolving my own conceptualization of web development towards installable, offline first experiences as the primary targeted experience. The PWA Starter Kit seems to be forging a path in this direction.

Check out [my blog](https://www.alexlockhart.me/) for more of my musings upon technology and various other topics.
Wobbly - a simple animation library for iOS 
Tags: ios, swift, iosanimation
Published: 2019-03-07 19:51:22

---
title: Wobbly - a simple animation library for iOS 
published: true
description: 
tags: ios,swift,ios animation
---

This is an easy to use animation library for iOS with so many predefined animations just like animate css
https://github.com/sagaya/Wobbly
twitter-replies-parser - A Tool for Converting Twitter Replies into JSON
Tags: javascript, node, twitter, opensource
Published: 2019-03-07 19:24:59

---
title: twitter-replies-parser - A Tool for Converting Twitter Replies into JSON
published: true
description: A brief intro to a nifty little tool for parsing Twitter replies into JSON
tags: javascript, node, twitter, opensource
---

Some of my teammates and I recently asked Node.js folks on Twitter what tools they used and why the liked them. We're collecting this so we can help our product teams at Microsoft create better [Node.js tools for Azure](https://docs.microsoft.com/en-us/javascript/azure/?view=azure-node-latest&wt.mc_id=devto-blog-brhugh) that serve you, the community. Turns out, lots of folks have a lot of great opinions and feedback on this subject. This is great!

What's not so great is that we had so many replies we couldn't just copy-paste them from the web client 😱. So what to do? Write some JavaScript, of course!

It was a little easier said than done though. As it turns out, Twitter doesn't have any APIs available to get the replies to a tweet. Instead, I had to use the search API and then create the reply tree by hand. With a little coding work and a handful of recursive calls, I got it all working to a high degree of accuracy. Due to the approach used, it's not 100% accurate. I noticed about 2-3 tweets were missing out of the ~60 replies to [my request for feedback](https://twitter.com/nebrius/status/1102630156718370816), but close enough!

This tool is a Node.js application that spins up a web server with a simple web app for entering the URL of the tweet you want to get the replies to. It's definitely not pretty, but get's the job done:

![Screenshot of the web UI for Twitter Replies Parser](https://thepracticaldev.s3.amazonaws.com/i/e7ktanuu8o88ddl390wh.jpg)

You can check out the tool on [GitHub](https://github.com/nebrius/twitter-replies-parser), which is released under the MIT open source license. I'd love to hear what you think, and if you run into any issues using it.
Nevertheless, Ceri-anne Coded
Tags: wecoded, career, womenintech
Published: 2019-03-07 19:12:48

---
title: Nevertheless, Ceri-anne Coded 
published: true
tags: shecoded, career, womenintech
---

## I began to code because...

I wanted to change career and I love maths, problem solving and tech. I started learning to code in January 2016 teaching myself Ruby and then did a 14 week evening course learning HTML, CSS, JavaScript, PHP and SQL. I began my first role as a junior developer in November 2016 and now code in Swift/iOS.

## I’m excited about..

Contributing to the Dev.to app. I was nervous about contributing to open source for the first time but have loved getting involved!

## I want to brag about...

Successfully changing career at 37 years old and learning a whole load of new things when I had thought I was too old. It was scary starting again but it was totally worth it!

My advice for allies to support women who code is...

Listen to them, mentor them and sponsor them! :)
React and Rails with Webpacker in Production
Tags: discuss, beginners
Published: 2019-03-07 19:09:45

---
title: 'React and Rails with Webpacker in Production'
published: true
description: All I was looking for was a walk-through react input form and what I got was an entire project tossed into the trash. 
tags: discuss, beginner
---

I have written a hand full of Rails applications and typically I use the asset pipeline and coffeescript with bootstrap and the likes when deploying. Most of the projects are somewhat barebones from a front end perspective, but that's not to say they aren't functional from the server side. I don't usually have a hard time moving projects from development to production, most of the work ends up being trivial configuration details. 

For my most recent rails project, I was looking to add a react form walk-through on sign up. I found a few ruby gems that worked with react and I decided to pick out [reactjs/react-rails](https://github.com/reactjs/react-rails). I had no problem getting the development environment up and running, but when I tried to move the project into a test environment and then production, webpacker was giving me a time and a half. I ended up scrapping the project and moving forward to something new.

Anyone have similar experiences with dumping side projects? How much work do you usually put into a problem before cutting the cord and moving forward?
Me, Finally
Tags: wecoded
Published: 2019-03-07 19:00:26

---
title: Me, Finally 
published: true
tags: shecoded
---

## I started learning to code in 2017

Because my heart told me to :) Seriously.

Resigning from my education career after 13-years as an art and design teacher, I decided to to focus on myself, despite the risks. 

Fingers crossed, my career as a web developer is just around the corner. With luck I'll flourish, ideally in a creative environment, while also finding the time to work on my own projects, both technically and artistically.
Does your company have an awesome internal wiki? What makes it 'awesome'?
Tags: discuss
Published: 2019-03-07 18:58:51

---
title: Does your company have an awesome internal wiki? What makes it 'awesome'?
published: true
tags: discuss
---

At StackCommerce, we currently host our internal private wiki with [Github Wikis](https://help.github.com/en/articles/about-wikis), and I've been trying to find a good way to organize it in a way that visually makes sense, i.e. how to utilize sidebar content and page content effectively.

I've tried looking for more discussions around wiki structure for inspiration outside of the world of open source (which doesn't quite fit our needs currently) and I haven't had much luck.

Right now, we have a few main sections such as 'Documentation', 'Engineering', 'How-To', 'QA' and 'Product Specifications', but not every sub-section is organized accordingly.

TL;DR--Do you use a wiki at your company and do you find that it's organized well? What makes it work for your team?

Any tips would be appreciated!
Nevertheless, Mary Codes
Tags: wecoded
Published: 2019-03-07 17:04:39

---
title: Nevertheless, Mary Codes
published: true
tags: shecoded
---

## I started/continued to code in 2019 because...
It was what I was supposed to do. I can tell in the way that I hunger for it. Teeth gnash through documentation. Eyes spiral in delight at the abolishment of bugs. I hunt for mentors and feast on the knowledge wrought. I was supposed to be a developer all along. The mania within me renders.

## I deserve credit for...
My appetite for asking questions —good questions. I can go down any rabbit hole and pull out a rabbit triumphant. I will go there, I will learn more, and I will conquer.

## I hope to see my school/work/developer/tech community...
Choose passion over pay. Integrity over celebrity, and the fascination with becoming a hero and helping fellow man. The society that clambers atop one another for recognition and rewards over logic and better planning should be the nightmares of yesterday. I can see it coming.
Nevertheless, Aurelia Specker Coded
Tags: wecoded
Published: 2019-03-07 18:31:37

---
title: Nevertheless, Aurelia Specker Coded 
published: true
tags: shecoded
---

## I started to code because...

I didn't find my previous job challenging enough. I wanted to get a job where I could constantly learn new skills and push myself to achieve new goals. 

Coding is challenging - there are so many things to learn and, when you eventually do learn them, they change again (for example, libraries and languages get updated all the time). But coding is also extremely empowering and rewarding. There are so many resources available out there and you can learn to build pretty much anything if you put in the right amount of effort and time. And that addictive feeling when you finally get something to work... priceless!

A year after I started coding, I got a job as a Partner Engineer. I love that my job stretches me and enables me to learn new things every day!


## I'm currently working on...

Several things... In January, I committed to the [#100DaysOfCode challenge](https://twitter.com/AureliaSpecker/status/1077196955514818560). The idea is that for 100 days, you code for at least one hour a day. I've recently hit the halfway mark and I've already learnt so many things. Initially, I was worried that I wouldn't have the right inspiration to keep this going for 100 days, but I'm actually finding that I want to do too many things and don't have enough time. 

I've started my own little projects (such as building an app that tracks Tweet engagement with the Twitter API) and I've taken online courses (for example a Udemy course on using Node.js). 

I've also been code pairing with some more experienced developers and have learnt a huge amount from coding with them.

I am also co-teaching the Code First: Girls Python course in London. It's a challenge at times, because explaining something requires of you that you really understand it (and I'm still relatively new to Python myself!). But it's also incredibly fun and so gratifying to inspire other girls to get into coding.

## My advice for others who are learning to code...

* **Get involved in the community of developers**. First of all, it's fun and you'll meet some like-minded people that will help you stay motivated during times of self-doubt. You will also learn a lot faster, by talking to other developers about their own experiences. Being part of the community will also bring up new opportunities: finding a new mentor, hearing about a job opening, etc.


* **Code on a regular basis**. We all have busy lives and, sometimes, it can be hard to continue learning when you're coding as a 'hobby on the side'. Make the time. Even if it's one hour every few days, make it a priority. The result is very fulfilling.


* Finally, **don't be too harsh on yourself**. It's really easy to get imposter syndrome, especially when you're surrounded by coders who know so much more than you do. There will be ups and there will be downs. Take things one baby step at a time and never give up - it's worth it & you can *totally* do it!
How to Cherry Pick Commits into a New Branch
Published: 2019-03-07 18:00:37

---
title: How to Cherry Pick Commits into a New Branch
published: true
description: 
tags: 
---

Have you ever found yourself in a situation where you needed to cherry pick a bunch of your own commits into a new branch in git?  I personally don't like to use `git cherry-pick` since it's usually a sign that something went wrong, but unfortunately  sometimes it's the only way out of a sticky git situation.  This happened to me recently at work and these were the steps I took to recreate my branch.       

**Step 1**
----------
First I needed to search the list of commits to find the ones that were relevant to me:    
`git log --pretty=format:"%h%x09%an%x09%s" | grep "Liz Lam"`

Woah!? What did you just type you ask?!!??!  Let's look at it in detail.    

`git log` gives you a list of commits in a repository.    
`--pretty=format:` allows you to format the commits in a way that makes sense to you (or in this case, me).    
`%h` prints SHA1 hash (short version) .   
`%x09` prints a tab.         
`%an` prints the author name.        
`%s` prints the summary of the commit.        
    
So put it altogether and `git log --pretty=format:"%h%x09%an%x09%s"` will output something like this:    
```
02705d38d4    Fabien Villepinte    l10n: fr.po Fix some typos from round3    
5a05494049    Fabien Villepinte    l10n: fr.po Fix some typos
ca1b411648    Johannes Schindelin   mingw: safe-guard a bit more against getenv` 
```
I then pipe that into `grep "Liz Lam"` to only get commits by me.
  
**Step 2**
----------
Once I have a list of commits by me, I'll inspect and manually pick the ones I'm interested in.  Let's pretend I came up with a list like this:    

`ff92f85cac`
`c8879ed156`
`b01cb9a3f9`

I then create a new branch and cherry pick the list of SHA1 commits:    
`git checkout -b my_new_branch`  
`git cherry-pick ff92f85cac` 
`git cherry-pick c8879ed156` 
`git cherry-pick b01cb9a3f9` 

Voila! Now I have a newly created branch with my freshly picked commits.
Nevertheless, Rachel Coded
Tags: wecoded
Published: 2019-03-07 16:53:24

---
title: Nevertheless, Rachel Coded
published: true
description: 
tags: #shecoded
---


#I began/continue to code because...

I started coding later in life. After a few years spent teaching in a secondary school in London, I knew I wanted a new challenge. My main teaching subject was Geography, but alongside this, I also taught Graphic Design. Enjoying the design element of the subject, I looked for career paths which would allow me to be creative and make things with real utility. It was this line of thinking that lead me to purchase an intro to HTML and CSS textbook.

Living in London, I was lucky enough to have access to many tech meetups, and Shoreditch’s growing startup scene. Whilst attending one of these meetups, I met Dan from [Founders and Coders](https://www.foundersandcoders.com), who suggested I should apply for their coding boot camp. It was here that I really got into coding. Covering the basics of HTML, CSS, frontend JavaScript, Node.js and Git, in quick succession, it was an intense learning curve, but an addictive one. I found learning how the web works and producing web applications really rewarding. 

After completing the boot camp, I started my first job as a React developer in an Ad Tech company. Following this, I worked as a JavaScript developer for a startup called Yoti. Currently, I am working full time as tech evangelist at Lightcurve, a blockchain development studio.  As a tech evangelist, my role is to build a community of developers for Lisk, a blockchain application platform. For me, the position is ideal – I get to combine my interests in tech and design, while at the same time learning a lot about blockchain and community building. I continue to code in my spare time. I guess old habits die hard, I will always be a nerd who likes to build things!

#I recently overcame...
Over the last year, I have definitely made progress in overcoming my fear of public speaking. Since joining Lightcurve in July 2018, I have represented Lisk at a variety of meetups and conferences, as well as speaking on podcasts and vlogs about the network. Although I can still get nervous, I also really enjoy it as well. Hearing or watching myself back is still a bit cringe, but I am learning to let go of this, slowly!

#I want to brag about...
Switching roles and adopting new marketing and community-building skills, whilst at the same time learning about the complexities of blockchain technology.

#My advice for allies to support women and non-binary folks who code is....
Ask for their opinions and seek their advice. Making people feel valued and useful goes a long way to help overcome imposter syndrome. Be mindful of the different paths people may have taken into tech.  If they aren’t aware of certain aspects of development, it doesn't mean they are stupid, just that they might not have been coding when this was prominent. Most importantly be kind and value the insight that underrepresented groups bring.
React-Native Https request to Server failed
Tags: reactnativeandroid
Published: 2019-03-07 17:34:59

---
title: React-Native Https request to Server failed
published: true
description: When I sent a http request to a resource/API on my corporate server it gets response but when I try to fetch the same API using https request it shows Network request failed as error while fetching from react-native android using android studio emulator
tags: React-Native Android
---