#coding blog

[bunnydevs]

[zenioynx]

blog/first-pwa-test

Recently, in my spare time, I’ve found myself drawn to yet another project idea — something new I’m curious about and excited to explore.

I’ve been feeling a bit stuck with my three main projects. Progress has slowed, and instead of forcing it, I’ve shifted focus — again — to something different. This time: Progressive Web Apps (PWA).

The concept is simple enough: by adjusting the structure of a standard web app, you can make it behave more like a native app. PWAs can be installed directly onto your phone or tablet, and in many cases, they’ll still work offline. I’ve seen this behaviour in real life — certain sites prompt to “install” themselves, and I always wondered how that worked.

So I tried it.

I built a small test site, deployed it to Netlify, and then visited the site on my phone. It prompted me to add it to my home screen — and it worked. I turned off Wi-Fi, reopened it, and the site still rendered. That was the confirmation I needed.

Now that I’ve seen the flow work end-to-end, I want to apply this to a real project — one I’d genuinely like to use offline. Realistically, the project would work best as a native mobile or tablet app. But I don’t have the skills for that yet, and the PWA approach is the closest I can get for now.

Hopefully, I’ll begin proper work on it today.

[codemom]

INTRODUCTION

Hi everyone!

I'm excited to share that I'm starting a new chapter by diving into fullstack web development. In just a couple weeks, I'll be embarking on courses to learn HTML, CSS, JavaScript, Python and more...

As a stay-at-home mom of one, I'm thrilled for this opportunity to expand my skills. I've always loved learning new things, whether it's knitting, gardening, or coding. Now I get to take my self-education to the next level!

My goals are to stay focused, avoid burnout, and find a healthy balance between studying and family. I know there will be challenges ahead, but I'm determined to succeed.

I plan to document my coding journey here, share tips, and connect with others in the field. Web development has always fascinated me, and I can't wait to become part of this community. Wish me luck!

[codomars]

Day 30 — 35/ 100 Days of Code

I learned how to handle JavaScript features (default parameters, spread, rest, and destructuring).

And I finally reached the DOM chapeter, 'The Document Object' which contains representations of all the content on a page. I'm still discovering its methods and properties.

So far, I've learned about the most useful ones: getElementById(), querySelector, changing styles, manipulating attributes, and the append method.

I'm doing some silly practice exercises just to get more familiar with the DOM methods. The more I progress in my course, the more fun things seem to get. I'm really excited to start building stuff with code and combining HTML, CSS, and JS all together.

[lostlibrariangirl]

August 14, 2024

227/366 Days of Growth I saw the recent video from Cyb3rMaddy, and that made me think about projects visiblity for Cybersecurity https://youtu.be/oxfb-yMC6z0?si=n5HVxksyAMSH8g1S Struggling here thinking about to make videos about my own Cybersecurity projects, and studies, as I don't know if I can find a proper time to do it. However, what I CAN do is to produce more texts for my Hashnode blog, which I conduct professionally. It looks like the best way to create content for now ( ๑‾̀◡‾́)σ"

[hidingundermicroscopes]

[ravenncouture]

[flowersfromunderground]

[luv4elaina]

[moonbelle444]

[zenioynx]

blog/developer-vs-engineer

I don’t love Software Engineering.

I trained as a Software Developer. That’s what I enjoyed then, and it’s still what I enjoy now. My previous role was Web Developer. I liked it. My current title is Software Engineer — and I don’t enjoy the “engineering” part.

I don’t aspire to architect systems. I’m not aiming for infrastructure mastery or microservice design. I like building things and then moving on. My brain works in tasks. In quests. A feature is a problem; I solve it and move forward. That’s the rhythm I understand.

When the conversation shifts to CI/CD pipelines, scalability, deployment pipelines, I disconnect. It’s not just disinterest. There’s an expectation in tech that every developer should eventually care about “the bigger picture.” But not everyone wants to be two roles in one.

I prefer tickets that ask for new components, new features, fixes with visible outcomes. That’s where I focus. That’s what feels good. I see other engineers talk deeply about pipelines and system stability — and I respect it — but it’s not for me.

What I enjoy is turning design into reality. From idea → interface → interaction. That’s the role I want.

And that’s why I prefer being and being called a 'Software Developer'.

[rocknrollangelsblog]

[vilenceviolins1105]

this months vibe

[livgrl22]

Me n who??

[cherryst4rg1rl]

Me for real I love him so much

[lostl1sbons1ster]