DEV Community: Prakirth Govardhanam

⚖️FROM Burn-Out TO Balance-Out (2/4)

Prakirth Govardhanam — Wed, 15 Jan 2025 16:22:40 +0000

Handling Anxiety and Learning to De-Stress 🤹

Last week I shared my journey on learning and building a web app and shifting immediately to building a mobile app without a break!

Of course, I was coerced by my situation to eventually take that 1-week detox break. During that week, I just did what I usually do to relax such as reading a book, listening to a podcast, watching TV, playing with my cats, going for a walk, working out...

Unfortunately none of them worked!

All these activities somehow triggered the anxiety center of my brain, since all of these activities were wired into my daily working life and didn't feel like I was taking a break.

The one thing which did break me out of my anxiety and stress was trying out a new hobby, Cooking!

The main reasons that Cooking as a hobby helped me out were :

I cooked a long long time ago, like 7 years ago.
I had to strain the brain's mental capacity to understand the recipe (it was in Finnish) without using the translator.
I prefer being meticulous with taste, texture and dicing ingredients. Hence, consciously focused on keeping the body posture aligned for performing the meticulous activities.

Overall, picking up Cooking as a hobby after a long time helped me in 2 ways :

my wife was happy! 👩
my brain thanked me for the mutual benefits! 🧠 💞

Hope this helps someone riding on their infinite anxiety spiral as a self-learner.

Cover image - dish I made as part of the break, "Couscous salad with feta cheese and grilled veggies"

Cheers and have a good one everyone! 🥂

⚖️FROM Burn-out TO Balance-out (1/4)

Prakirth Govardhanam — Thu, 09 Jan 2025 13:09:04 +0000

TLDR As part of learning MERN stack, learnt JavaScript, mastered full-stack concepts and built a full-stack web app for Symptom Checker in 6 months. Then tackled the mobile app version of the Symptom Checker, but got overwhelmed by new technologies. Took a break and refocused. Leveraged my existing backend, and used AI tools to accelerate development. Learned the value of strategic planning, efficient tool utilization and a growth mindset.

Overview 👀

Planning, building and presenting the full-stack web app for Symptom Checker application in September 2024 was a long journey.
It was a 6-month journey of learning JavaScript, starting off with MERN stack and learning the core technologies and concepts from Full Stack Open.

All of this while building learning projects, updating CV, applying jobs and networking.

Right after, I jumped onto my next project - React Native mobile app development for Symptom Checker application.
This rush was induced by the desire to finish the professional courses of the Vocational Degree within 2024.

I started with planning out the requirements for building the app with my current knowledge.
I was not at my peak performance so I started losing bearings and drifted down the rabbit hole! Here are the wonders I saw :

Challenges 💪

Got overwhelmed with tools and technologies that would be required to build the React Native mobile app (TypeScript, GraphQL)
Assumed that I would need a new backend and could probably use Backend-as-a-Service platform (Supabase, Appwrite) for easing this process.
However, learning TypeScript, GraphQL, BaaS SDKs AND building the mobile app prootoype within a month was overwhelming, to say the least!

Although these tools & technologies were a good list of items to learn as a Software Developer, BUT the project did not need that.

Solutions 🔮

To come back to my senses from the overwhelming thoughts, I took a week off to reconcile my thoughts and actions.

After that little break, everything started to fall in place. I figured that :

React Native components and their implementation were very similar to React. Hence, I could implement the components with JSX for now with thorough JSdocs for future-migration to TypeScript.
Refer TypeScript documentation to know how
Node.js Backend that I developed with such dedication by following Layered Architecture and security principles for scalability could also be extended to be used as a Shared Backend for both the Web Client and Mobile Client of Symptom Checker application.
Check out Node.js Shared Backend
Finally, after implementing 1 & 2 from above, I was able to handle the deadline under pressure by :

