#Front-end Web Development Project

[worldexploer]

Best 20's Front-end Language for Web Development

In the ever-evolving landscape of web development, choosing the right front-end language is crucial for crafting engaging and dynamic user interfaces. With a myriad of options available, it can be challenging to pinpoint the best tools for the job. In this blog, we’ll explore the 20 best advanced front-end languages that cater to the diverse needs of web developers. Let’s dive into the world of…

[swifttrinitychronicle]

Best Web Development Course in Phagwara

Join at Tech CADD for the best Web Development course in Phagwara, Punjab! Master skills to create dynamic websites and applications!

[hindintech]

Frontend Projects Ideas

ADVANCED

1. E-commerce Website

2. Social Network

3. Online Learning Platform

4. Music Streaming Service

5. Real Estate Listing

6. Project Management Tool

7. Chatbot Interface

8. Job Board

9. Weather Forecast with Al

10. Stock Trading Platform

11. loT Dashboard

12. Voice Assistant Interface

13. Expense Report Generator

14. Augmented-Reality App

15. Interactive 3D Graphics

16. Blockchain Explorer

17. Machine-Learning Dashboard

18. Language Learning App

19. Financial Planning

20. Astronomy Viewe

[likhithageddam]

Top 20 GitHub repositories to follow today as a Software Developer

Developer Roadmap - Up to Date roadmap to becoming a developer.

Awesome AI Tools - A curated list of Artificial Intelligence Top Tools.

Awesome - Awesome lists about all kinds of interesting topics

Free Programming Books - A huge list of freely available programming books.

Coding Interview University - A complete computer science study plan to become a software engineer.

Javascript Algorithms - Algorithms and data structures implemented in javascript with explanations and links.

Node Best Practices - The Node JS best Practices List

Tech Interview Handbook - Curated coding interview preparation materials for software engineers.

Project Based Learning - A curated list of project based tutorials.

30 Seconds of code - Short javascript code snippets for all your development needs

Free for dev - A list of Saas, Paas and Laas offerings that have free tiers.

Design resources for developers - A list of resources from stock photos web templates to frameworks, libraries and tools

App Ideas - A collection of application ideas that can be used to improve your coding skills.

Build your own X - Master programming by recreating your favorite technologies from scratch.

Real World - Explore how an identical Medium clone is constructed using various frontends and backends.

Public APIs - A comprehensive list of free APIs for use in software and web development.

System Design Primer - Discover how to design large-scale systems and prepare for the system design interview.

The art of command line - Master the command line, all in one page.

Awesome Repositories - A curated list of GitHub Repositories full of FREE Resources.

The Book of Secret Knowledge - A collection of inspiring lists, manuals, cheatsheets, blogs, hacks, one-liners, cli/web tools, and more.

[charile0]

Finding the Perfect Programmer for Your Project: A Guide to Hiring Coders in the UK

In the digital age, finding skilled programmers for hire is critical for businesses looking to build robust websites, apps, or software solutions. Whether you’re a startup or an established company, hiring the right coder can make or break your project. Here’s a guide to help you hire programmers in the UK and ensure a successful partnership.

When you hire a programmer, it’s essential to define your project’s scope and requirements. Are you looking for a front-end developer to enhance user interfaces or a back-end web developer to manage server-side logic? Perhaps you need React developers for a dynamic, responsive website. Once you identify your needs, you can begin searching for web developers for hire through reliable platforms.

For businesses seeking top-notch talent, hiring a UK developer ensures a good balance of technical expertise and understanding of local market trends. You can choose to hire a coder online for flexibility or engage a professional from an agency offering front-end web development services. Platforms like hireacoder and others specialize in connecting you with skilled professionals.

If you’re working on a long-term project, it’s important to hire programmers for the project who are not just technically proficient but also align with your company’s values and goals. Freelance platforms or agencies can help you find coders for hire who meet your specific needs, whether it’s for a quick task or an extended project.

Finding the right website developer for hire doesn’t have to be challenging. With clear goals, a detailed project brief, and a reliable platform to connect with talent, you can build your dream team of developers. If you’re saying, "I need a programmer," start your search today and turn your vision into reality.

[digitalsvibes]

What is coding for kids

[codingquill]

Essentials You Need to Become a Web Developer

HTML, CSS, and JavaScript Mastery

