teleren/devto huggingface dataset:
Java Static Keyword
Tags: java, beginners
Published: 2021-05-27 03:09:06

What does the static keyword mean and how is it used.  This keyword I have used many times but have only partially understood how it works under the hood.  The primary characteristic of something that is static in Java is that it belongs to the class and not a specific instance.  For regular variables and methods each time an object is instantiated a separate copy of each is created.  Static variables are created once at the start of execution.

Now that we have learned what the static keyword is how is this useful in the context of an application?  Reasons to use static is the value of the variable is independent and shared across each object.  An example off the top of my head is if there was a total count variable that incremented each time an object is created.  A static method that I use often is toString() from the integer class.  This method does not required an integer object to be created and can be called directly from the class.  Static methods and variables use dot notation to be referenced in the format class.variable or class.method().

Some other uses of the static keyword that I was not previously familiar with is the static block, class, and import.  Starting with static blocks, they are used for initializing static objects.  If a static array is created and elements need to be added then a static block acts almost as a constructor to populate that array at execution.  In Java, classes are able to be nested which allows for the use of static classes.  They will behave like normal classes but only the outer class will have access to it.  A popular implementation is the Singleton model which often utilizes a static class to hold the instance.  Lastly I will discuss the static import option.  When the static keyword is used while importing a library the static members are available without using the class name.  An example of this would be if a static import was called for the math library then the pow() method would be usable instead of Math.pow().  This makes sense for classes whose purpose is to provide methods that do not rely on objects or instances.  Thank you for reading my post this week on the static keyword.  Please leave a comment or like the post if you found it helpful.

*Sources:*

1. Moock, C. (2007). Essential ActionScript 3.0: ActionScript 3.0 programming fundamentals. O'Reilly.

2. Java Static Method, Variable and Block with Example. Guru99. (n.d.). https://www.guru99.com/java-static-variable-methods.html#:~:text=What%20is%20Static%20Variable%20in,the%20start%20of%20the%20execution.

3. Baeldung. (2021, May 10). A Guide to the Static Keyword in Java. Baeldung. https://www.baeldung.com/java-static.

4. Static import in Java. GeeksforGeeks. (2017, November 29). https://www.geeksforgeeks.org/static-import-java/.
먹튀검증 안전토토사이트
Published: 2021-05-27 02:51:34

This article is very interesting information. It has helped me a lot. <a href="https://a-cm.com//">먹튀검증</a> Thank you very much for providing this quality information in an easy-to-understand manner. Our site also provides high-quality information, so it will be helpful for your site. <a href="https://toto-times.com//">먹튀검증</a>
#SpeedOfLife - In Conclusion, Thanks for the Conversation
Tags: speedoflife, devops
Published: 2021-05-27 02:26:39

As we close out the month of May, the #SpeedOfLife campaign will come to a close as well. Soon I will no longer be monitoring the hashtag but please feel free to <a href="https://twitter.com/search?q=%23speedoflife&amp;src=typed_query">continue the conversation on Twitter</a>. You can even tag me (@dev_nikema) if you like.

What does "speed of life" mean to you?

<div class="sc__GifContainer-sc-3bu46y-4 gtctVE"><img class="aligncenter" src="https://media1.giphy.com/media/l2SpQRuCQzY1RXHqM/giphy.gif?cid=36b14facgo7lutzpzikpj47kilvh6o22lzt8kcaoaa2x1r8t&amp;rid=giphy.gif&amp;ct=g" alt="Talk amongst yourselves" width="314" height="321" /></div>
Before I step away, I'd like to highlight some of my favorite parts of my interviews with Armory crewmates. It was interesting to hear all of the different interpretations of the phrase, "speed of life."
<h3>Lee Faus, Field CTO</h3>
First up is Field CTO Lee Faus on speed. In the full conversation, he gives great examples of how the appropriate speed depends on the situation and the needs at hand.

{% youtube _rPjN4uTzeY %}

<h3>Chad Tripod, Field CTO</h3>
Field CTO Chad Tripod with examples of what software delivery at the speed of life looks like today.

{% youtube e_Flh4LaL3U %}

<h3>Fernando Freire, Software Engineer</h3>
Software Engineer Fernando Freire on how great developer tooling "helps software delivery fade into the background"

{% youtube L2MvVEcGmyU %}