learning key concepts of React Native, React Native Paper, React Navigation from their documentation,
confirming key takeaways by using assistance from Claude(3.5 Sonnet),
generating React Native Components by training Pieces Copilot on developed React Components for Symptom Checker web app,
refactoring the generated React Native Components for expected functionality,
adding error handling and edge case handling,

This approach is definetely questionable but consider that I have build the same components in React from scratch.
Now I am validating and reiterating the generated component structure in React Native for faster development.
Check out React Native mobile app development

Key Takeaway 🔑

Never stress yourself out to reach the summit at one go! Relax and rejuvenate between short-term goals. Mind becomes sharper, Goal becomes clearer :)

That's all for this post.
In the next upcoming posts, I will share about how I approached each challenge as I dived down the rabbit hole!

Cheers and have a good one everyone! 🍻

Prepping for Healthcare Software Development: Seeking advice from Seasoned Pros

Prakirth Govardhanam — Mon, 10 Jun 2024 11:30:56 +0000

About Me

I am a biomedical engineer transitioning into software development. As someone with a background in healthcare and a keen interest in coding, I'm eager to learn from experienced developers who have worked on healthcare applications.

My Questions

What was the last healthcare application you developed and pushed into production?
During any phase from design to production, what were the top five challenges or problems you faced?
How did you overcome or address those challenges?

Why I'm Asking

As I prepare to embark on my journey as a software developer in the healthcare sector, I believe that understanding the real-world challenges and experiences of seasoned professionals in this domain will be invaluable. Your insights and lessons learned can help me better prepare for the unique demands and considerations involved in developing healthcare applications.

I appreciate you taking the time to share your experiences and perspectives. Your responses will provide me with a more comprehensive understanding of the landscape and equip me with the knowledge to navigate potential challenges more effectively.

Thank you in advance for your valuable contributions!

Credits

Image by Leelo The First from Pexels

Backend Testing - exciting😀 yet confusing 🤔

Prakirth Govardhanam — Fri, 24 May 2024 13:55:29 +0000

Background

I am trying to learn MERN stack in 150 Days, about which I posted a while ago. In this series posts, I will be sharing What and How I have been learning.

MERN - 150 Days Challenge

Prakirth Govardhanam ・ May 13 '24

#webdev #beginners #learning #discuss

I am open to feedback to make this post better for readability/content quality.

DAY 17/150 ⏳

Today, I have brief summaries of concepts which were either unclear/unknown to me, until now. 🏄
In the below sections, I share the challenges I faced with Context, Reason and Solution wherever relevant.

Challenge 1 - Backend Testing fundamentals

Context : Backend-testing using node:test, node:assert and supertest.
Reason : Completely new topic and zero-experience from previous projects
Solution :
- After every topic in each section of Part 4, practice tests for 'Notes App' in a different context. For example on the current project in Part 4 exercises, 'Blogs App'
- Seek coding assistance from GitHub CoPilot
- Read through example tests from documentations

Challenge 2 - HTTP status codes

Context : HTTP Methods use similar status codes

Reason :

HTTP Method	Response Status Codes
GET	200, 304, 400, 404, 500
POST	200, 201, 400, 403, 404, 500
PUT	200, 204, 400, 404, 409, 500
PATCH	200, 204, 400, 404, 409, 500
DELETE	200, 202, 204, 400, 404, 500

Common status codes happen because HTTP method can have multiple response status codes because the outcome of a request can vary based on different factors.
- 200 OK: The request has succeeded.
- 400 Bad Request: The server could not understand the request due to invalid syntax.
- 404 Not Found: The server could not find the requested resource.
- 500 Internal Server Error: The server encountered an unexpected condition which prevented it from fulfilling the request.

Challenge 3 - Data re-initialization in test DB using `beforeEach`

Context :
- For Testing purposes, Test-database needs to be re-initialized before each test for executing assertions successfully.
- However, due to differences in the order of execution of the Promise the data can be initialized in different ways.
Reason : Depends on the sequence preferences, if any, of execution of Promises
Solution :