Text Editor/Integrated Development Environment (IDE): Popular choices include Visual Studio Code, Sublime Text.

Version Control/Git: Platforms like GitHub, GitLab, and Bitbucket allow you to track changes, collaborate with others, and contribute to open-source projects.

Responsive Web Design Skills: Learn CSS frameworks like Bootstrap or Flexbox and master media queries

Understanding of Web Browsers: Familiarize yourself with browser developer tools for debugging and testing your code.

Front-End Frameworks: for example : React, Angular, or Vue.js are powerful tools for building dynamic and interactive web applications.

Back-End Development Skills: Understanding server-side programming languages (e.g., Node.js, Python, Ruby , php) and databases (e.g., MySQL, MongoDB)

Web Hosting and Deployment Knowledge: Platforms like Heroku, Vercel , Netlify, or AWS can help simplify this process.

Basic DevOps and CI/CD Understanding

Soft Skills and Problem-Solving: Effective communication, teamwork, and problem-solving skills

Confidence in Yourself: Confidence is a powerful asset. Believe in your abilities, and don't be afraid to take on challenging projects. The more you trust yourself, the more you'll be able to tackle complex coding tasks and overcome obstacles with determination.

[the-nox-syndicate]

SysNotes devlog 1

Hiya! We're a web developer by trade and we wanted to build ourselves a web-app to manage our system and to get to know each other better. We thought it would be fun to make a sort of a devlog on this blog to show off the development! The working title of this project is SysNotes (but better ideas are welcome!)

What SysNotes is✅:

A place to store profiles of all of our parts

A tool to figure out who is in front

A way to explore our inner world

A private chat similar to PluralKit

A way to combine info about our system with info about our OCs etc as an all-encompassing "brain-world" management system

A personal and tailor-made tool made for our needs

What SysNotes is not❌:

A fronting tracker (we see no need for it in our system)

