teleren/devto huggingface dataset:
3 - Agile - Career development and security.avi
Tags: agile, career, leadership, devops
Published: 2022-01-28 00:25:26

[Portuguese version](https://dev.to/caju/3-agile-desenvolvimento-e-seguranca-naavi-1d66)

Your jobs, even if you are self-employed, freelancer, entrepreneur, anyway... if you have a job, and the order in which you take them, they structure your career. In this framework, you will develop certain skills and values, both formally and informally.

The two aspects interact and it is important to know how to use both. What you learn determines the future jobs and roles that will be available to you. On the other hand, they affect their learning. Some people get into a dead end, developing skills that offer little or no growth. Others develop skills and accumulate experiences that are increasingly in demand, and career options expand. Any of these directions can come by luck or chance, but if you are aware of the processes you can manage them.

Therefore, there is almost no talk of "a job for life" anymore. In fact, we don't even talk about a single source of income anymore. Nowadays you are an employee, employer, investor, I mean, you can have several functions and that's okay. Just as a doctor can be a doctor, a lecturer, and a teacher at the same time. Why not? Instead of "job security", understand that the important thing is "career security". Employers and employees alike have recognized that both benefit from mobility.

It is in the company's interest to support your career. But we know clearly that it's hard to see that around. But it is important to note this. It is important for the company to provide the means to develop your career, it can profit financially in many activities. In return, it expects you to be productive while on the job.

If you are willing to learn, and the company provides you with the resources, you can manage your career with a mutually beneficial contract. It's like a wedding. Think about it!
3 - Agile - Desenvolvimento e segurança na carreira.avi
Tags: agile, career, leadership, devops
Published: 2022-01-28 00:18:55

[English version](https://dev.to/caju/3-agile-career-development-and-securityavi-443o)

Seus empregos, inclusive se você é autônomo, free-lancer, empresário, enfim... se você possui um ofício, e a ordem em que você os assume, estruturam sua carreira. Nessa estrutura, você irá desenvolver certas habilidades e valores, tanto formal quanto informalmente. 

Os dois aspectos interagem e é importante saber usar os dois. O que você aprende determina os futuros empregos e funções que lhe estarão disponíveis. Por outro lado, afetam sua aprendizaem. Algumas pessoas se metem em um beco sem saída, desenvolvendo habilidades que oferecem pouco ou nenhum crescimento. Outras desenvolvem habilidades e acumulam experiências cada vez mais demandadas, e as opções de carreira se ampliam. Qualquer desses rumos pode vir por sorte ou acaso, mas se você estiver consciente dos processos poderá gerenciá-los. 

Logo, quase não se fala mais em "um emprego para toda a vida". Inclusive, nem se fala mais em uma única fonte de renda mais. Hoje em dia você é empregado, empregador, investidor, ou seja, ter várias funções e tá tudo bem. Assim como um médico pode ser ao mesmo tempo médico, palestrante, professor. Por que não? Em lugar de "segurança no emprego", entenda que o importante é "segurança na carreira". Tanto empregadores quando funcionários já reconheceram que ambos saem ganhando com a mobilidade. 

É interesse da empresa apoiar sua carreira. Mas sabemos claramente que é difícil ver isso por aí. Mas é importante observar isso. É importante a empresa dar meios de desenvolver sua carreira, pode lucrar financeiramente em muitas atividades. Em troca, espera que você seja produtivo enquanto estiver no emprego. 

Se você estiver disposto a aprender, e a empresa proporcionar-lhe os recursos, você pode gerenciar sua carreira com um contrato reciprocamente vantajoso. É como um casamento. Pense nisso!
How I landed my first job as a software engineer
Tags: career, leadership
Published: 2022-01-29 14:02:59

---
title: How I landed my first job as a software engineer
published: true
date: 2022-01-28 00:00:00 UTC
tags: 
 - career
 - leadership
canonical_url: https://petermekhaeil.com/how-i-landed-my-first-job-as-a-software-engineer/
---

I was once an entry level developer with no experience, looking for my first door into an engineering career. I finished my studies back in 2009 and for almost a year I could not find a job. It almost felt like a blind journey from one interview to another, that all ended up in rejection because of lack of experience and knowledge. Without knowing where to look or without knowing what to research, I was mostly answering interview questions with answers that I thought was right, based on my limited knowledge in web development (my computer science studies did not include web dev subjects).

It was until my approach changed during an interview at what soon to become the first company that accepted me.

At the very start of the interview, without any thought behind it - I told the engineering manager something I’ve never said during my previous interviews: I said something along the lines of _“Before we continue, I want to tell you - I do not know anything. But I want to learn”_.

Everything changed from that moment. The manager continued the interview by listing their tech stack and asked if any of it sounds familiar, and my answer was no to all of them. Nevertheless, he did not mind because I showed my eagerness to learn. The interview turned into a crash course introduction to the technologies and soon after, I was accepted for the job.

Call out your area of focus so others are aware that you are know. Shawn calls this [the Power of Lampshading](https://www.swyx.io/lampshading/).

For entry level developers looking to land their first job as a software engineer, it is totally okay to call out your area of focus. Let the interviewers know that you do not know the answers and you are willing to learn. This is powerful in itself and calling out your focus areas will have an impact throughout your career.
Keep your workflow actions up to date using GitHub Dependabot
Tags: github, actions, dependabot
Published: 2022-01-30 10:14:28

---
title: Keep your workflow actions up to date using GitHub Dependabot
published: true
date: 2022-01-28 00:00:00 UTC
tags: github, actions, dependabot
canonical_url: https://www.visualstudiogeeks.com/github/ensure-your-actions-are-up-to-date
---

GitHub Actions is great in automating your workflows. However, as you start using various actions from GitHub Marketplace in your workflow, it will soon become necessary for you to keep the actions up-to-date. Actions might contain security fixes, bug fixes etc and manually keeping track of updates or updating them when a newer version is available is a lot of hassle. This is where we can use Depndabot can help is by automatically raising PR’s whenever there is a newer version of action is available used in the workflow. In this post, we will see quick way to keep the actions up-to-date using GitHub Dependabot.

<!-- more -->

> For this post, I am using my [Git Config User Profiles](https://github.com/onlyutkarsh/git-config-user-profiles) repository. I have workflow setup which builds and releases the VS Code extension to VS Marketplace.

## Create dependabot.yml file

To set up Dependabot scan, first got to `.github` folder in your root and create a `depndabot.yml` file. Then add the following content. This will ensure GitHub Dependabot raise a PR whenever there is a newer version of action is available

```yml
version: 2
updates:
  - package-ecosystem: "github-actions" # search for actions - there are other options available
    directory: "/" # search in .github/workflows under root `/`
    schedule:
      interval: "weekly" # check for action update every week

```

## Commit the file

Commit the file created above and wait for few seconds. Based on your workflow, you will see a bunch of PR’s raised.

![Dependabot PR](https://www.visualstudiogeeks.com/images/screenshots/utkarsh/2022/jan/dependabot-to-update-actions/dependabot-alerts.png)
_Dependabot Alerts as PR_

If you look at the PR, you will be able to see the change and take a decision whether you want to upgrade the specific action or not. If you decide to accept the change, merge the PR and the changes on the workflow file will be made.

![Commit Details](https://www.visualstudiogeeks.com/images/screenshots/utkarsh/2022/jan/dependabot-to-update-actions/commit-detail.png)
_Commit Details_

## Conclusion

Isn’t it cool? This saves a lot of time, if you have a number of workflows and don’t want to keep checking the latest versions of actions. BTW, not only GitHub actions, you can use same approach to update `npm`, `docker` and many more using various [package ecosystems](https://docs.github.com/en/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/about-dependabot-version-updates#supported-repositories-and-ecosystems). Do check it out!
Pick a methodology: Scrum, Kanban, XP, Lean or DevOps?
Tags: agile, scrum, devops, xp
Published: 2022-01-28 14:17:36

---
title: Pick a methodology: Scrum, Kanban, XP, Lean or DevOps?
published: true
date: 2022-01-28 00:00:00 UTC
tags: agile,scrum,devops,xp
canonical_url: https://jhall.io/archive/2022/01/28/pick-a-methodology-scrum-kanban-xp-lean-or-devops/
---

What’s the difference between Scrum, Kanban, XP (eXtreme Programming), Lean, and DevOps? How do you choose which one to use?

This is a common question I hear. Often asked just about two, but often the whole list. “Should my new team use Scrum or XP?” or “Which is better, kanban or lean?”

These questions come from a good place: Wanting to know how to taylor a tool/framework to a situation.

But as is often the case when you don’t know what you don’t know, asking an intelligent question is difficult.

The truth is, none of these items directly replaces or conflicts with any of the others. In fact, you can use them all simultaneously.

Here’s a super, over-simplified explanation of each, to point you in the right direction, if you’re considering which, if any of these, you should investigate further:

- [Scrum](https://en.wikipedia.org/wiki/Scrum_%28software_development%29) is about managing a team’s work
- [Kanban](https://en.wikipedia.org/wiki/Kanban_%28development%29) is about optimizing flow, or throughput
- [XP](https://en.wikipedia.org/wiki/Extreme_programming) is about the particulars of software creation
- [Lean](https://en.wikipedia.org/wiki/Lean_software_development) is about optimizing systems
- [DevOps](https://en.wikipedia.org/wiki/DevOps) is about promoting collaboration between developers, operations, and any other groups involved in product creation

* * *
_If you enjoyed this message, [subscribe](https://jhall.io/daily) to <u>The Daily Commit</u> to get future messages to your inbox._
100 Days of Learning - Days 16 and 17
Tags: 11ty, ssg
Published: 2022-01-27 23:33:48

---
series: 100 Days of Learning
---

Hello and welcome to my 100 Days of Learning challenge! Yesterday was a fun day, I started digging into Raymond Camden's guide on setting up a blog with 11ty (linked down below). 

It was going really well until I tried combining tips from other resources and made a mess of the project structure, which introduced a bunch of errors. I didn't even realize I had gone so far astray, and Raymond himself helped me figure out where I'd gone wrong. (Thanks, Raymond!!)

I ended out the day with the first chunk of the project working, with a list of posts and post excerpts. 

Today, I wrapped up the Eleventy guide including updating the site UI, added git, pushed my changes up to [Github](https://github.com/lfosgett/eleventyBlog) and [deployed to Netlify](https://keen-volhard-367b43.netlify.app/). Phew! I didn't end up implementing RSS in this starter project, but I think that would be worth exploring another time. I have a much better understanding of how Eleventy structures your files, and the refresher on git/Github/deploying to Netlify was much needed.

This has been a really fun project and I'm learning a lot!

Next I'll explore using a "one click deploy" themed Eleventy starter project and poking around that. If I like what I see and can figure out how to use it, then I might just use that to set up my personal blog. Otherwise, I'll start from scratch and redo my personal site to include the new blog. It might be worth updating my personal site anyway, if only for the practice.


**Here are some of the resources I'm using:**
- [A Complete Guide to Building a Blog with Eleventy](https://cfjedimaster.github.io/eleventy-blog-guide/guide.html)
- [11ty Tutorial: Cranking Your Jamstack Blog Up to 11!](https://snipcart.com/blog/11ty-tutorial) (I didn't realize this tutorial was also by Raymond!)
- [Raymond Camden's Blog](https://www.raymondcamden.com/2022/01/19/a-guide-to-building-a-blog-in-eleventy)
- [11ty Docs]()
- [Let's Learn Eleventy! | Learn with Jason](https://www.learnwithjason.dev/lets-learn-eleventy)

---
Photo by <a href="https://unsplash.com/@heykellybrito?utm_source=unsplash&utm_medium=referral&utm_content=creditCopyText">J. Kelly Brito</a> on <a href="https://unsplash.com/collections/xj3Y8-lHOXo/dev-blogs?utm_source=unsplash&utm_medium=referral&utm_content=creditCopyText">Unsplash</a>
January 27th, 2022: What did you learn this week?
Tags: weeklylearn, discuss, weeklyretro
Published: 2022-01-27 23:32:30

It's that time of the week again. So wonderful devs, what did you learn this week? It could be programming tips, career advice etc.

<center>

![Yoda wooping someone's butt](https://media.giphy.com/media/yDYAHbqe5DfyM/giphy.gif)
</center>

Feel free to comment with what you learnt and/or reference your TIL post to give it some more exposure.

{%tag todayilearned %}

<!--
And remember, if something you learnt was a big win for you, then you know where to drop it as well.👇👇🏻👇🏼👇🏽👇🏾👇🏿

{%link https://dev.to/devteam/what-was-your-win-last-week-4f0n %}

<center>

![Little kid making a fist as if to say "Yes!"](https://media.giphy.com/media/6brH8dM3zeMyA/giphy.gif)
</center>
-->
2 - Agile - Planning your career.txt
Tags: agile, career, leadership, devops
Published: 2022-01-27 23:18:29

[Portuguese version](https://dev.to/caju/2-agile-planejando-sua-carreiratxt-1kic)

Very important subject and you have to check and analyze the market, talk to more experienced people and so on. That' something that never stops. It is like a Trader who is always keeping an eye on the Platform. Planning your career is more than simply mapping the stages of your professional life. It's having control of your own destiny. For that, you need to understand the world of work and what you really want.

With that, you only have to win, as the benefits of career management bring health to your professional and personal life, allowing more control and balance between them. You become more aware of what you expect from work and more able to create the means to achieve it.


![Image description](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/iw8m5srwb7101h74m9ky.png)
2 - Agile - Planejando sua carreira.txt
Tags: agile, career, leadership, devops
Published: 2022-01-27 23:12:26

[English version](https://dev.to/caju/2-agile-planning-your-careertxt-3cbl)

Assunto muito importante e tem que parar mesmo para analisar mercado, conversar com pessoas mais experientes e por aí vai. Inclusive isso nunca para. É como um Trader que tá sempre de olho na Plataforma. Planejar sua carreira é mais do que simplesmente mapear os estágios de sua vida profissional. É ter controle de seu próprio destino. Para tanto, você precisa compreender bem o mundo trabalho e o que você de fato deseja. 

Com isso você só tem a ganhar, pois os benefícios da gestão da carreira traz saúde para sua vida profissional e pessoal, permitindo mais controle e equilíbrio entre elas. Você fica mais consciente do que espera do trabalho e mais capaz de criar os meios de alcançar isso.


![Image description](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/njq69bywhbqd47iygmyk.png)
macOS Android Studio Bumblebee  Device Manager won't open.
Published: 2022-01-27 23:02:57

Working on macOS, I Just Upgraded to Android Studio Bumblebee and quickly discovered that Device Manager won't open. I've managed to start emulators with the command line but that is very tedious. So far I Invalidated the cache, restored the layout, and removed the emulators' folder from the SDK folder, but nothing solved the problem yet. does anybody see a similar problem? does anybody have a possible solution?
Mixed emotions: Saying goodbye to a team member
Tags: devrel, leadership, management
Published: 2022-02-04 19:06:17

---
title: Mixed emotions: Saying goodbye to a team member
published: true
date: 2022-01-27 22:51:53 UTC
tags: DevRel,leadership,management
canonical_url: https://jasonstcyr.com/2022/01/27/mixed-emotions-saying-goodbye-to-a-team-member/
cover_image: https://theagilecoder.files.wordpress.com/2022/01/pexels-photo-709732.jpeg
---

*NOTE: This content was inspired by an earlier post of mine as a [thread on Twitter](https://twitter.com/StCyrThoughts/status/1473285861534015498). 

Something I’ve struggled with when leading a team is saying goodbye. Such a mix of emotions! When somebody gets that next step in their career, it’s so great to see that success! At the same time you are told as a manager: “People don’t leave companies, people leave managers”.

So here you are, super happy for somebody and hoping that something you did helped them achieve this… while also thinking “Did I do something wrong? Was it me?” Like, seriously, Brain, calm down and pick a lane.

It’s easier to think about it with some time removed from the situation (like I am now). Still, no matter what answers you actually get from a person, no matter how direct the feedback, that little voice inside of you doesn’t stop nagging: “YOU MUST BE VERY BAD AT THIS YOU SHOULD STOP!”

Just me? Cool. Cool cool cool.

It conflicts with the mindset I want. I believe my role is not necessarily to keep the same crew together, but instead to give room for the individual to grow out of the team. I’m trying to learn from Pieter Brinkman (@pieterbrink123 ) who created a great space for us with room for creativity, experimentation, and career growth. We should all have that.

In my opinion, a manager’s role is to provide the opportunity for a team member to build out the skills needed for the job after this one. Hopefully, that type of environment for continuous learning and growth means that the current job they have **IS** the next job for them. And if I’m lucky, that means they’ll stay to grow more.

Not sure what exactly got me goin down this rabbit hole.

Maybe it’s this whole “Great Resignation” thing going on that has me on this, but I guess the summary is this:

1. Treat your team well.
2. Don’t be too hard on yourself.
3. Yes, your brain will still say you suck.
4. People can sometimes be pretty great for you.
Beginning Cyber-Security practice.
Tags: cybersecurity, security
Published: 2022-01-27 22:36:23

Cyber Security is one of the most lucrative fields in computer science that is registering streams of new learners and professionals. 
The massive move from analogue to digital data has greatly led to this migration.

Here are some vital resources you could use to make your learning path smooth. You could moreso use them to practise and affirm the skills you have learnt.

**1. Exploit.education**
https://exploit.education/ - Exploit education is a platform with a variety of resources for learning vulnerability analysis, software debugging, exploit development, binary analysis and general cyber security issues.

**2. Vulnhub.com**
https://www.vulnhub.com/ - This refers to a collection of exploitable Virtual Machines where you can practise penetration without fear of infringement policies.

**3. Newbiecontest.org**
https://www.newbiecontest.org/ - It is an online forum/platform that provides different challenges to your Cyber Security skills. The skills are not limited to: cryptography, forensics, Hacking etcetera.

**4. Command Challenge**
https://cmdchallenge.com/ - This is a platform where you get to practise your bash commands. It is simple and friendly to use since it instructs you on the command execution.
New Years Resolution - Dev Log 13
Tags: beginners, programming, webdev, computerscience
Published: 2022-01-27 22:29:38

Yesterday I was able to convert almost all of the original project over to Next. I am already seeing minor performance increases on Lighthouse. This is not the main reason I made the switch, but it is some nice frosting on the cake. The only issue I ran into so far was the rich text editor. So apparently most rich text editors use the "window" in some way or another, I believe to mount; which makes sense. The problem is that in Next the window is preloaded, and overall treated differently than in just standard React. So I had to ditch MKeditor5. I found a really good solution, in my opinion, I actually like it better than my last rich text editor, SunEditor. SunEditor is even easier to configure and implement, plus it works in Next. I feel like I am going to write an additional blog today on HashNode and DevTo which will be a tutorial on how to use SunEditor with Next. I had to learn through diving into the documentation which is fine, but it would have been nice to find an article and just use that.

If you have not checked out the video discussing the basic UI, please do: youtube.com/watch?v=jvH9iTYzUbQ

Idea 1 - Job Board: Currently in the process of converting the original React project over to Next. Most of the way through, only two pages left. After that, I can start on the back end.

Idea 2 - Paid Plugins: Scratched

Idea 3 - SaaS: I have a solid idea for a SaaS company I believe, but will not start on this till my job board is out and functional, even though I'm really excited about it.

Idea 4 - Paid API: Just learned about how you can build an API and market it easily through rapid API. I am thinking that this might be something I want to try.
What is Beacon request
Tags: javascript, api, programming
Published: 2022-01-27 22:27:03

navigator.sendBeacon() method asynchronously sends an HTTP POST request in reliable way, it's mostly used to send analytics.

it returns true if the user agent successfully queued the data for transfer. Otherwise, it returns false.

Unlike traditional HTTP requests, sendBeacon will always reach to the server even if you unload or exit the page in the middle of the request.

Example

```javascript
document.addEventListener('visibilitychange', function logData() {
  if (document.visibilityState === 'hidden') {
    navigator.sendBeacon('/log', analyticsData);
  }
});
```