Using for loop for control over execution order of Promise

    beforeEach(async() => {
        // executed in no specific order
        for(let blog of helper.initialBlogs){
            let blogObject = new Blog(blog)
            await blogObject.save()
        }
    })

    // tests to verify HTTP methods 
    ...

using Promise.all method to allow the completion of every Promise in the registered order

    beforeEach(async() => {
            // executed in specific order promises registred
            await Promise.all(helper.initialBlogs.map(async (blog) => {
                let blogObject = new Blog(blog)
                blogObject.save()
            }))
        })

        // tests to verify HTTP methods 
        ...

most ideal method, using mongoose built-in methods for insert and delete

        beforeEach(async() => {
            await Blog.deleteMany({})
            await Blog.insertMany(helper.initialBlogs)
            })

            // tests to verify HTTP methods 
            ...

Challenge 4 - Password Hashing fundamentals

Context : Hashing passwords (manually) using external libraries
Reason : Obviously, user data such as passwords must be encrypted, hence an enhanced level of encryption ensures user security
Solution : In the current context (FullStackOpen-core-part4), for user administration in saving blog posts, we are using bcrypt to ensure password hashing through Salt Rounds, as simplified below.
- Purpose : Salt rounds are used to 'thwart brute force attacks' by making the hashing process slower.
- How It Works :
  - Number of salt rounds is the exponent in the calculation of how many times the hashing algorithm is executed.
  - More rounds = more hashing iterations,
  - Brute force attacks slowed down and more secure.
- Example : If you choose 10 salt rounds, the algorithm will run 2^10 (or 1024) times.
- Balance between Security and Performance :
  - Higher salt rounds increase security but also make the hashing process take longer.
  - The cost of increasing rounds on 2 GHz core :
```
    rounds=8 : ~40 hashes/sec
    rounds=9 : ~20 hashes/sec
    rounds=10: ~10 hashes/sec
    rounds=11: ~5  hashes/sec
    rounds=12: 2-3 hashes/sec
    rounds=13: ~1 sec/hash
    rounds=14: ~1.5 sec/hash
    rounds=15: ~3 sec/hash
    rounds=25: ~1 hour/hash
    rounds=31: 2-3 days/hash
```

Challenge 5 - Process Flow between Backend-Database to Implement new Feature

Context :
- In MERN, if every new concept is implemented from the granular level, unlike Django, the sequence of operations to know are essential.
- In current context, we use MongoDB-mongoose for establishing backend-database communications
- If a new table/collection is introduced to implement a new feature, such as user administration, then the sequence of actions for an efficient process flow is as shown below.

Challenge 6 - Generating JSON Web Token

Context : What is included in 'process.env.SECRET'?
Reason : For user authentication, a jsonwebtoken (JWT) must be generated
Solution :
- Any string, preferably auto-generated as a cryptic string
- Using node built-in library for auto-generating a cryptic string as follows:
```
    const crypto = require('crypto')
    crypto.randomBytes(32).toString('hex')  // SECRET
```
- NEVER save it in the source code. Generate in the terminal. Save it in .env

Challenge 7 - Authorization Header and Authentication Scheme fundamentals

Context : How to retrieve the 'Authentication Header' value for implementing tests with backend API using Postman/REST Client ?
Reason : To authenticate the user when a POST request is generated

Solution :

HTTP request has Authorization headers in the format - <auth-schemes> <auth-parameters>
There are multiple <auth-schemes> (Authentication Schemes) available in a HTTP request Authorization header.
Most common ones are - Basic, Bearer, Digest

Feature	`Basic`	`Bearer`*	`Digest`
SECURITY	Credentials sent as `base64` encoded (plain text)	Credentials tokenized on server-side and stored on client side. Can be set to expire.	Password saved on server as plain-text/reversibly-encrypted format for verification with hashed-version.
USAGE	Simple, credentials sent with each request	Simple & safe, token sent with each request	Complex due to hashing process
STATE	Stateful, since credentials required for each request	Stateless, request contains credentials-encrypted token to authenticate user for each request	Stateful, random new hashed value different for each request
API Suitability	Only simple authentication, Not suitable for modern APIs	Suitable, specifically for APIs with `JWT`s and Single Sign-On (SSO)	Not Suitable, due to server-side storage