A social media where users can interact (but we're open to make it so if people are interested)

A public platform that can be used by others (we don't have much experience actually hosting web-apps, but will consider it if there is enough interest!)

An offline app

So if this sounds interesting to you, you can find the first devlog below the cut (it's a long one!):

(I have used word highlighting and emojis as it helps me read large chunks of text, I hope it's alright with y'all!)

Tech stack & setup (feel free to skip if you don't care!)

The project is set up using:

Database: MySQL 8.4.3

Language: PHP 8.3

Framework: Laravel 10 with Breeze (authentication and user accounts) and Livewire 3 (front end integration)

Styling: Tailwind v4

I tried to set up Laragon to easily run the backend, but I ran into issues so I'm just running "php artisan serve" for now and using Laragon to run the DB. Also I'm compiling styles in real time with "npm run dev". Speaking of the DB, I just migrated the default auth tables for now. I will be making app-related DB tables in the next devlog. The awesome thing about Laravel is its Breeze starter kit, which gives you fully functioning authentication and basic account management out of the box, as well as optional Livewire to integrate server-side processing into HTML in the sexiest way. This means that I could get all the boring stuff out of the way with one terminal command. Win!

Styling and layout (for the UI nerds - you can skip this too!)

I changed the default accent color from purple to orange (personal preference) and used an emoji as a placeholder for the logo. I actually kinda like the emoji AS a logo so I might keep it.

Laravel Breeze came with a basic dashboard page, which I expanded with a few containers for the different sections of the page. I made use of the components that come with Breeze to reuse code for buttons etc throughout the code, and made new components as the need arose. Man, I love clean code 😌

I liked the dotted default Laravel page background, so I added it to the dashboard to create the look of a bullet journal. I like the journal-type visuals for this project as it goes with the theme of a notebook/file. I found the code for it here.

I also added some placeholder menu items for the pages that I would like to have in the app - Profile, (Inner) World, Front Decider, and Chat.

i ran into an issue dynamically building Tailwind classes such as class="bg-{{$activeStatus['color']}}-400" - turns out dynamically-created classes aren't supported, even if they're constructed in the component rather than the blade file. You learn something new every day huh…

Also, coming from Tailwind v3, "ps-*" and "pe-*" were confusing to get used to since my muscle memory is "pl-*" and "pr-*" 😂

Feature 1: Profiles page - proof of concept

This is a page where each alter's profiles will be displayed. You can switch between the profiles by clicking on each person's name. The current profile is highlighted in the list using a pale orange colour.

The logic for the profiles functionality uses a Livewire component called Profiles, which loads profile data and passes it into the blade view to be displayed. It also handles logic such as switching between the profiles and formatting data. Currently, the data is hardcoded into the component using an associative array, but I will be converting it to use the database in the next devlog.

New profile (TBC)

You will be able to create new profiles on the same page (this is yet to be implemented). My vision is that the New Alter form will unfold under the button, and fold back up again once the form has been submitted.

Alter name, pronouns, status

The most interesting component here is the status, which is currently set to a hardcoded list of "active", "dormant", and "unknown". However, I envision this to be a customisable list where I can add new statuses to the list from a settings menu (yet to be implemented).

Alter image

I wanted the folder that contained alter images and other assets to be outside of my Laravel project, in the Pictures folder of my operating system. I wanted to do this so that I can back up the assets folder whenever I back up my Pictures folder lol (not for adding/deleting the files - this all happens through the app to maintain data integrity!). However, I learned that Laravel does not support that and it will not be able to see my files because they are external. I found a workaround by using symbolic links (symlinks) 🔗. Basically, they allow to have one folder of identical contents in more than one place. I ran "mklink /D [external path] [internal path]" to create the symlink between my Pictures folder and Laravel's internal assets folder, so that any files that I add to my Pictures folder automatically copy over to Laravel's folder. I changed a couple lines in filesystems.php to point to the symlinked folder:

And I was also getting a "404 file not found" error - I think the issue was because the port wasn't originally specified. I changed the base app URL to the localhost IP address in .env:

…And after all this messing around, it works!

(My Pictures folder)

(My Laravel storage)

(And here is Alice's photo displayed - dw I DO know Ibuki's actual name)

Alter description and history

The description and history fields support HTML, so I can format these fields however I like, and add custom features like tables and bullet point lists.

This is done by using blade's HTML preservation tags "{!! !!}" as opposed to the plain text tags "{{ }}".

(Here I define Alice's description contents)

(And here I insert them into the template)

Traits, likes, dislikes, front triggers

These are saved as separate lists and rendered as fun badges. These will be used in the Front Decider (anyone has a better name for it?? 🤔) tool to help me identify which alter "I" am as it's a big struggle for us. Front Decider will work similar to FlowCharty.

What next?

There's lots more things I want to do with SysNotes! But I will take it one step at a time - here is the plan for the next devlog:

Setting up database tables for the profile data

Adding the "New Profile" form so I can create alters from within the app

Adding ability to edit each field on the profile

I tried my best to explain my work process in a way that wold somewhat make sense to non-coders - if you have any feedback for the future format of these devlogs, let me know!

~~~~~~~~~~~~~~~~~~

Disclaimers:

I have not used AI in the making of this app and I do NOT support the Vibe Coding mind virus that is currently on the loose. Programming is a form of art, and I will defend manual coding until the day I die.

Any alter data found in the screenshots is dummy data that does not represent our actual system.

I will not be making the code publicly available until it is a bit more fleshed out, this so far is just a trial for a concept I had bouncing around my head over the weekend.

We are SYSCOURSE NEUTRAL! Please don't start fights under this post

[semiconductorwave]

Hotmail service was founded by Sabeer Bhatia and Jack Smith, and was one of the first webmail services on the Internet along with Four11's RocketMail (later Yahoo! Mail). It was commercially launched on July 4, 1996, symbolizing "freedom" from ISP-based email and the ability to access a user's inbox from anywhere in the world. The name "Hotmail" was chosen out of many possibilities ending in "-mail" as it included the letters HTML, the markup language used to create web pages (to emphasize this, the original type casing was "HoTMaiL"). The limit for free storage was 2 MB. Hotmail was initially backed by venture capital firm Draper Fisher Jurvetson. By December 1997, it reported more than 8.5 million subscribers. Hotmail initially ran under Solaris for mail services and Apache on FreeBSD for web services, before being partly converted to Microsoft products, using Windows Services for UNIX in the migration path.

Hotmail was sold to Microsoft in December 1997 for a reported $400 million (~$705 million in 2023), and it joined the MSN group of services. The sale had been preceded by a major incident in 1997 where all email was lost for 25% of mailboxes. Hotmail quickly gained in popularity as it was localized for different markets around the globe, and became the world's largest webmail service with more than 30 million active members reported by February 1999.

Hotmail originally ran on a mixture of FreeBSD and Solaris operating systems. A project was started to move Hotmail to Windows 2000. In June 2001, Microsoft claimed this had been completed; a few days later they retracted the statement and admitted that the DNS functions of the Hotmail system were still reliant on FreeBSD. In 2002 Hotmail still ran its infrastructure on UNIX servers, with only the front-end converted to Windows 2000. Later development saw the service tied with Microsoft's web authentication scheme, Microsoft Passport (now Microsoft account), and integration with Microsoft's instant messaging and social networking programs, MSN Messenger and MSN Spaces (later Windows Live Messenger and Windows Live Spaces, respectively).

[nymphomaniaa]

something about us [XX] "parasite" — a preview!

summary: this snippet includes part of a scene where the reader sets up a photoshoot for a merch drop featuring the lunch club members.

warnings: slightly nsfw joke

notes: FINALLY finished this monster of a chapter! it's really long because it sets up the current "arc" ending and the next one beginning, so it's... kind of a roller coaster of emotions. below is the only part of the chapter that i felt was fluff-ish enough to include as a lighthearted preview, so make sure to buckle in when you read the actual chapter because... oh boy. it's a lot.

Returning from the postal office (where the Lunch Club P.O. box was now up and running in hopes to receive packages from fans in the future, thanks to you, of course), you held the most important package in your arms three weeks before the start of TwitchCon.  Inside this large hunk of cardboard were the finalized versions of the new merch that you had painstakingly worked on throughout the past spring and summer.  It made it past weeks of reviews, tweaks, and packaging delays, and was finally in your possession, ready to be distributed to the boys so they could finally promote a project that had been on the works for months.

In the basement's common area, you spent most of the morning by yourself, working on setting up a photoshoot area for the group using a backdrop screenprinted with a repeating minimalistic pattern of the official Lunch Club logo — courtesy of a manufacturing company Ryan suggested weeks ago.  By the time you finished setting up the studio lights borrowed from Ted, arranged a couple of chairs on the set, and unpacked the box of merch to take a peek inside, most of the group had finished eating brunch upstairs.

Ted was the first to come down, since he was the one with the camera you would use for the shoot, so he was the first one to be spoiled by the surprise.  "Woah," he's taken aback by the set at first, bewildered by how official you made it look despite the very limited supplies you had.  "This looks really professional for only costing, what, like, two hundred bucks?  And my lights?"

"One hundred and eighty bucks, actually, with shipping and taxes," you snarkily reply, placing your hands on your hips with pride.

Ted lets out a halfhearted laugh, then after fiddling with his camera, hands it over to you.  "Take good care of her.  I've had her since the beginning of film school, she's practically my baby."

You wrap the neck strap around your head gently, and offer Ted a thumbs up while looking down at the camera screen, trying to orient yourself to its panel.  "We're all good to go, I think.  If you could bring all the boys down for me, please?"

"Yes, madam," Ted beams, then suddenly runs up the stairs, shouting, "Alright fellas, get all of yer asses down here right now!  We're aboutta' start rootin' and shootin'!"

A distant drawn out "yeehaw" (likely from Charlie) above you makes you roll your eyes.  These boys never ran out of ways to make noise echo throughout the house.

One by one, each of the Lunch Club members step down into the basement with 'oohs' and 'aahs,' until all of them convene in front of you and are now ogling the box behind you.  Methodically, you explain that you would start with getting shots of each member with their respective pieces of merch, then you would get photos of each of them wearing the group merch, then a few group pictures with all of them together: one set with their group merch, and one set with them wearing whatever they chose to wear.  All of these stills would be displayed on a new merch website that had already been prepared in advance by one of Schlatt's web developers he worked with, but you also intended to get some short candid video clips of them just goofing around and chatting with each other that could be used for a video promotion that could go on their channel.

If all went well, they could start promoting their merch exactly one week from now, and by the time TwitchCon rolls around, the manufacturing company should have enough pieces shipped to Ryan to be sold at the Lunch Club booth.

The shoot went as well as expected.  Each member had their turns modelling their own pieces, with the remaining boys being hypemen behind the camera.  As each session went by, you had a difficult time containing your excitement.  Your art and your designs were on official pieces of merchandise that people all over the world had access to.  You were directing a photoshoot, which granted, you had never done before nor had interest in, but for your first time trying it, each member seemed happy with the results when their mini modelling session was over.

Of course, when Schlatt's turn came around, you took the opportunity to get him in certain poses that accentuated his features.  Partly for you to shamelessly stare at his good looks in your own time, but also partly because you knew a certain part of his audience would be more inclined to support the merch drop if he looked overwhelmingly handsome in his own clothes.  If he could take advantage of you being a woman in his Love or Host show, you could take advantage of him being eye candy in clothes you designed.  More money for the group.  Everyone wins, and the score will be even between you two.

"Let's have you lean a little onto that back leg, and put your left thumb in your pocket...  Then just look at Travis behind me...  No, chin a little more to your right.  There you go.  Intense stare, and…" you directed the tall man, as you kneeled on top of a nearby stool to compensate for his height.

"Can you roll up your sleeves a little, like so the hem goes about an inch below your elbow?  Then just do that exact pose again...  Yep, that's it.  No, stop giggling.  You're serious.  You're calm.  You're serious."

"Sorry." You’re unsure what is so funny, but he stifles his laughter, then settles into the same pose as before.

"Okay, then can I maybe get you on the stool?  Yeah, just sit like you normally would.  Push your right knee outwards a little more, then let's get your elbows resting on your knees.  Yep, and then clasp your hands together, and lift your head and look towards Trav, but not too much?  You're trying to showcase your hat, so only let your eyes look up at him, not your entire head.  Chin to the right.  Perfect."

"I feel like you're shooting a fucking porno of me," he tries to contain his laughter.  "It's like you're recreating that one face reveal photo of me looking up at the camera,"

"Just trust the process, J," you roll your eyes as the shutter snaps a few more times when he closes his mouth.  "Here, you wanna look?"

You open the camera's preview gallery and show the rest of the boys first, who burst into a roar of overexaggerated gasps and whistles.

"Holy shit, he's hot!" Charlie moans, pretending to fan off his face.

Schlatt pulls himself off of the stool and meanders towards you, reaching a hand out to ask for the camera.  Once you give it to him, and he clicks through the photos, he raises his eyebrows in approval.  "Holy shit, I am hot."

"You sure are, handsome.  Now get back in that damn chair, we have more porn to shoot," you tease.  He shakes his head, chuckling as the boys keep cheering him on, chittering in excitement for his newfound confidence after seeing himself on camera.

read the entire chapter here, or start from the beginning here.

[gabessquishytum]

Dream's a software developer (I could see either as an architect for that large-scale view mentality or as the Senior level dev that keeps getting asked to move into management type positions and just straight up refuses because he's been doing code happily for the past fifteen years and doesn't plan on changing that now).

He enjoys his job enough. He likes computers and code. It functions exactly as told (for better or worse) and appreciates the straightforwardness of it all. He's a bit insufferable to work with, but if you have an issue, he'll readily help (just be prepares for critiques on your code in the process).

Hob works at the same company as Dream, but as a front-end dev. The work he does for his day job is kinda boring. All standard corporate style web design. No fancy scripts or fun colors. But in his spare time, he weaves Javascript and CSS like a wizard and creates magical, animated scenes across the page. Would it be easier to just make a video and play it on the page instead? Sure, but where's the fun in that?

Dream and Hob get paired together on a small side project for work. Hob does the front-end work, Dream does the back-end. They get on each other's nerves at first, until Dream spots Hob tinkering with his personal code on their lunch break and is honestly a bit in awe. He's found code beautiful in its own right (the way one appreciates a well-oiled machine) but he's never seen it wielded in such a fashion before. This is the moment he falls just a little bit (read: a lotta bit) in love with Hob. He was already starting to fall for that endless charm and wit of his anyways.

The company hits the first quarter of the New Year and with it come layoffs. Hob gets fired along with some other devs from Dream's same team (a younger pair of devs: Matthew and Jessamy). A fellow named Will comes along to help Dream finish the project in Hob's stead and Dream hates every moment of it. He misses Hob, more than he ever thought he would.

So, in an impulsive rush of anger and longing, he quits the company because how dare it toss someone as good as Hob Gadling out the door without a thought? He's halfway to the café he and Hob had started frequenting together when he realizes that he's just thrown away a career fifteen years in the making. But when he finally gets to the café and sees Hob tapping away on his laptop, he knows he's made the right choice.

Dream slides into the seat across from him and proposes that they build something wonderful together. So they create a small business of their own. They become a freelance web dev team (and steal Jessamy and Matthew as well) and with their skills combined, they take off. It's not huge, but for their size, they're incredibly popular. And Dream's certain he's never enjoyed his work more than when he's working beside Hob.

Later on, Hob proposes to Dream via a custom website with the most beautiful web animations he's ever seen before. And of course, he says yes.

(If you're curious about what inspired this, here's the website: http://www.species-in-pieces.com)

This is such a good concept for a story!!! I really really love aus where Dream and Hob are coworkers. Dream being the grumpy, awkward guy who hides behind his coffee mug while Hob is the popular, chatty one who tries to get Dream involved in fun office activities or socialising after work - it makes so much sense to me.

And Dream quitting his long-term dream job because he's mad that genuinely talented people have been laid off? I love it. Dream just has this inate appreciation for hard work and good art, and that's exactly what Hob (and Jessamy and Matthew) do. How dare the stupid company not understand that they're firing people who deserve to thrive and grow in an environment which actually appreciates them? Everyone is shocked that Dream has quit (not only that, he sends around an email to everyone in the company from the ceo all the way down to the work experience guy, outlining exactly why he quit) because he seemed to be the type to play by the rules and never leave his comfort zone. Apparently, Hob has really helped him bloom into a much more confident person, able to express his principles and strive for better.

And Hob isn't surprised, because he always knew that Dream had the courage, talent and ambition to strike out on his own. Maybe he just needed a bit of love and understanding. Which Hob is only too happy to provide.

Their work together sometimes involves long hours and stress, but Dream wouldn't ever want to go back to the slightly soulless corporation where he used to be. Even if he's tired and a little frustrated by Hob’s disorganised workspace, Dream is perfectly content. There's nothing better than curling up in Hob’s lap while he taps away on a line of code. Plus, he has a great time building their wedding website. Hob got to propose, so Dream gets to celebrate their upcoming marriage with his own expression of love through code. The theme colours are, of course, black and red <3

[swifttrinitychronicle]

Best Web Development Course in Phagwara

Join at TechCADD for the best Web Development course in Phagwara, Punjab! Master skills to create dynamic websites and applications!

[essential-randomness]

Enter the FujoVerse™

Starting 2024's content creation journey with a bang, it's time to outline the principles behind the FujoVerse™: an ambitious (but realistic) plan to turn the web back into a place of fun, joy, and connection, where people build and nurture their own communities and software. (You can also read the article on my blog)

The Journey

As those who follow my journey with @bobaboard or read my quarterly newsletter (linked in the article) know, the used-to-be-called BobaVerse™ is a collection of projects I've been working on since 2020 while pondering an important question: how do we "fix" the modern social web?

Obviously the joyless landscape that is the web of today is not something a single person can fix. Still, I loved and owed the internet too much to see it wither.

After countless hours of work, I found 3 pillars to work on: community, software ownership and technical education.

Jump in after the cut to learn more about how it all comes together!

Community

Community is where I started from, with good reason! While social networks might trick us into thinking of them as communities, they lack the characteristics that researchers identify as the necessary base for "true community": group identity, shared norms, and mutual concern.

Today, I'm even more convinced community is a fundamental piece of reclaiming the web as a place of joy. It's alienating, disempowering, and incredibly lonely to be surrounded by countless people without feeling true connection with most of them (or worse, feeling real danger).

Software Ownership and Collaboration

As I worked with niche communities "software ownership" also became increasingly important to me: if we cannot expect mainstream tech companies to cater to communities at the margins, it follows that these communities must be able to build and shape their own software themselves.

Plenty of people have already discussed how this challenge goes beyond the tech. Among many, "collaboration" is another sticking point for me: effective collaboration requires trust and psychological safety, both of which are in short supply these days (community helps here too, but it's still hard).

Education (Technical and Beyond)

As I worked more and more with volunteers and other collaborators, however, another important piece of the puzzle showed itself: the dire state of educational material for non-professional web developers. How can people change the web if they cannot learn how to *build* the web?

(And yes, learning HTML and CSS is absolutely important and REAL web development. But to collaborate on modern software you need so much more. Even further, people *yearn* for more, and struggle to find it. They want that power, and we should give it to them.)

Once again, technical aspects aren't the only ones that matter. Any large-scale effort needs many skills that society doesn't equip us with. If we want to change how the web looks, we must teach, teach, TEACH! If you've seen me put so much effort into streaming, this is why :)

And obviously, while I don't go into them in this article, open source software and decentralized protocols are core to "this whole thing".

The Future

All of this said, while I've been working on this for a few years, I've struggled to find the support I need to continue this work. To this end, this year I'm doing something I'm not used to: producing content, gaining visibility, and putting my work in front of the eyes of people that want to fight for the future of the web.

This has been a hard choice: producing content is hard and takes energy and focus away from all I've been doing. Still, I'm committed to doing what it takes, and (luckily) content and teaching go hand in hand. But the more each single person helps, the less I need to push for wide reach.

If you want to help (and read the behind the scenes of all I've been working on before everyone else), you can subscribe to my Patreon or to my self-hosted attempt at an alternative.

I deeply believe that in the long term all that we're building will result in self-sustaining projects that will carry this mission forward. After all, I'm building them together with people who understand the needs of the web in a way that no mainstream company can replicate.

Until we get there, every little bit of help (be it monetary support, boosting posts, pitching us to your friends, or kind words of encouragement and support) truly matters.

In exchange, I look forward to sharing more of the knowledge and insights I've accrued with you all :)

And once again, to read or share this post from the original blog, you can find it here.

[snickerduu]

Hi! How long did it take for you to become a web developer? Did you study by yourself or in uni?

Rn trying front end, but it seems that it will take years before my inattentive ass will actually be ready for the market

i finished my bachelor's degree in computer science earlier this year !! :)

but i personally don't think it's necessary when it comes to web development! i think in this scenario a portfolio would be more important. my uni studies were more theoretical (so i could potentially go into a research career but i dont really want to HAHA) over application, so i learned web dev through an internship! my supervisors + the internet helped me out 🐛

it took me around a month to settle in properly, but i still learn new things every day definitely hehe

++ you can build your portfolio with small web apps!! try starting w/small projects like your portfolio site, a task list, or a GPA calculator ^_^ more ideas will eventually come! if you're not sure what to do, you can also try recreating popular sites for practice to build knowledge 🧠

[fyeahnix]

That post from like a month ago (I was planning to write this the day after and then immediately forgot and this has been in drafts since lol) about web devs not having some basic knowledge of the web has been stuck in my brain for a while because they are correct as I said in the notes but it's the landscape of web dev right now that's causing it and I don't see it stopping anytime soon.

I've been a professional Front End Dev for just over 7 years at this point (now a UX Dev working on a design system), and while I have a good chunk of experience under my belt, I've gotten to the point where I realize just how much shit I do not know and it's a LOOOOT.

The current landscape of web dev is that most projects and products are robust web apps that, in the absolute best case scenario, are gonna require, at minimum:

User experience research and work (UX)

User interface design (UI)

Front end with accessibility and mobile responsiveness (I am here)

Front end interactions and state management (JS engineers)

Backend database and API work

Backend infrastructure work (including setting up the dev and QA test environments)

QA testing

Developer experience to make sure devs/engineers are working efficiently with the tools they have

I'm sure I've missed some roles here, but you can see why people end up specializing when they work on bigger projects and products. The web is so unbelievably JavaScript heavy nowadays that all these specializations are Kind Of Required™, but that's absolute best case scenario. A lot of companies simply do not have the budget (or desire) to fill all these roles. So then you have a bunch of people who are kinda okay to mediocre at multiple of these things instead focusing on being good at one or two things. And then put in timeline requirements. AND THEN you have some companies who have different philosophies on how to build their core product: some are very UX focused and will put time into making sure that's present, others are not and will not care about UX in the slightest and thus those roles may not exist there at all. And...well things aren't going to be as quality as you expect when you consider all of those points.

The web is full of applications now that require a lot more expertise in different fields than just a basic static site with no data. That's not to say static sites don't exist or have no place anymore, tho. But this is where we are. It sucks.

[digitalsvibes]

Higher Order Function in JavaScript