teleren/devto huggingface dataset:
My firth-week experience in Taskforce 5.0
Tags: taskforce, awesomitylab, codeofafrica
Published: 2022-03-20 09:54:27

The best and most successful products are designed with the people they are creating for in mind. When you understand your customers or end-user, you can create what they want or need. That’s design thinking – a human-centered approach to ideating and solving problems with innovative and creative solutions.

Recently, I have been working on a project but there was something wrong. We have seen that most of the users reach a registration page, but they don’t proceed to other pages. We interrogated the issue and we found that the reason is a long registration form and our customers are busy.

Imagine you bought a fridge and you want it to get delivered to your home, and you found a good app that can help you to book a driver to deliver your load. But when you open the app, you got a long registration form before you proceed. You will get frustrated.

![Long Registration Form Frustration](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/2qt5fa6hwfb2n4l6ryw1.jpg) 

The design thinking process encompasses five stages. Emphasize, define, ideate, prototype, and test.

Empathize – Understand the perspective of the target audience/customer/consumer to identify and address the problem at hand.

Define – Define the problem statement clearly.

Ideate – Brainstorm ways to address identified unmet needs.

Prototype – Identity which of the possible solutions can best solve the identified problem(s).

Test – Test the product with your target audience to get feedback.

In our case, we failed for the first stage. We didn’t emphasize with our customers to truly understand their experience and anticipate their needs. Empathy allows you to set aside your assumptions about the world to gain insight into users and their needs.

> If there is any one secret of success, it lies in the ability to get the other person’s point of view and see things from his angle as well as your own

Henry Ford

The design thinking process is iterative, flexible, and focused on collaboration between designers and users, with an emphasis on bringing ideas to life based on how real users think, feel and behave.

The effective way to ensure your next project is a success is to avoid self-referential and start incorporating design thinking exercises with your team.
Stalactite ORM 1.0.0 is out !
Tags: java, orm, sql, architecture
Published: 2022-03-20 09:54:12

After many years of dev, Stalactite ORM is finally released ! It has a brand new approach about persistence :
- mapping is defined by method references instead of Annotations or XML
- its fluent API helps you see the complexity of you graph
- it eagerly fetches your relations to avoid hidden sql queries

Here is a short view of what can be achieved with it :
```java
DataSource dataSource = ... // use whatever JDBC DataSource you want
PersistenceContext persistenceContext = new PersistenceContext(dataSource, new HSQLDBDialect());

EntityPersister<Country, Long> countryPersister = MappingEase.entityBuilder(Country.class, long.class)
    .mapKey(Country::getId, IdentifierPolicy.afterInsert())
    .map(Country::getName)
    .map(Country::getDescription)
    .mapOneToOne(Country::getPresident, MappingEase.entityBuilder(Person.class, long.class)
        .mapKey(Person::getId, IdentifierPolicy.afterInsert())
        .map(Person::getName))
    .build(persistenceContext);

Country country = new Country(42L);
country.setPresident(new Person(12L));
countryPersister.persist(country);

// you can also map an SQL query to build a projection
List<Car> allCars = persistenceContext.newQuery("select id, model, rgb from Car", Car.class)
    .mapKey(Car::new, "id", long.class)
    .map("model", Car::setModel)
    .map("rgb", Car::setColor, int.class, Color::new)
    .execute();
```