Based on the project (Reading list - Blogs App), the Bearer <auth-scheme> would be suitable for our User Authentication considering its beginner-friendly secure state of tokenizing user access.

Until next time! ✍️
Live Long and Prosper 🖖

Cover Photo by 'Leeloo The First' from Pexels

Hosting platform procrastination 😵‍💫

Prakirth Govardhanam — Fri, 24 May 2024 13:04:33 +0000

Background

I am trying to learn MERN stack in 150 Days, about which I posted a while ago. In this series posts, I will be sharing What and How I have been learning.

MERN - 150 Days Challenge

Prakirth Govardhanam ・ May 13 '24

#webdev #beginners #learning #discuss

Did you ever have to deal with yourself in a similar situation as this ? How did you deal with it ? Let me know in the comments 💬

This is how I dealt with it. 🤹‍♂️

Context

DAY 9/150

Until Part 3 - Deploying app to Internet part of the course, the course was not very challenging.

Reason

I always dreaded deployment. Last I tried I failed.
Then, I mastered procrastinating this particular aspect of Software Development 😐

Obviously, the procrastination comes from my insecurities as a non-traditional Developer, such as :

What if I do something wrong and my code gets deleted ?! 🤨
TMI! Where do I even start ?! 😬

Solution

It took me a whole day to reason with myself and find options which satisfy one simple condition - No Credit Card required
The answer was right in that part of the course - Render

Learnings

Procrastination or Impostor Syndrome is quite common for folks coming from non-traditional backgrounds to Software Development

Deal WITH it. Do NOT give in. 🦾

Sometimes the solution is right in front of You. Just breathe 😌

Along the way, I found some nice aggregated resources 🤩 :

List of services for Web Hosting, Database, File Storage, User Identity and Monitoring

Top Free Services To Deploy Full-Stack Applications (2023) | by Minianter | Medium

Minianter ・ Jan 11, 2024 ・
Medium
List of softwares with free-tiers for Developers

Free for Developers

Developers and Open Source authors now have a massive amount of services offering free tiers, but it can be hard to find them all to make informed decisions.

free-for.dev

Until next time! ✍️
Live Long and Prosper 🖖

Cover Photo by 'Leeloo The First' from Pexels

MERN - 150 Days Challenge

Prakirth Govardhanam — Mon, 13 May 2024 16:04:40 +0000

About Me

Ambitious Software Developer from non-traditional background (Bio-Medical Engineering)
Journey officially and purposefully started on March 2023 with Savon Ammattiopisto (Local Vocational College in Finland)
Self-learning and self-guiding through experiences 🤔
I believe I managed to understand and implement :
- Fundamentals of programming, data-structures and object-oriented programming. Hence, Backend engineering is my favorite part!
- Databases (relational) using SQL syntax was free-flowing. If possible, I would replace English with SQL to communicate with people 😆
- Frontend engineering was smooth but relating components and their functionalities between frontend <--> backend <--> databases was a journey! 🛤️

I wish to deduce my understanding of Software Development and start learning in public based on the advice from this wonderful post from Pieces 🛫

How to Build in Public as a Tech Professional

Pieces 🌟 ・ May 2 '24

I am open to suggestions and collaborations along this wonderful journey! 🤝

🦾 The Challenge

The What

Currently I am learning MERN stack from FullStackOpen, an Open University course from the University of Helsinki, Finland.
My progress so far : FullStack-open-core

About the Course

Course has 7 core parts and 7 extension parts for learning Full Stack Development.
Course is very detailed and gives adequate set of instructions, exercises and material to follow along without any confusion. (sometimes the instructions are so elaborate, that it starts to be confusing! 😵‍💫)

