teleren/devto huggingface dataset:
Why Programmers experience Imposter Syndrome
Tags: webdev, devops, database
Published: 2021-08-30 12:15:34

Imposter syndrome can never be defined in a single line of the sentence. But it’s a condition whereby it makes a programmer feel like quitting because of inside fears about some situations. It's not a portion of developers, but everyone in that field has or will experience imposter syndrome.

Causes of imposter syndrome and how to deal with it

When you start learning each technology that is emerging thinking you are being left behind. The fact is we cannot keep up 100% with the trends in the market. Technology, mostly web development, is growing daily.

Debugging is one of the processes that can make you feel inferior on your job. You might create a large project for a company but during production, it ceases to work as expected. Trust me, you will spend more time looking for the bug, if you are not working with a team, then it's even more difficult.

At some point, we doubt your ability to work, let's say on a certain job. When employed, we feel like we are being paid more than what we can deliver. Be bold with your knowledge, the managers don’t know how to write codes. Remember the time you spend learning those languages.

Programming in general is hard. It requires a sacrifice of time to be a good coder. Great programmers say you need to spend 1000 hours to become an 80% software programmer. Some people will give up on the way, especially when things seem rough. Yeah, it's true, learn one language at a time. Don’t rush, you will never know everything.

Don’t be afraid to make mistakes. In your journey, you will meet people who are smarter than you. Let's say you join a team, within your colleagues, there is one developer who will solve all your problems. Don’t look down, but take it as a challenge.

After you have spent all your time learning, be sure there are more than enough companies looking for developers. Not just software engineers, but people who can write clean and maintainable codes.

Most of the skills you will learn on the job are given. Therefore, if you feel you are set, never feel less on the certain post of a job. Just give it a try. There are various platforms offering freelancing activities. It might take some time but once you are in the limelight, you will ripe great stuff.

Technology is a large field with various sub-categories. You are flexible to change careers, therefore whenever you feel like you don’t want to write code anymore, shift to a DevOps engineer.

Don’t stay in a similar field for all that time if you hate it. I do love cybersecurity, but I am a web developer. On my journey, I opt to turn to ethical hacking. Trust me, being in the tech field is fun. All in all, joining big companies is more fun. People are making 6-figure salaries out of the things they wanted to quit. Never give up
What is Two-factor Authentication | Verification ??
Published: 2021-08-30 12:14:06

✅ With 2-Step Verification (also known as two-factor authentication), you add an extra layer of security to your account in case your password is stolen. After you set up 2-Step Verification, you'll sign in to your account in two steps using: Something you know, like your password. Something you have, like your phone.

✅ In Simple Terms => #Adding Extra #Layer of #Security on your #data

Some Examples of Two Step Verification Provided By The following
Organizations | Companies

✅ Google's 2-Step Verification 
✅ Facebook's 2-Step Verification 
✅ Instagram's 2-Step Verification 

& Many more services & companies provide the two step verification for their users...

#image credit =>naked security by SOPHOS

For More Interesting Facts...
✅ Follow @devkshitij7
A Fun Programming Joke To Start Your Day
Tags: jokes, dailydeveloperjokes
Published: 2021-08-30 12:00:24

---
title: "A Fun Programming Joke To Start Your Day"
description: "Check out today's daily developer joke! (a project by Fred Adams at xtrp.io)"
series: "Daily Developer Jokes"
published: true
tags: #jokes, #dailydeveloperjokes
---

Hi there! Here's today's Daily Developer Joke. We hope you enjoy it; it's a good one.

