Average Developer

6 Years Coding, 0 Things Shipped

roshan shrestha — Fri, 13 Feb 2026 14:44:42 GMT

"Talk is cheap. Show me the code." — Linus Torvalds  

How can you call yourself a good painter if you have not made any painting in life. you can’t be good artist just by reading books or passing comments on other paint works. If you think you are good artist, just show me your work. period.

6 years in coding.
5 different job switch.
0 interview had to be given, thanks to referral and connections.
0 earned from my project cause,
0 live software/app.

  Well, i am on that trap. Everyday i try to convince myself that i am the good developer, but i have nothing to show for. The funny thing is that, i convinced my self so hardly that i am the good developer, that i also went on teaching other to code? Like hello?? I don’t think i ever wanted to be teacher, maybe i was just looking for a escape? or maybe i was just looking for the validation;

I can’t name a single thing i have made in 6 years of my coding journey. Never created anything for me, or for anyone i love. Never earned singled dime from any of my project.

Here is a thing though, i love coding. i have been coding ever since i got my first laptop. I still remember spending multiple night trying to fix bugs, trying to make games or anything cool. I believe those were the final moments i ever had fun coding. Once i started working at office, once the first pay check arrived, i think i started to live off paycheck to paycheck.
My curiosity was sidelined by the family debt, “apps to build” never escape the paper, day one became one day. The thing i thought i will do on my free time, now required too much motivation to start.  Slowly i priority shifted, and working just enough to get paid became my new normal. Guilt never stop creeping though but;

I got comfortable.

Not happy, just comfortable. i didn’t had to make my own app, thanks to stable income. i couldn’t quite my job to start my own company, thanks to family debt.  So i did what every comfortable man does — stay in comfortable. Live my life of paycheck to paycheck. Maybe i overthink to much what other will say? There is a loud voice somewhere in me constantly remind me with “What others will think”. 

“Oh you are going to build this app? bruh, anyone can build it. its nothing special”  “Oh you think its the best solution? even a junior student can come up with better solution”
“Damn, can’t solve even this DSA problem? Who hired you?”

  Mind you these are not something other told me, its my brain convincing me to think this stuff.

That has been my biggest regret so far. Not that i don’t have my own company or my own app, just that i didn’t have courage to fail.  i failed to fail faster now all that is left is shy, under confident and too much comfortable person who regrets every decision.

Now i am leaving that version of myself behind. I am marking this blog as the first step to get uncomfortable. In fact i will just publish this blog without reading it twice. it will be like note to me for future.
I will not expect anything in return. I will just do cause i wanna do it. Keep building and publishing for myself.  May be next year, i will love the version of myself.

"Everything you want is on the other side of fear." — Jack Canfield

Gogogaga, Learn Git like 5 years old

roshan shrestha — Sat, 29 Nov 2025 12:04:21 GMT

This command is just to give some description about what you did so far, this will help camera to remember even if you check it after a year. It can tell you exactly what, when, who was doing this.

Now you have the exact copy of your original work, even though its completely empty

» But wait a minute, you notice something different in the copy

Congratulation. You created the first copy with version number. The hash you see is unique to your work, so it won’t repeat ever.

So far, the above is our state, we have 1 original work we were doing and on the backup, we have 2 copy with different state version.

But opps, you did some mistake while making the another shape, and unfortunately you can’t erase it anymore.

This is where the git backup will be useful. You can just pull the copy and start working again, and delete the mistake original file, you can remove the original mistake file as we won’t need that again.

Everytime we any changes and write,
git add all
& git commit -m “Message” it just create another version that we can use later and modify whenever we want.

thats why, once you use the git. You don’t have to worry about the versioning.

Alright, thats the start of the git. Alot to cover, see you kids on the next blog!
Gogogaga byee

Quick setup the Bootstarp and Laravel 9 in few steps 🚀

roshan shrestha — Tue, 22 Nov 2022 10:44:29 GMT

1) Project Setup:

I am going to use the composer to setup everything here.

composer create-project laravel/laravel simple-project-name

This will basically setup the new laravel project in your machine. Once the setup is complete, cd simple-project-name to move inside your project and follow below code.

2) Setup laravel ui inside project

composer require laravel/ui

This add the laravel/ui package inside your project. We will further use this ui package to add the bootstrap.

So far so good , Hopefully you are not facing any issue till now. Moving on,

3) Setup the bootstrap (5) using php artisan

php artisan ui bootstrap

Before we move on to another steps, make sure you have nodejs setup on your machine.

4) Setup up dev dependencies using NPM

npm install

and build everything

npm run build

5) Update the vite.config.js

Add the resolve: {} field just below the plugins inside the vite.config.js,

 resolve: {
        alias: {
            "~bootstrap": path.resolve(__dirname, "node_modules/bootstrap"),
        },
    },

Make sure to import the path at the top

So now your vite config file should looks something like this:

import { defineConfig } from "vite";
import laravel from "laravel-vite-plugin";

import path from "path";

export default defineConfig({
    plugins: [
        laravel({
            input: ["resources/sass/app.scss", "resources/js/app.js"],
            refresh: true,
        }),
    ],
    resolve: {
        alias: {
            "~bootstrap": path.resolve(__dirname, "node_modules/bootstrap"),
        },
    },
});