Networking 🕸️ I have heard about this course from a peer and thanks to him, I could plan out the curriculum for my Vocational college degree.🕸️

The Why

I get to learn the most popular tech-stack and start applying for jobs as soon as I have a static portfolio in both MERN and Django 🗽
More importantly, the course has a nice reward if completed as a whole package! Here is my core reason :

To qualify for the "Interview Promise"
- Core course - 7 parts
- Course exam - after completing parts 0-7
- Extended course - 7 parts
- Course project - Full stack project (10 ECTS)

The How

My self-study happens full-time, hence I am able to dedicate 6-8 hours/day for 5 days/week. Based on what I know and what I have (time) so far I believe I can complete the entire course including the course project within 150 Days.
To make myself accountable, I will be posting (1 post/week) my progress and key takeaways from what I have learnt.

Interested ? 🤠

If you are also new and a beginner from a non-traditional background, I would welcome you to join me in exploring MERN stack or any stack together.
Learning together can always be confidence boosting and make the journey less lonelier 😁
Let me know in the comments below. We can connect via Discord 📬

Credits

Cover Image : Photo by Leeloo The First

Document Object Model (DOM) : One Byte Explainer

Prakirth Govardhanam — Fri, 29 Mar 2024 19:47:21 +0000

This is a submission for DEV Challenge v24.03.20, One Byte Explainer: Browser API or Feature.

Explainer

A Tree represents a structure with branches, nodes and leaves manipulated by Nature to change its layout every season. Similarly, DOM represents a web page structure where elements, attributes and text are manipulated by a Developer's genius.

Additional Context

To access and manipulate the DOM content, JavaScript is fundamentally used. React framework with JSX (JavaScript XML) abstracts DOM access through a virtual DOM. Finally, TypeScript provides static typing for advanced capabilities.

Apologies, if the post seems inappropriate in any sense 😥 . This is my first post and my first challenge in the process of becoming part of a Developer community.
This is the summary of what I have learnt from MDN Documentation and discussions with Chat GPT.

Thank you for this wonderful challenge ! 😍

DEV Community: Prakirth Govardhanam

⚖️FROM Burn-Out TO Balance-Out (2/4)

Handling Anxiety and Learning to De-Stress 🤹

⚖️FROM Burn-out TO Balance-out (1/4)

Overview 👀

Challenges 💪

Solutions 🔮

Key Takeaway 🔑

Prepping for Healthcare Software Development: Seeking advice from Seasoned Pros

About Me

My Questions

Why I'm Asking

Credits

Backend Testing - exciting😀 yet confusing 🤔

Background

MERN - 150 Days Challenge

Prakirth Govardhanam ・ May 13 '24

DAY 17/150 ⏳

Challenge 1 - Backend Testing fundamentals

Challenge 2 - HTTP status codes

Challenge 3 - Data re-initialization in test DB using beforeEach

Challenge 4 - Password Hashing fundamentals

Challenge 5 - Process Flow between Backend-Database to Implement new Feature

Challenge 6 - Generating JSON Web Token

Challenge 7 - Authorization Header and Authentication Scheme fundamentals

Hosting platform procrastination 😵‍💫

Background

MERN - 150 Days Challenge

Prakirth Govardhanam ・ May 13 '24

Context

Reason

Solution

Learnings

Top Free Services To Deploy Full-Stack Applications (2023) | by Minianter | Medium

Minianter ・ Jan 11, 2024 ・ Medium

Free for Developers

MERN - 150 Days Challenge

About Me

How to Build in Public as a Tech Professional

Pieces 🌟 ・ May 2 '24

🦾 The Challenge

The What

About the Course

The Why

The How

Interested ? 🤠

Credits

Document Object Model (DOM) : One Byte Explainer

Explainer

Additional Context

Challenge 3 - Data re-initialization in test DB using `beforeEach`

Minianter ・ Jan 11, 2024 ・
Medium