Give it a try, see documentation [here](https://www.codefilarete.org/stalactite-doc/)
Week 5 of TaskForce 5.0 reflections
Published: 2022-03-20 09:51:27

> Time flies

I am not sure who said this quote but they were absolutely right. We are at the end of Week 5 and almost at the end of the TaskForce and I feel like it has only been a week. That is what happens when you are having the time of your life.

Reflecting on the progress made in the past 5 weeks is amazing and I am here to report on the things I learnt this past week.

#Design Thinking

####What is design thinking?

It is a problem-solving methodology that provides a solution based approach to solving problems. It is well suited to solving complex problems that are not well defined or known.

In a software development context, a complex problem might be that you want a new software that eliminates a particular problem for farmers but you do not have first hand knowledge on the problem since you are not a farmer.

There are some steps you would take to solve the problem like: 

- Empathise
- Define the problem
- Ideate
- Prototype
- Test
- Repeat the above until you have the perfect product.

![Design thinking process](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/4bmnh3o6784jzthtjde9.png)
 
The process deserves its own post but there are multiple resources online and I would recommend [clicking here](https://www.interaction-design.org/literature/article/5-stages-in-the-design-thinking-process) to read more about it.

#React Native bits

We had so many interesting sessions on React Native on new topics like: 
- State management
- Local storage 
- Database management
- Deployment to Google Play & App Store

The amazing thing about these technical sessions is that we are introduced to these new concepts by instructors from Code of Africa and Awesomity Labs and it is explained in detail then we are given time to put it in practice.

#Summary

This week was more fast-paced than the previous ones but it was just as interesting. Learning and fun are things that are constant in the TaskForce. Can't wait for this final week.
Week 5 at Task Force 5.0
Tags: taskforce50, awesomity, codeofafrica
Published: 2022-03-20 09:40:46

> “The more I learn, the more I realize how much I don't know.”
Albert Einstein

The famous quote by Albert Einstein can pretty much sum up my journey at Task Force 5.0. It's been 5 weeks of continuous learning and each day I get introduced to new concepts that I was not aware of. So what was new this week? Which challenges did I face? And How did I overcome them? Here is my reflection:


![What's new](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/vlxns78rz349mjbht9p2.jpg)

This week, like every other week we had informative and interesting sessions. In soft skills, I learnt how to work effectively in self-organizing teams, and realized the most important thing is to trust each other in the team. This was helpful as in the Task Force we work as a self-organizing team. Design thinking was another new concept of how to create products that are relevant to the users. In this session, I learnt to never be self-referential, which is one of the most essential things as a developer. 


![Challenges ahead](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/qghqyhtugmp113bp0ycz.jpg)

This week’s biggest challenge came in technical skills sessions. Where we were introduced to TypeOrm. `TypeScript ORM (object-relational mapper) library that makes it easy to link your TypeScript application up to a relational database.` What was the challenge? 
I installed the package following instructions from the documentation but the package was not working. I did some research on the internet, tried all the suggested solutions but to no avail. I asked my fellow interns and none of them was facing the same issue. This brought back the “5 whys” methodology we learnt the previous week. Probing myself the whys it led to the root cause which was the package was updated a couple of minutes ago and the reason it was working for others but not me it was because the new update caused some breaking changes and it was not indicated in the documentation. So the solution was downgrading to the previous version.


![fun](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/25ftmzorwzo6yrxyitkc.jpg)

All in all, easy is boring and at Task Force we are always give some interesting challenges which makes it a fun and informative experience. it's unfortunate it's coming to an end but looking forward to the final week. Thank you for your time. See you on the next one.
How do you see traffic on K8's?
Tags: programming, kubernetes, microservices, devops
Published: 2022-03-20 09:34:30

Mizu just released a new service map feature that is similar to tools like Jaeger and Zipkin that presents a map of service dependencies. 
The service map has some unique features, [[see a quick 30 sec demo vid here](https://youtu.be/iA4NBg89NTo).]

Or visit [getmizu.io](https://getmizu.io)an open source project and the service map feature offers:


1. Each connecting arrow represents a dependency between a downstream and an upstream service, where the arrow always points to the upstream service.
2. The arrow colour represents the protocol that is used between the two services (e.g. Rest, gRPC, RabitMQ, Kafka, Redis etc). 
3. The arrow thickness represents the connection’s protocol relative throughput and it is based on the number of processed messages. 

The number of processed messages is also present on the connecting arrow.

As a reminder, [Mizu](https://getmizu.io) is a lightweight API traffic viewer for Kubernetes that doesn't require any code instrumentation. It provides complete visibility to all API traffic and payloads with support for different protocols and encryption. A short video describing the new feature can be found here [Add link to video].
Next.js and <svg />
Published: 2022-03-20 09:34:26

A quick share of my experiance with Next.js and `.svg` files.


I needed to display a bunch of `.svg` files on a Next.js app.

Using `.svg` files with Next.js super cool `<Image />` component is [not recommended](https://nextjs.org/docs/api-reference/next/image#dangerously-allow-svg) since it can create unexpected behavior and lead to vulnerabilities if a security policy header is not defined.

So I needed to incorporate a loader. 
The quickest way I found was using `.babelrc` file and `babel-plugin-inline-react-svg`.
It worked! well kind of.. :confused: Some graphics were not displayed and some did, while others were cut off unexpectedly.

I dug a bit more and found [this answer](https://stackoverflow.com/a/55180310/11528989) by [@felixmosh](https://stackoverflow.com/users/6539317/felixmosh) on stackoverflow using `next.config.js` file.

####TL;DR:
~ Step One:
```.bash
$ npm install --save-dev @svgr/webpack
```

~ Step Two:
```.js
// next.config.js
    
module.exports = {
  webpack(config) {
    config.module.rules.push({
      test: /\.svg$/,
      issuer: {
        test: /\.(js|ts)x?$/,
       // for webpack 5 use
       // { and: [/\.(js|ts)x?$/] }
      },
      
      use: ['@svgr/webpack'],
    });

    return config;
  },
};
```

If you used the above solution make sure to give the question and the answer a [vote up on stackoverflow](https://stackoverflow.com/a/55180310/11528989) :slightly_smiling_face:

----
Side note, if you’re using typescript in your project and feel bad that the next.config file is a .js file don’t because next does not plan “to transpile next.config.js.” As you can see in [this issue](https://github.com/vercel/next.js/issues/5318).


I hope it helped, thanks for reading!
Task force5.0 {challenge}
Tags: taskforce, reactnative, episode5
Published: 2022-03-20 09:34:16

Hello beautiful people, In taskforce we are in our fifth week and I can`t believe that we are heading into last one.
This one was another insightful and interesting week, but unlike others was very very stressful. In fifth episode of the taskforce 5.0 blog series I will share my interesting, educational and challenging experience of the week.

## The Challenge

Software development Industry is one of industries that changes fast in way you can't imagine, to cope with those changes you must have discipline of continuous learning or improving.
Having challenge to overcome  is one of the most used technique  to grow you skillset in tech. This week in task force we had a challenge of building advanced todo application. 

![todo](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/ffo6br9kj2ohw8jz2bio.gif)
Building this app wasn't easy at all  as it was my first time building app in react-native. Late nights and stressful week took me to this success.
I can't thank enough COA and Awesomity Management  for organizing this bootcamp, the skill I gained is weapon drove me in this stressful week. Like prioritizing task  we learnt in [time management session](https://dev.to/rkay250/task-force50-time-5520) helped to deliver on time and problem solving skills help to address every problem/bug easily.

## Design thinking

Design thinking was another talk of the week. it was new concept and from this session I learnt to put user/client at the center of product we as developer are building. 
to achieve this we must pass through five stages `EMPATHIZE` `define problem`  `Ideate` `prototype` and `test`. 

In short this week ended in style and I am happy for what I can build in just a week. I know that there is long way to go and best part of me is that am eager to learn. See you on the last one
History of HTML - Hypertext markup language
Tags: html, history
Published: 2022-03-20 09:22:43

## Overview
**HTML** was developed in the 90s and still continues because HTML is constantly developing language. Many versions have come so far, In 1980, Lee discovered HTML in Geneva. Berners Lee Invented the world wide web in 1989. Al present, the task of developing HTML is within an organization "WORLD WIDE WEB CONSORTIUM" this organization now takes care of HTML

## HTML Versions
### HTML
This version was a form of SGML(Standard Generalised Markup Language). The text could be structured by this. Some tags were created it was an HTML and the next version of HTML had names so for convenience this version was also called HTML1.0

### HTML 2.0
This version of HTML was named by IETF(Internet Engineering Task Force) after the primary version of HTML. this version was called HTML 2.0 which was published in 1995 in this edition some new features were added in which "Image tag" was the most important.
HTML 3.0
By this time HTML and the internet had left their mark and both were becoming popular more and more people wanted to join the internet. Therefore due to excessive use of HTML, some complications arose, so the next version of HTML was created which was 3.0 but it was never published.

### HTML 3.2
An organization had already emerged until the publication of HTML 1.0 and the recommendation of HTML 3.0, which is made to work for the HTML language. It is known as W3C("worldwide web Consortium").In 1997 the next version of HTML was published by the W3C. It had many features than both versions of HTML.html document could now be created in more ways through HTML3.2 in this edition Many new attributes were added which were more for his style than the structure of the document. However, by the time, the readers of HTML i.e browsers were very slow. They still did not support all features of HTML3.2,

### HTML 4.0
Now the internet was very popular. More and More people wanted to learn HTML. They started wanting more than HTML.therefore to fill this gap the next version of HTML4.0 was published.
1. Separation of structure and presentation
2. Style sheet
3. Accessibility Client-side Scripting
4. Frames
5. Advanced Tables
the browser who read it had also got some advance and could read most of the features of HTML. This was a major change in HTML

### HTML 5
HTML5 has come along with clean markup and clean code that make it more accessible than the previous version. HTML 5 allows the web developer and web designer to use neater code and remove div tags and replace all the div tags with new HTML 5 elements 

- video and audio. Video and audio are the new tags that allow embedding a video in the website
- header 
- canvas 
- footer 
- nav. The nav element is used for the part of an internet site that links to different pages at the website.

## FOR MORE SUCH ARTICLES VISIT [CodeWithNG](https://codewithng.blogspot.com) NOW
Change to Test Network on Metamask
Tags: metamask, blockchain, solidity, webdev
Published: 2022-03-20 09:21:23

I recently started learning web3 and had to use Metamask. In recent updates of MetaMask, only the Ethereum Mainnet shows by default

![Default Metamask display](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/jze6c8y2n6v1826bnj2i.png)

In development, I need to change to a Test Network not work with the Ethereum Mainnet - until the application gets to production.

Clicking on Add Network shows you the list of all the test network but clicking on it doesn't change the network you are on. You can only Add an external network here - not one of the predefined ones listed.

![Network Page](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/7m333xuxznb72agclksj.png)
 

>## So how do i change my network

Simple, 

- Go to Settings > Advanced
- Look for **Show test networks**

![Advanced Settings Preview](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/utopmgf1tyxlbp5a91ev.png)

- Toggle it ON
![Enabled Show Test Networks](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/3nzhn120skfva97wm509.png) 
 
Viola🥳🥳🥳🥳 Problem Solved. Now you can switch between the Ethereum Mainnet and the Test Network from the dropdown above.

![Updated Metamask dropdown display](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/6aivwyu5zo18ib1h5fw7.png)
 

Simple but can be tricky.

I hope this helps.
A Nice Developer Joke For Today
Tags: jokes, dailydeveloperjokes, watercooler
Published: 2022-03-20 08:00:16

---
title: "A Nice Developer Joke For Today"
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, #watercooler
---

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/5e1259d54c109.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___: Did you here about the witch who was off by two when casting a hex?

___A___: They failed to make the target DEAD and made them DEAF instead!
 -->
Magento Review
Tags: webdev, php, discuss, opensource
Published: 2022-03-20 08:28:44


Magento seems to be a forgotten opensource PHP "eCommerce" programming language due to the rise of WordPress. The idea of creators was to enhance the flexibility and stability of the eCommerce platform. However, the growth of frameworks challenges this open-source and its fame or perhaps is not likely to be heard in most developer conversations.

Let's analyze the dynamics and changes.

Magento is an excellent PHP open-source content management system (CMS) for eCommerce websites. It has eCommerce functionalities such as a shopping cart, product pages, and checkout form. It is free to use and has fantastic themes to select for your website. I believe it is the best open source if you want to get your hands dirty on code.

**The dynamics**

It is still evident that Magento would be discussed regarding the selection option of eCommerce storefronts. I believe many businesses will somewhat still opt for Magento because of scalability.

However, Magento has the frustrations of performance and speed. Performance seems to be the biggest frustration with little interaction I have with Magento developers. The reasons for these challenges include;

- Extensions and modules problems

- Caching sensitivity

- Javascript and CSS nightmare

- Web hosting

- Compilation problem

- Admin notifications

- Cookie limitation time

- Spam emails

- Slow display of products

These challenges are the most common errs that most Magento developers and store owners face. Improving the version may be the simplest way to solve these problems, but is it reasonable to update the version to avoid these problems if it is open-source like any other framework?

I would not deny how the codes are scalable and unique, but it needs a proficient coder to structure or restructure them. I believe the number of developers proficient with Magento is scarce, making it lucrative if you are an existing Magento developer.

We can not dispute the rise of WordPress. Storefronts owners want their eCommerce done within a few days, and WordPress may require purchasing plugins and themes and paying a web designer to do the job. The constant need to re-learn Magento may lead most beginners to just switch to WordPress.

**The future**

Magento would definitely grow. However, addressing the common "difficulties mentioned above would perhaps attract more coders to learn or use Magento. This open-source seem to fit in creating big e-commerce sites alone. An example is Jumia which is a leading eCommerce site in Africa. WordPress has come in and works perfectly for small business owners.

I believe if the inventors consider business factors and improve future versions, it will be the first choice for most developers. Currently is hard to find a PHP developer talking about it. Perhaps it is limited to eCommerce creation, but it should be among the leading in web conversation.

What do you think about Magento? leave a comment
Week V Experience task force 5.0
Tags: coa, awesomity, coding, webdev
Published: 2022-03-20 08:27:44

“People should pursue what they're passionate about. That will make them happier than pretty much anything else.’’ Elon Musk said.😎
As Elon said l am the happiest person because of the task force. Having enthusiasm is more curiously when you’re in your environment’s enthusiasm. As the story of Five weeks passed in the task force.
Week five was more interesting where I learned a lot of things, especially technical-wise. We were building our App endpoints (API) as a Backend team, indeed in case we are two in a back-end team which is kinder a challenge but we oversee to work together and as a team of cause, we are stepping to another level with GraphQL Which is a query language for APIs.
Indeed on the off chance that it’s a modern thing in us but we have as of now done a few inquiries about for presently we have done with a few endpoints where a full web App must be completed at the conclusion of this week. Something else l learned this week was self-organization, I used to know that self-organization is about being on time and doing work given at the perfect time but l found that Is more than that as in a team once everyone did his/her task it makes a big impact to the project given.
We also saw more about Design thinking which is a non-linear, iterative process that teams use to understand users, challenge assumptions, redefine problems and create innovative solutions to prototype and test. It was the best experience since I didn’t know it before, and one of the tools that will help me in my career as a software engineer.

All in all, this was yet another educational, insightful, and fun week and I can't wait to see what comes next.🤩