![Joke Image](https://private.xtrp.io/projects/DailyDeveloperJokes/public_image_server/images/5e1258f50f7c0.png)

---

For more jokes, and to submit your own joke to get featured, check out the [Daily Developer Jokes Website](https://dailydeveloperjokes.github.io/). We're also open sourced, so feel free to view [our GitHub Profile](https://github.com/dailydeveloperjokes).

### Leave this post a ❤️ if you liked today's joke, and stay tuned for tomorrow's joke too!

_This joke comes from [Dad-Jokes GitHub Repo by Wes Bos](https://github.com/wesbos/dad-jokes) (thank you!), whose owner has given me permission to use this joke with credit._

<!--
Joke text:
___Q:___ Why did the developer go broke?

___A:___ Because they used up all their cache
 -->
5 Reasons Why You Should Never, Ever Write Tests
Tags: beginners, programming, webdev, testing
Published: 2021-08-30 11:57:33

*This post was originally published at [kais.blog](https://kais.blog/p/reasons-why-you-should-never-ever-write-tests).*

---

As a software developer, there is one topic that always leads to controversial discussions. Should one write tests or not? While there are always questionable experts who argue FOR writing tests, I have the definitive answer. Don't.

Many terrible things happen once you start testing your code. So I prepared a small, incomplete list to show you why you should never, ever, write tests:

---

## You would start to question your code

What audacity. If you wrote tests, which of course you won't, your code would be questioned. Does it work as expected? Of course it does. Besides, there's no point in catching catastrophic bugs early, after all, they only ever happen in someone else's projects.

---

## Your code would be clearly defined and well designed

You're not an art student, are you? Then what do you care about design? If you ever test parts of your code, you would be forced to clearly define what the code is responsible for. So you would focus on what is essential. With that you take away the possibility to sneak in code that nobody needs and nobody uses.

---

## You would have to write less code

Testing can lead you to write less code. After all, you only ever implement so far that the tests pass. And less code means fewer lines of code. Who can brag about having worked on gigantic projects when there aren't that many lines of code? Besides, we're still in the 2000s, somehow, and we're billed on the basis of lines of code (LOC). Never reduce the lines of code. Ever.

---

## You would save countless hours that you could normally waste on debugging or maintenance

This point is really critical. If, strangely enough, you are not paid by lines of code, then at least by the hour. With testing you would save many hours. How awful is the idea that you suddenly have time for other things and on top of that the certainty that the code behaves as expected. Scary.

---

## You would enable others to understand your code and collaborate with you

I don't really need to write that much about it. Why would you even want to do that? With tests, your code is suddenly documented and much easier to refactor. Not good. If you are no longer the only one who can work on a project, then you will definitely be replaced immediately.

---

## Final Thoughts

There you have it. My list of reasons why you should definitely not write tests. In summary, tests have only drawbacks and you should definitely [follow me on Twitter](https://twitter.com/intent/follow?screen_name=kais_blog) if you want to learn even more about how to avoid being a good software developer.

If you want to convince other software developers why they shouldn't write tests, feel free to share this post with them.

Seriously though, write tests.

---

*This post was originally published at [kais.blog](https://kais.blog/p/reasons-why-you-should-never-ever-write-tests).*
Run RDS start of month
Tags: aws
Published: 2021-08-30 11:53:23

If you have a requirement to keep the AWS RDS running only few days at the start or end of the month and unable to use Instance Scheduler, setup a lambda function to trigger based on cronjob using the following python script.


Following lambda python script will stop the RDS based on the environment variable configured on the lambda function.  You can setup another function to start separately by modifying `rds.stop_db_instance` to `rds.start_db_instance`

```
import sys
import os
import botocore
import boto3
import datetime
from botocore.exceptions import ClientError


def lambda_handler(event, context):
    # TODO implement

    rds = boto3.client('rds', region_name='ap-southeast-2')
    DBinstance = os.environ.get('DBInstanceName')
    
    try:
        dt = datetime.datetime.today()
        print(dt)
        if dt.day == 1 or dt.day == 2:
            print("Skip...")
        else:
            print("Continue...")
            response = rds.stop_db_instance(DBInstanceIdentifier=DBinstance)
            print(response)
    except ClientError as e:
        print(e.response['Error']['Message']) 
```
Mike Woods Biography, Wife, Fox 5, Gay, Age, Net Worth More

Published: 2021-08-30 11:48:37

Are you interested in knowing who is Mike Woods and his biography? If your answer is yes so you come to the right place to know about him.  He is an American meteorologist. He joined the Fox 5 news channel in 2001. Moreover, since then, he has been a featured reporter for Fox 5 NY, also known as Gay Weather Men.

Today I came to tell you is he married and the name of Mike Woods Wife? And also Mike Woods Age and Net Worth in 2021. 
https://www.biographyhoses.com/2021/06/mike-woods.html
Working With Dynamic Components in Svelte
Tags: svelte
Published: 2021-08-30 05:54:45

Svelte offers multiple [special elements](https://svelte.dev/docs#svelte_self) that we can use to write cleaner and more efficient code.

One such special element is the very powerful `<svelte:component>`. It can be used to dynamically render a component and switch to rendering a different component on demand.

To better understand this, consider the following code:

```svelte
{#if fruit === `apple`}
    <Apple />
{:else if fruit === `banana`}
    <Banana />
{:else if fruit === `pumpkin`}
    <Pumpkin />
{/if}
```

The issue with this approach is that it doesn't scale nicely. In this example, a fruit component is dynamically rendered based on the value of `fruit`, each time the variable changes.

But what if you had a hundred fruits? Well, now you're dealing with hundreds of lines of code. And managing those hundreds of lines, especially with more complex conditionals, is going to be a real mess.

So, this is where `<svelte:component>` comes in!

Here's an example of how we can use it to dynamically render our fruit components:

```svelte
<script>
    import Apple from './Apple.svelte';
    import Banana from './Banana.svelte';
    import Pumpkin from './Pumpkin.svelte';

    const fruits = [
        { id: 0, component: Apple, },
        { id: 1, component: Banana, },
        { id: 2, component: Pumpkin, }
    ];

    let fruit = fruits[0];
</script>

<svelte:component this={fruit.component} />
```

That's much better! Now, no matter how many fruits we have, all we need is just one `<svelte:component>`, potentially shaving off many redundant lines of code.

Just remember to pass a valid component *or* a falsy value to the `this` prop!

## Conclusion

Svelte has a lot of useful and unique features, and it can take some time to learn them all and get familiar with using them.

Special elements like the dynamic component can be very powerful, and I hope it helps you optimize your code a bit.
Week Wise Data Structures and Algorithms Schedule for Placements. (Part-2)
Tags: datastructure, programming, dsa, python
Published: 2021-08-30 11:46:00

_This is the part-2.
For Part-1- You can visit below._
{% link https://dev.to/sakshamceo/complete-data-structures-and-algorithms-roadmap-for-placements-part-1-551b %}
#### There are Different strategies
1) Either you can Finish the entire syllabus once and then move to detailed practice questions. On [Leetcode](https://leetcode.com/) and [A2OJ](https://a2oj.herokuapp.com/). Side by side sharpen your DSA skills by giving **Short contests** on *Codeforces* and **Long Contests** on *Codechef*

2) Or you can got to [Codechef DSA Learning Series](https://www.codechef.com/LEARNDSA/?itm_medium=navmenu&itm_campaign=learndsa) and my favorite [A2OJ](https://a2oj.herokuapp.com/). Pick Questions topic wise and try solving. You will come across new concepts at every new question and then you can learn them as well.  

###Week wise Study Plan
**Week 1**
Basic Maths + Practise Questions
Array Introduction and Operations
STL (very very imp)

**Week 2**
Array Practise Questions
Sorting Algorithms + Practise Questions

**Week 3**
Matrix/Strings + Practise Questions 
Basic Bit Manipulation + Practise Questions

**Week 4**
Hashing + Practise Questions 
Linked List Introduction and Operations

**Week 5**
Linked List Practise Questions 
Stack Introduction and Operations

**Week 6**
Stack Practise Questions

**Week 7**
Queue Introduction and Operations
Queue Practise Questions 

**Week 8**
Tree Introduction and Operations
Tree Practise Questions 

**Week 9-10**
Heap/Graph Introduction and Operations
Heap/Graph Practise Questions

**Week 11**
REVISE TREES,GRAPHS, STACKS QUEUES
Recursion + Practice Question

**Week 12-14**
Greedy Algorithm Introduction and Implementation
Greedy Algorithm Practise Questions 

**Week 15-17**
BackTracking/Dynamic Programming Introduction and Implementation, BackTracking/Dynamic Programming Practise Questions

####For Programing Practice Question -[Love Babbar's DSA 450 questions](https://drive.google.com/file/d/1FMdN_OCfOI0iAeDlqswCiC2DZzD4nPsb/view) are sufficient. _Do 3-4 Easy Questions and 1 Tough Question_ (At bare minimum) _per day_ from _each Topic_

:heart: _Like and Follow_
AWS Security Analytics Bootstrap
Tags: aws, security, serverless
Published: 2021-08-30 11:37:36

AWS recently released AWS Security Analytics Bootstrap which is an open source framework designed to quickly setup Athena to perform analysis on AWS service logs archived in Amazon S3 buckets.

More info here: [Link](https://github.com/awslabs/aws-security-analytics-bootstrap/blob/main/AWSSecurityAnalyticsBootstrap/docs/aws_security_analytics_bootstrap_deployment_guide.md)

This solution currently support CloudTrail, VPC Flowlogs, and Route53 resolver query logs. Ensure S3 bucket policy is modified before deploying the solution.
WebRTC: How to Create a Simple Skype-Like Application
Tags: webrtc, skype, livecoding, application
Published: 2021-08-30 11:28:22

{% youtube fs_0Lr6OMWM %}
How to create a simple Skype-like video calling application that runs in your browser? When Jakub explains that, it seems so simple! 

In this episode of Experts Zone you will find not only useful information, but also livecoding - try yourself :)

☑ Introduction of WebRTC technology 
☑ Core application architecture
☑ Dialing flow
☑ ICE candidates exchange 
☑ STUN/TURN servers
☑ Live coding

You can also read the article at [Frontend House](https://frontendhouse.com/experts-zone/webrtc:-how-to-create-a-simple-skype-like-application-experts-zone-3)
Best coding practices.
Published: 2021-08-30 10:56:07

### Best coding practices.
- Always name your variables and functions with the utmost care and explain them thoroughly.
- Keep documentation concise but descriptive.
- The reading time for programs is much more than the writing time. Hence, the code must be such that the reading is easier to do. A little more time spent in making the code lucid goes a long way in saving time later.
- Each function must do only one task but do it well.
- Treat each function as a BlackBox- each function must hide something.
- Keep the connections simple. Avoid global variables wherever possible.
- If you use global variables, document them thoroughly. Not doing so will cause side effects.
- The quality of the test data is more important than its quantity.
- Program testing can show the presence of bugs, but never their absence. You cannot ever guarantee 100% correct code.

_Adapted from the book [Data Structures and Program Design in C](https://www.amazon.in/Data-Structures-Program-Design-2e/dp/8177584235)_
DevOps Services | Devops Consulting and Implementation Services | Utthunga
Tags: devops, services
Published: 2021-08-30 10:48:43

Are you looking for custom DevOps services for all industry verticals? Utthunga provides DevOps consulting services, implementation and setup for both on-prem and cloud setup using the popular toolchains with applicable standards. Find out more!-->https://utthunga.com/product-engineering/quality-engineering/devops/
Cara Membuat Power Amplifire
Published: 2021-08-30 10:27:49

Hallo sahabat semua salam jumpa kembali,mempunyai sebuah power amplifire yang bersuara jernih memang sangat di idamkan oleh para hobby elektronik apalagi sebagai pembuat nya,nah pada kali ini saya ingin berbagi buat anda para sahabat semua yang suka dalam hal merakit sebuah peralatan elektronik terutama dalam membuat amplifire yang saya kira hasil nya sudah cukup lumayan lah buat berdendang dalam satu ruangan,dan pada kali ini saya ingin berbagi buat anda para sobat bagaimana Cara Merakit Power Amplifire Suara Jernih

Yang tentu saja kita perhatikan adalah pada bagian regulator nya ,serta karakter dari jenis power amplifire nya itu sendiri ,dan saya coba - coba untuk membuat nya serta sudah banyak di buktikan oleh sahabat dan teman teman yang hobby nerakit amplifire dengan membuat sebuah amplifire yang berdaya sedang dengan jenis mono dengan ic yang cukup populer yaitu IC TDA2004 yang pada kali ini saya menggunakan layout yang sudah saya bagikan di blog ini,jadi anda yang penasaran ingin membuat nya silahkan anda cari - cari pada artikel di blog ini ya layout nya.

Source :
https://blogkamarku.blogspot.com/
Git Remove Local and Remote Tag : The Final Guide
Tags: git, codenewbie, beginners, tutorial
Published: 2021-08-30 10:27:46

On [Git](https://git-scm.com/), **tags** are often used in order to tag specific commits that may be more important than others.

**Tags** may be used in order to bookmark certain events : releases, bug-fixes or just to add an informative and descriptive note to a commit.

On [GitHub](https://github.com/), tags are often associated with actual product releases for example.

However, in some cases, you may want to delete Git tags easily locally or remotely.

## Delete a local Git tag
In order to delete a local Git tag, use the `git tag` command with the `-d` option.
```
git tag -d <tag_name>
```
For example, if you wanted to delete a local tag named “v0.1” on your commit list, you would run
```
git tag -d v0.1
```
The output will be:
```
Deleted tag 'v0.1' (was 88f2a35)
```
If you try to delete a Git tag that does not exist, you will simply be notified that the tag does not exist.
```
git tag -d v0.2
```
the output will be:
```
error: tag 'v0.2' not found.
```
If you want to make sure that tags were correctly deleted, simply list your existing tags using the tag command and the `-l` option.
```
git tag -l
```

## Delete a remote Git tag
In order to delete a remote Git tag, use the `git push` command with the `-–delete` option and specify the tag name.
```
git push --delete origin <tagname>
```
Back to the previous example, if you want to delete the remote Git tag named “v0.1”, you would run
```
git push --delete origin v0.1
```
the output will be:
```
To https://github.com/ZigRazor/repo.git
 - [deleted]         v0.1
```
To delete a remote Git tag, you can also use the `git push` command and specify the tag name using the refs syntax.
```
git push origin :refs/tags/<tag>
```
Back to the example, in order to delete a tag named “v0.1”, you would run
```
git push origin :refs/tags/v0.1
```
the output will be:
```
To https://github.com/ZigRazor/repo.git
 - [deleted]         v0.1
```
Why should we specify the “refs/tags” instead of just specifying the tagname?

In some cases, your tag may have the same name as your branch.

If you tried to delete your Git tag without specifying the “refs/tags” you would get the following error
```
git push origin :v1.0
error: dst refspec v1.0 matches more than one.
error: failed to push some refs to '<repository>'
```
As a consequence, you need to specify that you are actually trying to delete a Git tag and not a Git repository.

## Conclusion
In this tutorial, you learnt how you can easily delete a local and a remote Git tag.

______________________________________________________

*For More "The Final Guide" see the [Index Page](https://dev.to/zigrazor/the-final-guide-index-4954)*
How to show which Git branches have changed recently
Tags: git, workflow
Published: 2021-08-30 10:19:29

---
title: How to show which Git branches have changed recently
published: true
description: How to use Git's in-built sorting functionality to manage repos with many active branches
tags: git, workflow
//cover_image: https://direct_url_to_image.jpg
---

I will admit to some bad working habits, one of them is working on multiple things at the same time rather trying to focus exclusively on one unit of work and completing it before I move on to the next thing. This means that I sometimes have multiple Github branches that I'm working on for a repository. Unfortunately this intersects with another bad habit I have of not cleaning up my local branches frequently. The two combined mean that when I'm slicing between tasks I often find it difficult to find the branch I was working on before I switched tasks.

Enter Git [sorts](https://git-scm.com/docs/git-branch#Documentation/git-branch.txt---sortltkeygt) to save me!

By default Git sorts branches lexically but using the `committerdate` sort you instead get the branches from the most recently committed to the last commit date.

Git sorts can also be reversed by putting the minus sign before the sort name.

This effectively brings back the branches in the order you last changed them.

To summarise then:

```
git branch --sort=-committerdate
```

Allows you to see which branches you changed most recently in a repository.