This campaign was a stretch and a challenge for me. I have thoughts about it but I'm saving them for a future blog post 😀. To say the least, I learned a lot. I appreciate everyone who took the time to speak to me and extra-special thanks go to the people who joined a live stream (Kelsey Hightower, Margaret Francis, and David Morgenthaler).

Some recordings I've yet to publish. If you're interested in viewing them, check out the <a href="https://youtube.com/playlist?list=PLkzenGYiHxOPSxa2bW939rN3u7g3KXyDm">#SpeedOfLife YouTube playlist</a>. It will be updated with clips from the interviews and live streams.
Hi everybody. It smells like minestrone soup in here, or maybe that something I left in my backpack
Published: 2021-05-27 02:22:32

Hi everybody. I'm DK, the guy who's usually spanging out front by the bus stop. (I only say that because I don't know if you would recognize me without my glitter robe on.) Budenieways I'm just mentioning that because I've talked to a few of you about my idea for eatable glitter that breaks down so the mess goes away after a few days, plus it tastes great and it doesn't get you fired from Baskin Robbins. Budenieways, I saw this really neat Joplin plugin for VSCode and thought I'd come say hi!
#SpeedOfLife Week Two Recap
Tags: speedoflife, softwaredelivery
Published: 2021-05-27 02:15:07

<h2>Tweets, Clips, and Double the Livestreams</h2>
In week two, we shared some awesome clips from my #SpeedOfLife interviews. Additionally, we had a bonus live stream with Kelsey Hightower. To date, there has been an element of chaos in each live stream. I've got two more planned, so two chances to get through a smooth stream 🤞🏾.
{% twitter 1393292629010313216 %}

<h3>The Armory Crew is Chiming In</h3>
I shared clips from my chats with Becky Jaimes (Chief of Staff) and Margaret Francis (COO). It was nice to hear their personalized perspectives on #SpeedOfLife.
{% twitter 1394388947908718595 %}
{% twitter 1395154804993789954 %}

{% youtube bN3g1jnRflY%}

&nbsp;
<h3>Reminder, You Can Join the Conversation on Twitter</h3>
Jeff Barr and Isaac Mosquera did. Just use the hashtag #SpeedOfLife and share what coding at the speed of life means to you.

{% twitter 1392517572633976836 %}


We're chatting with the community for the month of May. I'd love to hear your point of view. See you next week!

&nbsp;
5 mistakes that every intern should avoid
Tags: mistake, internship, intern, developer
Published: 2021-05-27 02:04:06

## :alarm_clock: Poor Time Management
One of the most common mistakes interns make is managing their time badly. Getting to work late or taking long lunch breaks doesn't sit well with employers. As a professional, you should adhere to the rules and regulations of the office.

You should also learn how to better manage and prioritize your time. If you have multiple tasks, it's your job to prioritize them. If necessary, speak with your mentor or supervisor to determine which are the most time-sensitive ones.

## :computer: Avoid Trivial Tasks
Another common mistakes many interns make is to underestimate the importance of menial tasks. These can include research, data entry or filing and although they might not seem that important, they are actually a crucial part of running a business.

By doing those kind of work, you'll also gain the respect of your boss, which could lead to more challenging one. But you want to avoid being taken advantage of. Don't hesitate to speak with your employer, mentor or manager beforehand about responsibilities you'll have grounds for requesting some challenging work mixed in with the filing.

## :speech_balloon: Not Asking for Feedbacks
Feedback is the most valuable part of the internship as it helps you enhance your skills and become a better worker. Getting feedback will let you know about your strengths and weaknesses. It will also expose you to your key skills, strong areas, natural talent, and professional inclination.

Unfortunately, a lot of interns overlook this step, expecting managers to deliver feedback only if something critical comes up. Instead, take the first step and ask them to weigh in some of the tasks you're working on.

## :office: Not Learning the Office Culture
Each office has its own culture that make it different than others. Individuality is a good trait but not when it clashes with the corporate culture. Some offices are formal and corporate, while others are laid-back and casual. Oftentimes just observing how employees behave and interact will help you fit in.

## :notebook: Not Keeping in Contact
Many interns lose touch with an organization once they stop interning there. If you happened to enjoy your time during the internship and you want to be a part of it in the future, then it is important to show your interest by keeping in contact with the organization.

Keeping in touch with the organization will keep you in their good books and they will be more than happy to consider you for a suitable job since you are already familiar with the people and environment of the organization.

What about you? Have you made any memorable mistakes during your internship? :smiley:

:iphone: Keep in Touch
If you like this article, don't forget to follow and stay in touch with my latest ones in the future by following me via:

- **Twitter:** https://twitter.com/RichardWynn01
- **Medium:** https://richard-wynn.medium.com
- **Github:** https://github.com/richard-wynn
Next.js + TypeScript + Tailwind CSS project setup 
Published: 2021-05-27 01:09:54

---
title: Next.js + TypeScript + Tailwind CSS project setup 
published: true
description: 
tags: 
//cover_image: https://miro.medium.com/max/1000/1*s4M2aiTo5Xec7-HT24wtjg.png
---

**1. Set up the Next.js project**
First, create-next-app use the command to create a codebase from the Next.js template.
```
npx create-next-app nextjs-ts-tailwind-example --use-npm --example "https://github.com/vercel/next-learn-starter/tree/master/basics-final"
```
When the command is completed, the code of Next.js is generated, so move the directory and check the operation.

```
cd nextjs-ts-tailwind-example
npm run dev
```
**2. Set up typescript**
create config files for typescript 
```
touch tsconfig.json next-env.d.ts

```
Install the packages needed to run TypeScript.
```
npm install --save-dev typescript @types/react @types/node
```

add to the Typescript config file
```
//tsconfig.json 
{
  "compilerOptions": {
    "target": "es5",
    "lib": [
      "dom",
      "dom.iterable",
      "esnext"
    ],
    "allowJs": true,
    "skipLibCheck": true,
    "strict": false,
    "forceConsistentCasingInFileNames": true,
    "noEmit": true,
    "esModuleInterop": true,
    "module": "esnext",
    "moduleResolution": "node",
    "resolveJsonModule": true,
    "isolatedModules": true,
    "jsx": "preserve"
  },
  "include": [
    "next-env.d.ts",
    "**/*.ts",
    "**/*.tsx"
  ],
  "exclude": [
    "node_modules"
  ]
}

```
add to the next-env.d.ts config file
```
/// <reference types="next" />
/// <reference types="next/types/global" />
```
Next, rewrite various js files to ts files by referring to the following repository.
```
mv components/date.js components/date.tsx
mv components/layout.js components/layout.tsx
mv lib/posts.js lib/posts.ts
mv pages/_app.js pages/_app.tsx
mv pages/index.js pages/index.tsx
mv 'pages/posts/[id].js' 'pages/posts/[id].tsx'
mv pages/api/hello.js pages/api/hello.ts
```
After rewriting, check the operation.
```
npm run dev
```
Check the operation with a browser and it is OK if it works without error.

**3. Set up Tailwind css**
```
npm install tailwindcss@latest postcss@latest autoprefixer@latest
```
generate a Tailwind CSS configuration file.
```
npx tailwindcss init -p
```
Then, tailwind.config.js the postcss.config.js two files will be generated.
```
//tailwind.config.js
module.exports = {
  purge: [], //remove this line 
  purge: ['./components/**/*.tsx', './pages/**/*.tsx','./public/**/*.html'], //add this line
  darkMode: false, // or 'media' or 'class'
  theme: {
    extend: {},
  },
  variants: {
    extend: {},
  },
  plugins: [],
}
```

```
//postcss.config.js
module.exports = {
  plugins: {
    tailwindcss: {},
    autoprefixer: {},
  },
}
```
Rewrite to read the CSS generated by Tailwind CSS styles/global.css.

```
//styles/global.css
@tailwind base;
@tailwind components;
@tailwind utilities;
```
Now you can use Tailwind CSS!
Dramacool la
Published: 2021-05-27 00:39:23

"Dramacool la - Watch Video and download free Asian Dramas, Movies and Shows with English Subtitles on DramaCool in Full HD For Free at Dramacool.la

+ Website: https://dramacool.la/

+ Address: C6H2+6V Shreveport, Louisiana, United States

+ Email: admin@dramacool.la

+ Phone: +14896124425

+ Social: 

- Twitter: https://twitter.com/dramacoolla
- Facebook: https://www.facebook.com/dramacoolla
- IG: https://www.instagram.com/dramacoolla
- Linkedin: https://www.linkedin.com/in/dramacool-la-b69733212/
- Pinterest: https://www.pinterest.com/dramacoolla
- About.me: https://about.me/dramacoolla

Hastag: #dramacool #dramacoolla, #movies, #streaming, #freemovies, #freemoviesonline, #watchmovies, /m/02vxn, /m/03x49v, /m/0735l, /m/02mzct, /m/07c52"
Things that don't scale well
Tags: scale, team, monolith, microservices
Published: 2021-05-31 09:03:17

---
title: Things that don't scale well
published: true
date: 2021-05-27 00:00:00 UTC
tags: scale,team,monolith,microservices
canonical_url: https://jhall.io/archive/2021/05/27/things-that-dont-scale-well/
---

Yesterday I introduced the concept of [diseconomies of scale](https://jhall.io/archive/2021/05/26/diseconomies-of-scale/). This raises the natural question: “What are some examples of things that suffer from diseconomies of scale?”

I’m sure there are countless, but here are a few I’ve been thinking about lately:

- Databases. Even the most scalable databases have limits, usually well under the order of hundreds of nodes. Many popular databases start to see diminishing returns where n > 1.
- Software development teams. Even the famous [2-pizza team](https://www.seanblanda.com/the-jeff-bezos-school-of-long-term-thinking/) is often considered too large.
- Monolithic code bases. These often turn into [big balls of mud](http://www.laputan.org/mud/)
- Microservice architectures. Come to think of it, microservices often aren’t much better.

What would you add to this list?

* * *
_If you enjoyed this message, [subscribe](https://jhall.io/daily) to <u>The Daily Commit</u> to get future messages to your inbox._
Upgrading legacy Terraform providers
Tags: terraform, aws, github
Published: 2021-05-27 00:00:00

---
title: Upgrading legacy Terraform providers
description: How to upgrade project with legacy Terraform providers
published: true
date: '2021-05-27'
canonical_url: https://marcqualie.com/2021/05/upgrading-legacy-terraform-providers
tags:
  - Terraform
  - AWS
  - Github
---
I recenty worked on some pretty old Terraform projects (built using v0.10.x I believe). The state on these projects is no longer compatible with v0.13+, which causes errors when trying to run any command. Quite frustrating and the docs don't seem to help much.

Apart from manually downgrading to 0.13, running `terraform 0.13upgrade`, then upgrading to the latest version, there didn't seem to be any documented solution.

You will likely have some kind of error, similar to the following:

> Error: Invalid legacy provider address<br/>
> This configuration or its associated state refers to the unqualified provider "aws"<br/>
> You must complete the Terraform 0.13 upgrade process before upgrading to later

If you've already upgraded past terraform 0.13 (likely if you're reading this), then you'll instead need to replace the state values directly. This can be done with the following command:

```shell
terraform state replace-provider registry.terraform.io/-/aws hashicorp/aws
terraform state replace-provider registry.terraform.io/-/github hashicorp/aws
```

Related to this, the Github provider moved from hashicorp namespace to `integrations/github`. You will need to update your existing state with this new reference. An error message you see may look something like the following:

> Warning: Additional provider information from registry<br/>
> The remote registry returned warnings for registry.terraform.io/hashicorp/github:
> For users on Terraform 0.13 or greater, this provider has moved to integrations/github. Please update your source in required_providers.

You can resolve this with the following config:

```
terraform {
  required_providers {
    github = {
      source  = "integrations/github"
      version = "~> 4.10"
    }
  }
}
```

Once you've made that change, run the following to sync it to your state:

```shell
terraform state replace-provider hashicorp/github integrations/github
```

Now you can run `terraform init` which should show green, and that it is using `integrations/github`.

My current output shows the following:

```
terraform -version
Terraform v0.15.4
on darwin_amd64
+ provider registry.terraform.io/integrations/github v4.10.1
```
THE STATE OF my REACT...ion
Tags: beginners, javascript, react
Published: 2021-05-26 23:30:13

I'm getting further along in react. I'm on the section about state and lifecycles. The example used in the reading is to  create a clock that tells time (of course) and updates itself in real time using state and lifecycle.

 This is the code:

class Clock extends React.Component {
  constructor(props) {
    super(props);
    this.state = {date: new Date()};
  }

  componentDidMount() {
    this.timerID = setInterval(
      () => this.tick(),
      1000
    );
  }

  componentWillUnmount() {
    clearInterval(this.timerID);
  }

  tick() {
    this.setState({
      date: new Date()
    });
  }

  render() {
    return (
      <div>
        <h1>Hello, world!</h1>
        <h2>It is {this.state.date.toLocaleTimeString()}.</h2>
      </div>
    );
  }
}

ReactDOM.render(
  <Clock />,
  document.getElementById('root')
);

From my understanding:
1. < Clock /> being in React.render()is how you call everything in the clock component.  

2.State is private and is controlled by the component. It is like props but replaces it in this example for the date.  

3.state is taking and holding in date.toLocaleTimeString() as a value for the Clock component. 

Later on in the example a constructor is added and this.state  = {date: new Date ()} is declared inside of it. 

In my head: 

- this.state has the value of date: new Date which is used to return the current date. Example, date: March 26 2021 , if i click on the page the next day...date: new Date() will produce March 27 2021. 

Lifecyle Methods:

Lifecycles are special methods like  mount(componentDidMount())and unmount (componentWillUnmount()) in react.

I won't make this too deep but I'm trying to find a way to understand this in a way that sticks. I'm trying to see why certain things are necessary.  

Until next time!
Are Developers Not That Keen On Kubernetes?

Tags: kubernetes, devops, developers
Published: 2021-05-26 23:11:34

Should application developers learn Kubernetes? Let’s ask an even deeper question; should application developers even be aware of Kubernetes in their infrastructure?

I frequently hear this question being asked by DevOps, Platform Engineering, and Development teams. Of course, this is a discussion that brings very different views from different people and can result in a very long debate.

Kubernetes, without a doubt, provides far more functionality than the average developer needs. While Kubernetes is robust and provides dozens of types of objects (around 50 the last time I checked), developers don’t care how many replicas of their service are running, what roles it has, or if it’s running via StatefulSets; all they care about is getting an HTTPS endpoint that they can use to deliver their product to their users.

This may appear unnecessary when only a handful of developers with only a few applications or services are deployed; however, the story quickly changes as an organization’s number of clusters, applications, and services in Kubernetes begin to scale. The development team is generally to first to feel frustrated by the growing complexity, greatly increasing the chance of inexperienced AND experienced developers to become distracted, less productive, and more prone to mistakes. Developers need to deal with infrastructure more these days, so the focus should be on simplifying and not complicating.

Considering this, we decided to build Shipa to do precisely that; grow Kubernetes into a user-friendly application management framework. Shipa’s goal is to allow developers to focus on their application code while empowering DevOps and Platform engineers to better manage and control their clusters and infrastructure.

Shipa makes deployment, management, and controls of applications easy. Shipa does not treat Kubernetes as a first-class citizen; Shipa reserves that title for the applications and the teams that develop and control them. Doing so allows the developer not to worry about ConfigMaps, ingress rules, PVs, PVCs, etc. in his/her day-to-day. Even if DevOps and Platform engineering teams decide tomorrow to move from one Kubernetes cluster to another or across different providers, the way applications are deployed, operated, and controlled will not be impacted.

Software is getting complicated, and business requirements are evolving rapidly. The easier we make it for developers to deploy their applications and for DevOps and Platform Engineering teams to build controls and guardrails around it, the more value they will deliver, faster, and more secure.
Day 375 : CREAM
Tags: hiphop, code, coding, lifelongdev
Published: 2021-05-26 22:44:41

_liner notes_:
- Professional : Got some good feedback on my demo application. Just added a little notice if the user denies access to a thing that is needed to run the app. Other than that, worked on my blog post and spoke with some team members.

- Personal : Got the server part of the push notifications for my site working. People can subscribe to get notifications. So the client side application can get a token and then use that token to subscribe to different "topics" and get notifications on that "topic". Originally, I was thinking about having a Cron job run every hour and when it hit an hour where we were going live, it would send notifications to the people who signed up for that time. Found out that it's 10 cents a month for every job that runs. So 24 hours means 24 jobs everyday of the month. That can be a lot of CREAM! I'm thinking that's why I've been getting a bill every month for other projects that only checks every 3 hours. haha So now, I have it where the backend will send a message when a new entry is added to the database.

![View from a mountain through some trees into a very green valley in Mangup, Crimea with other mountains that have white cliffs](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/l7gconl8gi69gra2yaot.jpg)

Now that a user can subscribe to a date and have a message sent to them when a new entry is made in the database, I need to create the interface that will create the entry. So it's time to start working on the dashboard / admin section. The project is getting there, slowly. haha

Have a great night!

peace piece
Dwane / conshus
https://dwane.io / https://HIPHOPandCODE.com
{% youtube PBwAxmrE194 %}