6) Update the app.js file inside the `resource/js` folder

Just import the resource/scss/app.scss file inside the resource/js/app

so now your app.js file should look like this

import "./bootstrap";
// add this like
import "../sass/app.scss";

7) Now finally include bootstrap in your blade template

@vite(['resources/js/app.js'])

My app.blade.php looks like this





  
  
  
  Article App
// New like added here
  @vite(['resources/js/app.js'])

Everything is now done, just make sure the restart the server by doing

php artisan serve

And rebuild the npm package by

npm run build

Or or or, just use the CDN if you want to quickly start.

Byeeeeeeeee 🍻

Easy Form validation with YUP (+ Formik) in react (For beginners)

roshan shrestha — Wed, 05 Oct 2022 14:36:11 GMT

We just need 3 things to work, React , Formik & YUP (Obviously). 🤦

I will be assuming that you already setup the react and just looking something for the validating the form.

React Js:

Just incase if you haven't, here is the link to setup the react link. 🔗

Formik:

Setting up the Formik is also dead easy,
just use the NPM or the YARN to install the formik on your project.

npm: npm install formik --save
yarn: yarn add formik

Now we need to setup the form, for that we need the Formik.
We can either useFormik hooks or directly import the Formik.

// by implementing useFormik() hooks
const formik = useFormik({
     initialValues: {},
     onSubmit: values => {}, ...
   });

or directly using the Formik as the form, more classical approach per say,

// using Formik as the Form.

I will be using the formik hooks for this tutorial, feel free to use whatever you want. Below we have the very simple Form made from the formik.

import React from "react";
import { useFormik } from "formik";

export default function App() {
  const formik = useFormik({
    initialValues: {
      email: ""
    },
    onSubmit: (values) => {
      // simple code
    }
  });
  return (
    <form onSubmit={formik.handleSubmit}>
      <input
        id="email"
        name="email"
        type="email"
        onChange={formik.handleChange}
        value={formik.values.email}
        placeholder="Email"
      />

      <button type="submit">Submitbutton>
    form>
  );
}

Output:

YUP

Finally, lets add the YUP validation on the form.
Installing yup on the project using npm and yarn:
npm install yup or yarn add yup

For the sake of easiness, Let's say we want to add the validation where email must not be empty, or Required validation on email field.

First, import the YUP package where your code is, for me i will import on the code above.

import React from "react";
import { useFormik } from "formik";
// import like this
import * as yup from "yup";

We need the create the validation schema, which is also very simple.

import React from "react";
import { useFormik } from "formik";
// import like this
import * as yup from "yup";

const formSchema = yup.object().shape({
  email: yup.string().required('Required'),
 // This will make sure that the email is string,
 // and value must not be empty.
});

You can put any error message inside the required("message-to-show-on-error")

Now all we have to do is link the yup schema and the formik form

import React from "react";
import { useFormik } from "formik";
// import like this
import * as yup from "yup";
const formSchema = yup.object().shape({
  email: yup.string().required('Required'),
 // This will make sure that the email is string,
 // and value must not be empty.
});
export default function App() {
const formik = useFormik({
 initialValues: {
   email: ""
 },
// >>> Link schema here <<<
 validationSchema: formSchema,
 onSubmit: (values) => {
   // simple code
 }
});
return (
 <form onSubmit={formik.handleSubmit}>
   <input
     id="email"
     name="email"
     type="email"
     onChange={formik.handleChange}
     value={formik.values.email}
     placeholder="Email"
   />
   <button type="submit">Submitbutton>
 form>
);
}

Done! thats it, we have included the yup validation with formik. Just a small problem , how would we know if we have the error? Cause right now we don't have any mechanism to display the error message. And my friend, that is also super simple.
Simply add the following code where you want to see the error message, and it will work like charm.
```
{formik.errors.email}
```

Final code will look something like this 👇

import React from "react";
import { useFormik } from "formik";
import * as yup from "yup";

export default function App() {
  const formSchema = yup.object().shape({
    email: yup.string().required("Required")
  });
  const formik = useFormik({
    initialValues: {
      email: ""
    },
    validationSchema: formSchema,
    onSubmit: (values) => {
      // simple code
      console.log(values);
    }
  });
  return (
    <form onSubmit={formik.handleSubmit}>
      <div>
        <input
          id="email"
          name="email"
          type="email"
          onChange={formik.handleChange}
          value={formik.values.email}
          placeholder="Email"
        />
        <br>br>
        <span>{formik.errors.email}span>
      div>

      <button type="submit">Submitbutton>
    form>
  );
}

Output:

With Error

And obviously looks ugly, which can be fixed with simple css/ styling.
Congratulations! 🎉🎉 you have successfully used the formik and yup validation.

Yup is super powerful, we can do all sorts of stuff like:

email: Yup.string().email('Invalid email address').required('Required'),

To check for the valid email input + must not be empty

firstName: Yup.string()
       .max(15, 'Must be 15 characters or less')
       .required('Required'),

To check for the non empty firstname field + firstName length of 15 character

age: yup.number().required().positive().integer()

To check if the age is positive number + non empty

I will leave the example code here: https://codesandbox.io/s/vigilant-lamarr-fhscbj?file=/src/App.js:0-817

Have fun experimenting on it. 👨‍🔬

Byeeee 👋👋👋👋👋