#Javascript tools for your web developer

[zoofsoftware]

Top AngularJS Development Tools AngularJS development tools are software applications that aid developers in building, testing, and debugging web applications using the AngularJS framework. They provide features like code editing, live reloading, component inspection, and performance analysis to streamline the development process and enhance productivity. . . ➡️Check out the post to learn more about them. ➡️Let us know if you want to know more points in the comment section below 👉Do not forget to share with someone whom it is needed. 👉Let us know your opinion in the comment down below 👉Follow @Zoof Software Solutions for more information ➡Grow your business with us! . . ✔️Feel free to ask any query at info@zoof.co.in ✔️For more detail visit: https://zoof.co.in/

[kafus]

beginner’s guide to the indie web

“i miss the old internet” “we’ll never have websites like the ones from the 90s and early 2000s ever again” “i’m tired of social media but there’s nowhere to go”

HOLD ON!

personal websites and indie web development still very much exist! it may be out of the way to access and may not be the default internet experience anymore, but if you want to look and read through someone’s personally crafted site, or even make your own, you can still do it! here’s how:

use NEOCITIES! neocities has a built in search and browse tools to let you discover websites, and most importantly, lets you build your own website from scratch for free! (there are other ways to host websites for free, but neocities is a really good hub for beginners!)

need help getting started with coding your website? sadgrl online has a section on her website dedicated to providing resources for newbie webmasters!

HTML (HyperText Markup Language) and CSS (Cascading Style Sheets) are the core of what all websites are built on. many websites also use JS (JavaScript) to add interactive elements to their pages. w3schools is a useful directory of quick reference for pretty much every HTML/CSS/JS topic you can think of.

there is also this well written and lengthy guide on dragonfly cave that will put you step by step through the basics of HTML/CSS (what webpages are made from), if that’s your sort of thing!

stack overflow is every programmer’s hub for asking questions and getting help, so if you’re struggling with getting something to look how you want or can’t fix a bug, you may be able to get your answer here! you can even ask if no one’s asked the same question before.

websites like codepen and jsfiddle let you test HTML/CSS/JS in your browser as you tinker with small edits and bugfixing.

want to find indie websites outside the scope of neocities? use the search engine marginalia to find results you actually want that google won’t show you!

you can also use directory sites like yesterweb’s link section to find websites in all sorts of places.

if you are going to browse the indie web or make your own website, i also have some more personal tips as a webmaster myself (i am not an expert and i am just a small hobbyist, so take me with a grain of salt!)

if you are making your own site:

get expressive! truly make whatever you want! customize your corner of the internet to your heart’s content! you have left the constrains of social media where every page looks the same. you have no character limit, image limit, or design limit. want to make an entire page or even a whole website dedicated to your one niche interest that no one seems to be into but you? go for it! want to keep a public journal where you can express your thoughts without worry? do it! want to keep an art gallery that looks exactly how you want? heck yeah! you are free now! you will enjoy the indie web so much more if you actually use it for the things you can’t do on websites like twitter, instead of just using it as a carrd bio alternative or a place to dump nostalgic geocities gifs.

don’t overwhelm yourself! if you’ve never worked with HTML/CSS or JS before, it may look really intimidating. start slow, use some guides, and don’t bite off more than you can chew. even if your site doesn’t look how you want quite yet, be proud of your work! you’re learning a skill that most people don’t have or care to have, and that’s pretty cool.

keep a personal copy of your website downloaded to your computer and don’t just edit it on neocities (or your host of choice) and call it a day. if for some reason your host were to ever go down, you would lose all your hard work! and besides, by editing locally and offline, you can use editors like vscode (very robust) or notepad++ (on the simpler side), which have more features and is more intuitive than editing a site in-browser.

you can use ctrl+shift+i on most browsers to inspect the HTML/CSS and other components of the website you’re currently viewing. it’ll even notify you of errors! this is useful for bugfixing your own site if you have a problem, as well as looking at the code of sites you like and learning from it. don’t use this to steal other people’s code! it would be like art theft to just copy/paste an entire website layout. learn, don’t steal.

don’t hotlink images from other sites, unless the resource you’re taking from says it’s okay! it’s common courtesy to download images and host them on your own site instead of linking to someone else’s site to display them. by hotlinking, every time someone views your site, you’re taking up someone else’s bandwidth.

if you want to make your website easily editable in the future (or even for it to have multiple themes), you will find it useful to not use inline CSS (putting CSS in your HTML document, which holds your website’s content) and instead put it in a separate CSS file. this way, you can also use the same theme for multiple pages on your site by simply linking the CSS file to it. if this sounds overwhelming or foreign to you, don’t sweat it, but if you are interested in the difference between inline CSS and using separate stylesheets, w3schools has a useful, quick guide on the subject.

visit other people’s sites sometimes! you may gain new ideas or find links to more cool websites or resources just by browsing.

if you are browsing sites:

if the page you’re viewing has a guestbook or cbox and you enjoyed looking at the site, leave a comment! there is nothing better as a webmaster than for someone to take the time to even just say “love your site” in their guestbook.

that being said, if there’s something on a website you don’t like, simply move on to something else and don’t leave hate comments. this should be self explanatory, but it is really not the norm to start discourse in indie web spaces, and you will likely not even be responded to. it’s not worth it when you could be spending your time on stuff you love somewhere else.

take your time! indie web doesn’t prioritize fast content consumption the way social media does. you’ll get a lot more out of indie websites if you really read what’s in front of you, or take a little while to notice the details in someone’s art gallery instead of just moving on to the next thing. the person who put labor into presenting this information to you would also love to know that someone is truly looking and listening.

explore! by clicking links on a website, it’s easy to go down rabbitholes of more and more websites that you can get lost in for hours.

seeking out fansites or pages for the stuff you love is great and fulfilling, but reading someone’s site about a topic you’ve never even heard of before can be fun, too. i encourage you to branch out and really look for all the indie web has to offer.

i hope this post helps you get started with using and browsing the indie web! feel free to shoot me an ask if you have any questions or want any advice. <3

[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.

[javascript]

Tumblr.js is back!

Hello Tumblr—your friendly neighborhood Tumblr web developers here. It’s been a while!

Remember the official JavaScript client library for the Tumblr API? tumblr.js? Well, we’ve picked it up, brushed it off, and released a new version of tumblr.js for you.

Having an official JavaScript client library for the Tumblr API means that you can interact with Tumblr in wild and wonderful ways. And we know as well as anybody how important it is to foster that kind of creativity.

Moving forward, this kind of creativity is something we’re committed to supporting. We’d love to hear about how you’re using it to build cool stuff here on Tumblr!

Some highlights:

NPF post creation is now supported via the createPost method.

The bundled TypeScript type declarations have been vastly improved and are generated from source.

Some deprecated dependencies with known vulnerabilities have been removed.

Intrigued? Have a look at the changelog or read on for more details.

Migrating

v4 includes breaking changes, so if you’re ready to upgrade to from a previous release, there are a few things to keep in mind:

The callback API has been deprecated and is expected to be removed in a future version. Please migrate to the promise API.

There is no need to use returnPromises (the method or the option). A promise will be returned when no callback is provided.

createPost is a new method for NPF posts.

Legacy post creation methods have been deprecated.

createLegacyPost is a new method with the same behavior as createPost in previous versions (rename createPost to createLegacyPost to maintain existing behavior).

The legacy post creation helpers like createPhotoPost have been removed. Use createLegacyPost(blogName, { type: 'photo' }).

See the changelog for detailed release notes.

What’s in store for the future?

We'll continue to maintain tumblr.js, but we’d like to hear from you. What do you want? How can we provide the tools for you to continue making cool stuff that makes Tumblr great?

Let us know right here or file an issue on GitHub.

Some questions for you:

We’d like to improve types to make API methods easier to use. What methods are most important to you?

Are there API methods that you miss?

Tumblr.js is a Node.js library, would you use it in the browser to build web applications?

[izicodes]

Mini React.js Tips #1 | Resources ✨

I thought why not share my React.js (JavaScript library) notes I made when I was studying! I will start from the very beginning with the basics and random notes I made along the way~!

Up first is what you'll need to know to start any basic simple React (+ Vite) project~! 💻

What you'll need:

node.js installed >> click

coding editor - I love Visual Studio Code >> click

basic knowledge of how to use the Terminal

What does the default React project look like?

Step-by-Step Guide

[ 1 ] Create a New Folder: The new folder on your computer e.g. in Desktop, Documents, wherever that will serve as the home for your entire React project.

[ 2 ] Open in your coding editor (will be using VSCode here): Launch Visual Studio Code and navigate to the newly created folder. I normally 'right-click > show more options > Open with Code' on the folder in the File Explorer (Windows).

[ 3 ] Access the Terminal: Open the integrated terminal in your coding editor. On VSCode, it's at the very top, and click 'New Terminal' and it should pop up at the bottom of the editor.

[ 4 ] Create the actual React project: Type the following command to initialize a new React project using Vite, a powerful build tool:

npm create vite@latest

[ 5 ] Name Your Project: Provide a name for your project when prompted.

[ 6 ] Select 'React' as the Framework: Navigate through the options using the arrow keys on your keyboard and choose 'React'.

[ 7 ] Choose JavaScript Variant: Opt for the 'JavaScript' variant when prompted. This is the programming language you'll be using for your React application.

[ 8 ] Navigate to Project Folder: Move into the newly created project folder using the following command:

cd [your project name]

[ 9 ] Install Dependencies: Execute the command below to install the necessary dependencies for your React project (it might take a while):

npm install

[ 10 ] Run the Development Server: Start your development server with the command (the 'Local' link):

npm run dev

[ 11 ] Preview Your Project: Open the link provided in your terminal in your web browser. You're now ready to witness your React project in action!

Congratulations! You've successfully created your first React default project! You can look around the project structure like the folders and files already created for you!

BroCode's 'React Full Course for Free' 2024 >> click

React Official Website >> click

Stay tuned for the other posts I will make on this series #mini react tips~!

[fujocoded]

Funding FujoCoded: Stretch Goals!

It’s time! With our first goal met (🎉 thank you!), let’s talk about stretch goals. We have quite a few planned, so we're going to go through them one by one and explain what they are and why we chose them!

Before we go down the list, here's something fun:

Sticker Unlock: At 45 backers, we also unlocked one more sticker!

The goal of our campaign is to cover business expenses most of all. The unlocked content is an extra token of gratitude for your support that also helps us meet our own targets! 

With that said, let's get to our stretch goals...

$4,000: "That's Why I Ship On Company Time" Ao3 Sticker

At $4,000 we'll unlock one more sticker design that you can add to your collection! 

Our first version of this "shipping" sticker features VSCode and a terminal, but there's more than one type of shipping... here's to the other one!

$5,000: "Using NPM with Javascript" Article

Next up, we have our first article. Our plan is to add an Articles section to @fujowebdev where we'll collect simple, free guides to help beginners get past the roadblocks we see them encounter!

This first one will cover the basics of NPM, a core element of modern JavaScript!

"How do I install this JavaScript library? How do I run this open source JavaScript project? How can I get started creating my blog using a tool like @astrodotbuild?" are some of the most common questions we get in our Fandom Coders server. 

Let's give *everyone* the answer!

$6,000: Offering Website Art Prints

Next up, we'll turn the excellent art on our website into prints! These will be (probably) 8x10-sized art prints that will look amazing without breaking the bank. Full specs soon!

...and speaking of the site, you have tried moving the windows, right?

$7,000: "Catching Up With Terminal" Article

Next, another common issue for beginner developers: how to start learning how to handle the Terminal.

This will require some research to determine the major roadblocks, which is how our project operates: active learning from those going through it all!

$8,000: "Crucial Confrontations" Article

And last (for now), something very dear to us: an article extracting some wisdom from the book "Crucial Confrontations": https://www.amazon.com/Crucial-Confrontations-Resolving-Promises-Expectations/dp/0071446524

This may seem like an unusual choice, but it highlights how our teaching goals go beyond programming to cover collaboration!

After years of working within our community, we repeatedly found that developing effective communication and confrontation skills helps our collaborators thrive. Unfortunately, the world doesn't teach us how to effectively (but kindly) hold each other accountable.

Some of our most involved collaborators have read this book and found the tools within it transformative. Given this experience, we deeply believe that making some of this wisdom easily accessible (without having to read the full book) will allow all of us to collaborate better!

If we can reach $8,000, this will enable us to test this hypothesis and learn how teaching soft skills beyond programming influences what we're able to achieve! It's a bold idea, but we're excited to see how it turns out in practice.

Help us make it there!

And that's all...for now!

If you want to hop on Twitch right now, you can join us as we put some extra polish on our shiny new FujoCoded website.

And remember, you can back our campaign here to help us achieve these goals and more:

[esoxy]

So let's get into the nitty-gritty technical details behind my latest project, the National Blue Trail round-trip search application available here:

This project has been fun with me learning a lot about plenty of technologies, including QGis, PostGIS, pgRouting, GTFS files, OpenLayers, OpenTripPlanner and Vita.

So let's start!

In most of my previous GIS projects I have always used custom made tools written in ruby or Javascript and never really tried any of the "proper" GIS tools, so it was a good opportunity for me to learn a bit of QGIS. I hoped I could do most of the work there, but soon realized it's not fully up to the job, so I had to extend the bits to other tools at the end. For most purposes I used QGis to import data from various sources, and export the results to PostGIS, then do the calculations in PostGIS, re-import the results from there and save them into GeoJSON. For this workflow QGIS was pretty okay to use. I also managed to use it for some minor editing as well.

I did really hope I could avoid PostGIS, and do all of the calculation inside QGIS, but its routing engine is both slow, and simply not designed for multiple uses. For example after importing the map of Hungary and trying to find a single route between two points it took around 10-15 minutes just to build the routing map, then a couple seconds to calculate the actual route. There is no way to save the routing map (at least I didn't find any that did not involve coding in Python), so if you want to calculate the routes again you had to wait the 10-15 minute of tree building once more. Since I had to calculate around 20.000 of routes at least, I quickly realized this will simply never work out.

I did find the QNEAT3 plugin which did allow one to do a N-M search of routes between two set of points, but it was both too slow and very disk space intense. It also calculated many more routes than needed, as you couldn't add a filter. In the end it took 23 hours for it to calculate the routes AND it created a temporary file of more than 300Gb in the process. After realizing I made a mistake in the input files I quickly realized I won't wait this time again and started looking at PostGIS + pgRouting instead.

Before we move over to them two very important lessons I learned in QGIS:

There is no auto-save. If you forget to save and then 2 hours later QGIS crashes for no reason then you have to restart your work

Any layer that is in editing mode is not getting saved when you press the save button. So even if you don't forget to save by pressing CTRL/CMD+S every 5 seconds like every sane person who used Adobe products ever in their lifetimes does, you will still lose your work two hours later when QGIS finally crashes if you did not exit the editing mode for all of the layers

----

So let's move on to PostGIS.

It's been a while since I last used PostGIS - it was around 11 years ago for a web based object tracking project - but it was fairly easy to get it going. Importing data from QGIS (more specifically pushing data from QGIS to PostGIS) was pretty convenient, so I could fill up the tables with the relevant points and lines quite easily. The only hard part was getting pgRouting working, mostly because there aren't any good tutorials on how to import OpenStreetMap data into it. I did find a blog post that used a freeware (not open source) tool to do this, and another project that seems dead (last update was 2 years ago) but at least it was open source, and actually worked well. You can find the scripts I used on the GitHub page's README.

Using pgRouting was okay - documentation is a bit hard to read as it's more of a specification, but I did find the relevant examples useful. It also supports both A* search (which is much quicker than plain Dijsktra on a 2D map) and searching between N*M points with a filter applied, so I hoped it will be quicker than QGIS, but I never expected how quick it was - it only took 5 seconds to calculate the same results it took QGIS 23 hours and 300GB of disk space! Next time I have a GIS project I'm fairly certain I will not shy away from using PostGIS for calculations.

There were a couple of hard parts though, most notably:

ST_Collect will nicely merge multiple lines into one single large line, but the direction of that line looked a bit random, so I had to add some extra code to fix it later.

ST_Split was similarly quite okay to use (although it took me a while to realize I needed to use ST_Snap with proper settings for it to work), but yet again the ordering of the segments were off a slight bit, but I was too lazy to fix it with code - I just updated the wrong values by hand.

----

The next project I had never used in the past was OpenTripPlanner. I did have a public transport project a couple years ago but back then tools like this and the required public databases were very hard to come by, so I opted into using Google's APIs (with a hard limit to make sure this will never be more expensive than the free tier Google gives you each month), but I have again been blown away how good tooling has become since then. GTFS files are readily available for a lot of sources (although not all - MAV, the Hungarian Railways has it for example behind a registration paywall, and although English bus companies are required to publish this by law - and do it nicely, Scottish ones don't always do it, and even if they do finding them is not always easy. Looks to be something I should push within my party of choice as my foray into politics)

There are a couple of caveats with OpenTripPlanner, the main one being it does require a lot of RAM. Getting the Hungarian map, and the timetables from both Volánbusz (the state operated coach company) and BKK (the public transport company of Budapest) required around 13GB of RAM - and by default docker was only given 8, so it did crash at first with me not realizing why.

The interface of OpenTripPlanner is also a bit too simple, and it was fairly hard for me to stop it from giving me trips that only involve walking - I deliberately wanted it to only search between bus stops involving actual bus travel as the walking part I had already done using PostGIS. I did however check if I could have used OpenTripPlanner for that part as well, and while it did work somewhat it didn't really give optimal results for my use case, so I was relieved the time I spend in QGIS - PostGIS was not in vain.

The API of OpenTripPlanner was pretty neat though, it did mimic Google's route searching API as much as possible which I used in the past so parsing the results was quite easy.

----

Once we had all of the data ready, the final bit was converting it to something I can use in JavaScript. For this I used my trusted scripting language I use for such occasion for almost 20 years now: ruby. The only interesting part here was the use of Encoded Polylines (which is Google's standard of sending LineString information over inside JSON files), but yet again I did find enough tools to handle this pretty obscure format.

----

Final part was the display. While I usually used Leaflet in the past I really wanted to try OpenLayers, I had another project I had not yet finished where Leaflet was simply too slow for the data, and I had a very quick look at OpenLayers and saw it could display it with an acceptable performance, so I believed it might be a good opportunity for me to learn it. It was pretty okay, although I do believe transparent layers seem to be pretty slow under it without WebGL rendering, and I could not get WebGL working as it is still only available as a preview with no documentation (and the interface has changed completely in the last 2 months since I last looked at it). In any case OpenLayers was still a good choice - it had built in support for Encoded Polylines, GPX Export, Feature selection by hovering, and a nice styling API. It also required me to use Vita for building the application, which was a nice addition to my pretty lacking knowledge of JavaScript frameworks.

----

All in all this was a fun project, I definitely learned a lot I can use in the future. Seeing how well OpenTripPlanner is, and not just for public transport but also walking and cycling, did give me a couple new ideas I could not envision in the past because I could only do it with Google's Routing API which would have been prohibitively expensive. Now I just need to start lobbying for the Bus Services Act 2017 or something similar to be implemented in Scotland as well

[quietmarie]

Anyone can program (yes, even you)

"Programming is easy"

I saw some variations of this statement shared around the site recently, always in good intentions of course, but it got me thinking.

Is that really true?

Well it certainly isn't hard in the way some developers would want to make you believe. A great skill bestowed only upon the greatest of minds, they're the ones making the world work. You better be thankful.

That is just elitist gibberish. If anyone ever tells you that programmers are "special people" in that way, or tries to sell you on the idea of "real" programmers that are somehow better than the rest, you can safely walk in the other direction. They have nothing of value to tell you.

But I think the answer is more complicated than a simple "Yes, programming is easy" too. In all honesty, I don't think it's an easy thing to "just pick up" at all. It can be very unintuitive at first to wrap your head around just how to tell a computer to solve certain problems.

One person in the codeblr Discord server likened it to cooking. That's a skill that can be very hard, but it's also something that everyone can learn. Anyone can cook. And anyone can program.

I really mean that. No need to be good at maths, to know what a bit is or whatever it is people told you you need. You're not too old to learn it either, or too young for that matter. If you want to start programming (and you can read this post), you already have everything you need. You can write your first little programs today!

One of the cool things about programming is that you can just fuck around and try lots of stuff, and it's fine. Realistically, the worst thing that can happen is that it doesn't work the way you imagined. But you'll never accidentally trigger the fire alarm or burn your house down, so feel free to just try a bunch of stuff.

"Okay I want to learn programming now, what do I do?"

That's awesome, I love the enthusiasm! As much as I'd love to just give you a resource and tell you to build a thing, you still have to make a choice what you want to learn first. The options I'd recommend are:

Scratch: A visual education tool. The main advantage is that you don't have to worry about the exact words you need to write down, you can just think about the structure of your program. The way it works is that you drag and drop program elements to be executed when they should be. You can relatively quickly learn to make cute little games in it. The downside is that this isn't really a "professional" programming language, so, while learning from Scratch will give you the basics that apply to most languages and will make switching to another language easier, you're still gonna have to switch sooner or later. Start here: https://scratch.mit.edu/

Python: The classic choice. Python is a very widely used, flexible programming language that is suited for beginners. It is what I would recommend if you want to skip right to or move on from Scratch to a more flexible language. https://automatetheboringstuff.com/ is your starting point, but there's also a longer list of resources here if you want to check that out at some point.

HTML/CSS/JavaScript: The web path. HTML and CSS are for creating the look of websites, and JavaScript is for the interactive elements. For example, if you ever played a game in your browser, that was probably written in JS. Since HTML and CSS are just for defining how the website should look, they're different from traditional programming languages, and you won't be able to write programs in them, that's what JS is for. You have to know HTML before you learn CSS, but otherwise the order in which you learn these is up to you. Your JavaScript resource is https://javascript.info/, and for HTML and CSS you can check out https://developer.mozilla.org/en-US/docs/Learn/Getting_started_with_the_web.

I put some starting out resources here, but they're really just that - they're for starting out. You don't have to stick to them. If you find another path that suits you better, or if you want to get sidetracked with another resource or project, go for it! Your path doesn't have to be linear at all, and there's no "correct" way to learn things.

One of the most important things you'll want to do is talk to developers when you struggle. The journey is going to be frustrating at times, so search out beginner-friendly coding communities on Discord or wherever you're comfortable. The codeblr community certainly tends to be beginner-friendly and kind. My DMs and asks are also open on here.

[astridvalencia]

How to Learn Programming?

Learning to code can be a rewarding and empowering journey. Here are some steps to help you get started:

Define Your Purpose:

Understand why you want to learn to code. Whether it's for a career change, personal projects, or just for fun, having a clear goal will guide your learning path.

Choose a Programming Language:

Select a language based on your goals. For beginners, languages like Python, JavaScript, or Ruby are often recommended due to their readability and versatility.

Start with the Basics:

Familiarize yourself with fundamental concepts such as variables, data types, loops, and conditional statements. Online platforms like Codecademy, Khan Academy, or freeCodeCamp offer interactive lessons.

Practice Regularly:

Coding is a skill that improves with practice. Set aside dedicated time each day or week to code and reinforce what you've learned.

Build Simple Projects:

Apply your knowledge by working on small projects. This helps you gain hands-on experience and keeps you motivated.

Read Code:

Study existing code, whether it's open-source projects or examples in documentation. This helps you understand different coding styles and best practices.

Ask for Help:

Don't hesitate to ask questions on forums like Stack Overflow or Reddit when you encounter difficulties. Learning from others and getting feedback is crucial.

Join Coding Communities:

Engage with the coding community to stay motivated and learn from others. Platforms like GitHub, Stack Overflow, and coding forums provide opportunities to connect with fellow learners and experienced developers.

Explore Specializations:

As you gain more experience, explore different areas like web development, data science, machine learning, or mobile app development. Specializing can open up more opportunities and align with your interests.

Read Documentation:

Learn to navigate documentation for programming languages and libraries. It's a crucial skill for developers, as it helps you understand how to use different tools and resources effectively.

Stay Updated:

The tech industry evolves rapidly. Follow coding blogs, subscribe to newsletters, and stay informed about new developments and best practices.

Build a Portfolio:

Showcase your projects on platforms like GitHub to create a portfolio. It demonstrates your skills to potential employers or collaborators.

Remember, learning to code is a continuous process, and it's okay to face challenges along the way. Stay persistent, break down complex problems, and celebrate small victories.

[vorenado-m]

ok that post has 7 reblogs which is kind of exciting but also very embarrassing cuz the game doesnt do anything yet.

i am an aspiring [front-end] web developer and HTML, CSS, and javascript are foundational parts of that job, so i have a solid basis for making an HTML5 game using javascript.

ive probably got around 2-3 dozen hours of crying over javascript under my belt and ive been doing it semi-regularly for a few months (just kind of building random bullshit-- the first independent project i made was a number guesser, and more recently i made a wordle clone that i based a little more than loosely on this tutorial) so thats a beginner project but i am by no means like. just dipping my toes into javascript.

ive been adapting from this specific youtube tutorial. the main changes ive made are the player moving instead of the map. it requires knowledge of objects, nesting, and object/constructor methods, which is something i didnt have a strong basis in before i started the tutorial, but its really straight-forward and the guy does a great job explaining it.

if youre having trouble with the tutorial cuz your foundational javascript isnt up to par, freecodecamp just updated their javascript algorithms and data structures tutorial and it fucks SOOOOO HARD. the first project is building a simple text-based RPG which is what inspired me to try and build a simple 2d game. i dont recommend making this jump unless youre actually at least semi-comfortable in javascript but it is VERY doable.

i drew the sprites in paint.net which is free and it has a grid tool and allows transparency. no tutorial for that i just like pixel art even if im really bad at it lol.

[ss-tech-services]

Proven Techniques for Ranking Higher on Google

Google is a powerful search engine, and seeking ways to place one's website at the top is important for enhancing the website's visibility, attracting more traffic, as well as the success of the online presence. At the digital marketing agency, we recognize that optimization is vital as there are millions of sites competing for the first places. Therefore, it is possible to use effective methods which cut across Google’s successful methods. In this article, we present systems that have been tested and proven to improve your google ranking and more traffic to your website.

1.Do a proper keyword research

Keyword research is the most important part of an SEO strategy. It is because by knowing what the intended audience is searching for you will be able to develop content that cuts across.

Action Steps:

Use Keyword Tools: Use high traffic specific keywords’ search volume tools like Google Keyword planner, Ahref, SEM rush etc. to search for keywords with low competition.

Analyze Competitors: Look at the keywords that are working for your competitors and narrow dow n on the related ones.

Focus on Long-Tail Keywords: The phrases are less competitive in nature and since they are more specific they lead to higher conversions.

2. Better the On-Page SEO Optimization

On page SEO Optimization is the process of editing and facilitating changes on the pages of a web document in order to make them rank well and fit to the targeted audience. Such changes may involve content optimization of the webpage, markup optimization improvement of the HTML source code.

Action Steps:

Rewriting and Optimization Strategy Title Tags and Meta Descriptions: Always ensure you note your page title and all the meta area as it has been promised to the readers and throughout the website.

Header Tags: Help cluster words and enhance comprehension by assigning H1 tags for the headline as the highest, H2, H3, etc for the subtitles.

URL Structure: Lines should be simple and moderate but include powerful words that are in line with what you are targeting.

Internal Linking: Where necessary links are created to other pages which are relevant to the current page being viewed by users and helps to spread out the link equity within the site.

3. Create High-Quality Content

Content is a very important element of SEO. Content, when properly designed, well written and is valuable and informative, will drive visitors, retain them and help establish credibility on a given niche.

Action Steps: Write for Your Audience: Use Solutions oriented approach where every word helps to eliminate audience problems.

Incorporate Keywords Naturally: Avoid abrupt keyword inclusion or excess use of keywords in the content.

Use Multimedia: Use of multimedia such as, images, animations, values etc to assist in a more appealing manner and also hold attention.

4.Enhance User Experience (UX)

The most important aspect with any Google ranking of the website is the user experience. Along with other factors, page speed, mobile usability, and site hierarchy are considerable for rankings.

Action Steps:

Improve Page Speed: It is possible to analyze why their site is slow through the use of Google PageSpeed and rectify the site’s speed. Spelling out some issues – Image compression, browser caching, CSS and javascript files minification.

Mobile-friendly Site Design: Create a website that is responsive to any device and that offers the same level of interaction regardless of the device used. With Google focusing on mobile first indexing, this becomes self-explanatory.

Utilize simple Structure: Website usability should be observed through the enabling of a better navigation structure and size of the website. This enables the website content to be easily accessed reducing the levels of bouncing.

5. Improve Quality of Backlinks

Links are an essential component of the parameters used in the Google algorithm, page rank among them. Backlinks from other websites with high reputation which are also relevant to the topic covered by a site will in most cases optimize the site.

Action Steps:

Develop Great Content: Write content that will drive people to share it, persuasive contents such as how to guides and case studies, original research.

Advertising through blogs: Write articles as a guest for reputable blogs in the niche and ensure to include a link to one’s site in the author information or within the article text.

6. Geo-targeting

For businesses that are into a certain geographic perspective, optimizing local search can get them local patrons and also enhance the local ranking.

Action Steps:

Claim Your Google My Business Listing: Your Google My Business profile must have all relevant details about your ventures such as addresses and business hours.

Social Media – Add Local Clientele Keywords: Identify local phrases and use them when generating content, title tags and meta descriptions.

Encouraging Reviews: Actively ask clients to review your services on Google and any other outlets and respond to them if possible, as good reviews will help boost your visibility in local search results.

7.Review and Performance metrics

It allows you to keep track of and evaluate your performance in line with search engine optimization. Bring out the strengths and weaknesses by utilizing the right tools.

Action Steps:

Google Analytics: Establish and analyze google analytical for effective tracking of such elements as the frequency of visitors, viewership and even exit of visitors.

Google Search Console: Use the GSC to see how well your web page performs, fixes, and submits the sitemap of your web page.

Finesse your strategies: With the use of prior or primary researches, refine any of your current seo methods. Adequate emphasis should be placed on aspects with some room for growth as well as recent developments on global search engine behaviors.

8. Follow New SEO Trends

SEO, as any other discipline, is dynamic, thus, it is important for the SEO professionals to go on top of the new developments and any new releases in a bid to keep their positions and even enhance them.

Action Steps:

Follow Industry Blogs: Sign up to popular and authoritative SEO blog sites and forums as fresh content and relevant changes are posted.

Participate in Webinars and Conferences: Join the SEO web-based presentations and conferences to listen to the views from other relevant fields.

Adapt to Algorithm Changes: Many changes concerning the Google algorithm are commonplace. This means these things are happening in a constant rush and therefore SEO strategies had to be altered with the changes.

Conclusion

Achieving a good rank on Google is a process that requires effective execution of multiple strategies like keyword research, website on-page and off page optimization, content writing and technical enhancement, etc. Downham Digital Marketing is dedicated to assist companies who wish to adopt these tested approaches to increase their online exposures. Keep in mind that SEO is not a one-time thing; it requires persistent revisions and improvements for the strategies to survive the competitive scene. For further assistance with your SEO efforts, be sure to contact our team of experts at SS TECH SERVICES as they employ state-of-the-art strategies and approaches.

[retailscrap]

What Are the Key Benefits of Scraping Zepto Grocery Data for Your Business?

In the rapidly evolving world of e-commerce, quick commerce or q-commerce is gaining significant traction, particularly in the grocery sector. Zepto, a prominent player in this space, is redefining how consumers shop for groceries by offering ultra-fast delivery services. Scraping Zepto grocery data is essential for businesses aiming to harness insights, optimize operations, and stay ahead in the competitive landscape. This article explores the significance of extracting Zepto grocery data, the methods involved, and the potential applications of this information.

Understanding Zepto and Quick Commerce

Zepto is a critical player in the quick commerce (q-commerce) sector, providing rapid grocery delivery services to meet the growing demand for convenience. With a promise of delivering groceries in as little as 10 minutes, Zepto operates in a highly competitive market where speed and efficiency are paramount. As a result, the platform handles a vast amount of data related to inventory, prices, customer preferences, and order patterns.

Quick commerce is a subset of e-commerce focused on delivering products within a short time frame, often under 30 minutes. This model requires real-time inventory management, dynamic pricing strategies, and agile logistics. Scraping quick commerce data offers invaluable insights into these aspects, enabling businesses to adapt and thrive in this fast-paced environment.

Why Scrape Zepto Grocery Data?

Scraping Zepto grocery data is crucial for gaining insights into market trends, optimizing inventory, and refining pricing strategies. By analyzing this data, businesses can enhance their competitive edge, tailor their offerings to consumer preferences, and drive operational efficiency.

Market Analysis and Competitive Intelligence: Zepto grocery data scraping services provide a window into the competitive landscape. Businesses can gain insights into market trends and competitor strategies by analyzing Zepto’s product offerings, pricing strategies, and inventory levels. This information is crucial for positioning your products and services effectively.

Consumer Behavior Insights: Understanding consumer preferences and buying patterns is essential for tailoring marketing strategies and optimizing product offerings. Scraping data on popular items, purchase frequency, and customer reviews from Zepto helps businesses identify trends and adapt to changing consumer demands.

Pricing Strategy Optimization: Dynamic pricing is critical to the quick commerce model. By scraping pricing data from Zepto, businesses can monitor price fluctuations, track promotions, and adjust their pricing strategies accordingly. This ensures competitiveness and maximizes revenue potential.

Inventory Management: Real-time inventory data is crucial for effective supply chain management. Scraping Zepto inventory data allows businesses to monitor stock levels, track product availability, and optimize inventory management practices to avoid overstocking or stockouts.

Product Development and Innovation: Insights gained from Zepto data scraper can drive product development and innovation. Analyzing popular products and customer feedback helps businesses identify gaps in the market and develop new products that cater to emerging trends.

Methods for Scraping Zepto Grocery Data

Scraping Zepto grocery data involves collecting relevant information from the platform’s website or app. There are several methods to accomplish this, each with its advantages and challenges:

HTML Parsing: This traditional method involves downloading the HTML content of Zepto’s web pages and using parsing libraries to extract data. Tools like BeautifulSoup (Python) or Cheerio (JavaScript) can be employed. While effective, HTML parsing may face challenges with dynamic content and frequent website updates.

APIs: If Zepto provides an API (Application Programming Interface), it offers a structured and reliable way to access data. APIs are generally more stable and less prone to breaking than HTML parsing. Checking for available APIs or contacting Zepto for API access can simplify the data extraction.

Web Scraping Tools: Several commercial and open-source web scraping tools, such as Scrapy, Selenium, or Puppeteer, are available. These tools can automate data extraction processes, handle dynamic content, and efficiently manage large-scale scraping tasks.

Browser Automation: For sites that use JavaScript extensively to load content, browser automation tools like Selenium or Puppeteer can simulate user interactions and extract data. These tools help scrape dynamic content but may require more resources and setup than straightforward methods.

Web Scraping Services: There are dedicated web scraping services and platforms that offer pre-built scrapers for various e-commerce sites, including grocery platforms. These services can save time and resources, providing ready-to-use data extraction solutions.

Challenges and Considerations

Scraping data from Zepto presents challenges related to legal compliance, data accuracy, and server load. Ethical considerations also include respecting privacy and avoiding excessive strain on the website. Addressing these challenges ensures responsible and effective data extraction practices.

Legal and Ethical Issues: Scraping data from Quick Commerce websites must comply with legal regulations and terms of service. Some sites explicitly prohibit scraping, and violating these terms can result in legal consequences. It is essential to review Zepto’s terms and seek permission if required.

Data Accuracy and Quality: Maintaining data accuracy is crucial for practical analysis. Websites frequently update their content, which can impact scraping tools. Regular monitoring and updating of scraping scripts are necessary to ensure data quality.

Rate Limiting and Load: Excessive scraping activity can significantly load Zepto’s servers, potentially affecting the site’s performance for other users. Implementing rate limiting and respecting the site’s bandwidth can mitigate this issue and ensure ethical scraping practices.

Data Privacy: Scraping user-generated content, such as reviews or ratings, requires careful handling of personal data. Adhering to data protection regulations and ensuring that scraped data is stored and processed securely is crucial to maintaining user privacy.

Applications of Scraped Zepto Grocery Data

Scraped Zepto grocery data can be applied to enhance business intelligence, optimize supply chains, and personalize marketing efforts. Analyzing imthis data helps identify trends, benchmark performance, and improve inventory management, driving strategic decisions and operational efficiency.

Business Intelligence: craped data can be analyzed to generate actionable insights for strategic decision-making. Businesses can create dashboards, reports, and visualizations to track performance metrics, identify trends, and make data-driven decisions.

Competitive Benchmarking: By comparing scraped data from Zepto with data from other grocery platforms, businesses can benchmark their performance and identify areas for improvement. This competitive analysis can guide strategy and operational adjustments.

Personalization and Marketing: Insights from scraped data can inform personalized marketing campaigns and product recommendations. Understanding customer preferences and purchase patterns allows businesses to tailor their marketing efforts and improve customer engagement.

Supply Chain Optimization: Real-time inventory data helps businesses optimize their supply chain operations, ensuring that popular products are adequately stocked and reducing the risk of overstocking or stockouts.

Trend Identification: Analyzing data on popular products and customer reviews helps businesses identify emerging trends and adapt their product offerings to meet changing consumer demands.

Conclusion :

Scrape Zepto grocery data to offer businesses a wealth of opportunities to gain insights, optimize operations, and stay competitive in the dynamic, quick commerce landscape. Businesses can make informed decisions, enhance their marketing strategies, and improve overall performance by leveraging data on product offerings, pricing, inventory, and consumer behavior. However, it is crucial to approach data scraping with a strong understanding of legal, ethical, and technical considerations. With careful planning and execution, scraping Zepto grocery data can provide valuable advantages and drive success in the fast-paced world of quick commerce.

Transform your retail operations with Retail Scrape Company's data-driven solutions. Harness real-time data scraping to understand consumer behavior, fine-tune pricing strategies, and outpace competitors. Our services offer comprehensive pricing optimization and strategic decision support. Elevate your business today and unlock maximum profitability. Reach out to us now to revolutionize your retail operations!!

Source : https://www.retailscrape.com/benefits-of-scraping-zepto-grocery-data.php

[izicodes]

Hi Loa! You said you started off with HTML/CSS/JavaScript, and you post a lot about your website projects. So I wanted to ask if you have any advice for the process of designing a website and making various graphics. I enjoy coding a whole lot, but I've avoided front-end stuff until now because looking into design and tools for it made me feel a little overwhelmed. What would you do if you were to start learning anew web design for your coding job and hobby projects? Thank you a lot :)

Hiya! 💗

I'd be happy to share some advice on designing a website and creating graphics. It's great that you enjoy coding and want to explore front-end development and design, and don't worry, though I love frontend stuff a lot, I still find some things overwhelming e.g. I'm currently learning Django which I have put off from learning because it looked "hard" but now I love learning it. Just give yourself a little push and you'll enjoy it! 😉🙌🏾

Web Design Inspiration

Two key places I get inspiration for my website designs are Pinterest and Behance!

For instance, when I was, and still am, researching Old Web GUI designs, I made a Pinterest board of images relating to what I wanted to design and I used that as a reference when building the design in HTML and CSS. So, I would look at the picture and think "Okay in terms of HTML elements and CSS styling, how can I replicate this? 😉👍🏾". You can check out these boards: board 1 | board 2

Pinterest is the main inspiration place, and Behance is for more in-depth web design components. What I mean is if I need inspiration for a navbar design or a certain card design, I would use Behance.

Now I don't particularly do this, which is bad, but I do recommend making a wireframe for your web designs. I talked about wireframes in a previous post, but to sum it up; wireframes are good because they allow you to stick to your design plans and not go off on a tangent. These are especially good when working in a team at work, for example.

The reason why I don't particularly do them as often as I should is because I see things in my head vividly enough that I won't forget where everything should be - no super power but that's the main reason I don't make wireframes. As well, I change ideas halfway through so there's no real need for me to keep making wireframes if I will change the design 2 minutes later! 😭💔

But that's just me, but you should totally start designing wireframes. Practising drawing up some wireframes will definitely help with being creative in your designs. Take everything around you as an inspiration. The way I think of it is to think like an artist who is capable of painting anything - all you have to do is look around and paint. You can do the same with web development - everything is an inspiration. I saw a person make a whole webpage with amazing graphics... just about water. You can do the same.

If you need help on that part, definitely look into graphic design. I took extra classes in Graphics (which was just graphic design) when in school which involved looking at graphic artists and studying their work, then replicating something with our own twist. You can do the same with web design - study websites online, some you like or random ones. Look at a piece of the website and try and replicate it. That's why I like projects which are like "make a Google clone" or "make a Netflix clone" because it gives you the chance to study other people's codes and you can keep that knowledge for any future projects!

And lastly, study web design principles. There are some principles that good websites all put into their design that make the user's experience good. Read this article about it and this should even give hints to how you could design your next website! Learn about fundamental design principles such as colour theory, typography, layout, and composition. Understanding these principles will help you create aesthetically pleasing and user-friendly designs.

Web Design Tools I Use

Now, what do I use every time I start a new "project", what online tools do I use? I literally have these on my browser's bookmarks, ready to go!

Pinterest (inspiration) - LINK

Behance (inspiration) - LINK

Coolors (colour palette generator) - LINK

CSS Gradient Generator (because I'm lazy) - LINK

Google Fonts (main source for fonts) - LINK

Font Palace (fonts I want but not on Google Fonts) - LINK

Font Awesome (for the little icons) - LINK

Image Colour Picker (if I have an image and I want to pick the colour from it) - LINK

Optional tools:

Bootstrap 4/5 (sometimes I use this for personal projects, definitely use it at work) - LINK

Pattern.css (creates a patterned background for you, again I'm lazy) - LINK

Storyset on Freepik (people graphic images) - LINK

Pexels (stock background and even fake product images) - LINK

Unsplash (same as Pexel) - LINK

LottieFiles (set animations) - LINK

TinyPNG (makes image sizes smaller so less space) - LINK

CSSmatic (4 cool CSS generators) - LINK

That's all I have to say, if I didn't help with your question, message me to help you further but I do hope this helps you!! Good luck! 🥰🙌🏾💗

[lunarsilkscreen]

HTML, RichText, and BB_Markup

Back in the day "RichText" or text that can be stylized like you would in Microsoft Word, or an E-Mail, wasn't often available in social media platforms.

And there's still some social media platforms who don't allow it at all.

This has multiple reasons, the processing is done in script at the browser level, and so there used to be performance reasons not to allow it. Or most of your users would experience a slow down just to view the text, why bother with it?

As browsers started getting more comfortable and fast enough to deliver HTML pages, with the markup allowed in HTML, HTML became the default. But as JavaScript grew in popularity, scope and use. HTML itself became a way for people to inject scripts directly into the page.

And instead of just, cleaning script tags and other injection vulnerabilities, websites took HTML away from users all together. This was a problem, in Part, directly influenced by the W3C {World-wide web consortium}, and big-browser (Microsoft, Netscape, and Mozilla, and later Google, Apple, and Opera) who all implemented HTML/CSS/JS differently.

Nobody knows why they did this, they just did. (Actually, there's a bunch of different reasons, but as you look deeper into the rabbit hole, the more absurd it gets.)

After that, forum and social media designers came up with *BB_Markup* I think BB means blackboard, but who knows for sure anymore.

BB was basically a shorthand HTML markup that used square-brackets instead of triangle-brackets, and at a server level, that markup got turned into *safe* HTML markup--to avoid user-level injection attacks.

We also get a bunch of other short hand that may or may not be used in certain platforms (like reddit) to this day. Wrapping text in asterisks to italicize a word, or tildes or the little wavey dash (~) which denote bolding under lining or strike through depending on what you're used to.

All sorts of things that some people who were netizens of the 90s and early-00s might still be in the habit of using.

Today, there's little reason for browsers to even allow <script> or script-referencing mark-up at that particular level anymore. Which would solve A LOT of early security issues. But they don't change it back because a lot of websites still use tricks like that, because that's what developers do.

Even though advertising still allows injection and browser-hijacking at a "user-level" just like in the olden days. Yep, if you host ads, there's a good chance you're allowing those ads to deliver malware to your users.

Looking at you YouTube and websites that say "Please stop using ad-block". They don't use them to prevent you from getting paid, they use them to stop you from injecting their device with malware.

You big dummys.

That's part of the reason why I'm an advocate of "ad-reform". Advertising companies are leveraging their ad-platforms for more than simply delivering ads.

There's a drive to put internet tools only in the hands of companies, taking net freedoms a lot of early-adopters take for granted, not like ad-block, more like not having to worry about malware being delivered to you while you're powerless to stop it.

I'm not even talking about internet surveillance, I'm talking about advertising companies delivering malware to office equipment. You know those hacks that seemingly target large databases everyday?

Paid Advertising.

Since a lot of, too many even, Internet users these days even know the basics of HTML/CSS/JS, they don't even get to see what it feels like to have the inspection tools be taken away from you so you can see how it is these websites are f* you.

I can't even [view source] on my phone anymore. *That's considered* a bigger security risk than ad-delivery hijacking *your* phone.

How much does ad delivery cost these days, and you can see, that's the price of delivering malware to the user. Not just advertising products.

[enigmalea]

Why I Contributed to FujoGuide

If you follow me here or mastodon you may have noticed that I've been reblogging/boosting a lot of posts for something called The Fujoshi Guide to Web Development (@fujowebdev). There's a good chance you followed me or know me from the Dragon Age fandom where I run communities, events, and zines and write fanfic, and you might be wondering why the sudden and drastic departure from my normal content. Why would a writer contribute to something related to webdev? Why have you stopped seeing thirst for Dragon Age characters and started seeing… whatever a FujoGuide is?

The answers to those questions (and more!) are below the cut.

My Coding Journey

I wrote my first lines of code in 1996 (yes, I'm old AF). It was the early days of the internet and tutorials for how to make your own websites were literally everywhere. You couldn't go more than two clicks without finding a how-to written in plain language. But it was painstaking and tedious. CSS didn't exist yet (literally, I started coding about six months before it was released) and even when it appeared it wasn't widely adopted or supported.

It was the "glory days" of Geocities, Myspace themes, Neopets, and Livejournal. If there was a cool site, you could use HTML and/or CSS to customize it. I honed my skills by coding so many tables character profiles for RPs, creating themes, painstakingly laying out user info pages, and building my own site.

Gradually, things changed. Web 2.0 showed up with locked down profiles and feeds you couldn't customize, free website hosts became more difficult to find, and point and click page builders became the way of the web. Shortly after, I took a long break from fandom; frustrated and disappointed with site closures, lost communities, and general fandom wank… it felt like it just wasn't worth it anymore.

I eventually came back, and when I did it meant customizing themes, figuring out how to create tools for my communities, coding tumblr pages (and learning they're not really supported on mobile), and looking at automations for my common tasks. One day, I woke up and thought, "I'm going to make a Discord bot… it can't be that hard."

So, I did it.

An Unexpected Friendship

About a month after I launched my bot to the public, I received a random Discord message from @essential-randomness. A friend had told her about my bot, and she was working on BobaBoard which needed volunteers. I was shocked. First, people were talking about my bot. Second, I wasn't a real coder. I didn't know anything! I just googled a bunch of stuff and got something working. I had no idea what I was doing.

She assured me it was okay. She was willing to teach me what I didn't know - and most of all, that she wanted my help. I took a day or two to think it over, and fatefully filled out the volunteer form. I didn't know if I could be useful or how I could be useful, but I wanted to try.

Programming Is Awful

In the years months that followed, I spent a lot of time in @essential-randomness' DMs complaining about programming… at least once I realized she wouldn't judge me. I was still very much doing things the hard way, taking hours to update a site to add a single link on all the pages. I knew there were easier methods, but I either couldn't find them or once I found them, they were filled with dense jargon which was terrifying.

"An all-in-one zero-javascript frontend architecture framework!" Is that even English? "A headless open-source CMS." Cool. Sounds good. "A full-stack SSG based on Jamstack extending React and integrating Rust-based JS." Those sure are words. With meanings. That someone knows. Not me, though.

I spent so much time looking at what sites claimed was documentation and losing my mind because I had no idea where to even start most of the time. With @essential-randomness' encouragement, I kept at it, experimenting with new things, and jumping in headfirst even when I had no idea what I was doing. And I was so glad. Where I used to struggle keeping one website updated, last year I managed to deploy and update 7 websites. Yeah, you read that right. It was amazing.

The new stuff made it all much, much easier.

An Idea Is Born

Meanwhile, we spent hours discussing why it was difficult to get fandom to try coding. Part of the barrier was the belief you must be some sort of genius or know math or that creative/humanities people can't do it. It is also partially coding communities being unfriendly to newbies and hobbyists; a culture which often thrives on debasing people's choices, deriding them for not understanding, and shouting rtfm (read the fucking manual) and lmgtfy (let me google that for you)- all of which are unhelpful at best and humiliating and abusive at worst. The tech dudebro culture can be unforgiving and mean.

The number of coding-based Discords I've left far outnumbers the ones I've stayed in.

We determined what fandom needed was a place for coders of all skill levels to come together to help and support one another; where they could learn to code and how to join open-source projects they love, and where they could make friends and connections and show off their projects whether they were new or experienced programmers.

And thus… Fandom Coders was born.

What About FujoGuide?

Of course, running a coding group and working on BobaBoard together means we spent a lot of time talking about the state of the web. We both lamented over poor documentation, jargon-rich tutorials, and guides which assume a baseline of knowledge most people don't have. What we needed to do was provide tutorials which start at the beginning… from the ground up (what is a terminal and how do I open it?) without skipping steps. What we needed to do was make those tutorials fun and appealing.

I don't remember exactly the journey it took to get us here if I'm honest. I have no clue who said it first. But I do remember I first started thinking about anthropomorphizing programming languages when we attempted to cast the languages as the Ouran High School boys… and again when I suggested we do a [TOP SECRET IN CASE WE DO IT] group project in Fandom Coders to help people learn about programming.

What I do know is that as last year ended, @essential-randomness became laser-focused on creating our gijinka and moving forward with FujoGuide… and I couldn't say no.

Okay, But… Why Contribute?

To be honest, it's not just that I was around for the birth of the idea. It's ALL of the things in this post - the culmination of three years of frustration trying to figure out what I'm doing with coding, of wading through dense documentation, of wanting to give up before I even start. It's three years of dipping my toes into toxic techbro culture before running away. All added to decades of watching the web become corporate-sanitized, frustratingly difficult to customize, increasingly less fun, and overtly hostile to fans who dare enjoy sexual content.

To sum all of this up, it's the firm belief that we desperately need a resource like this. Something that's for us, by us. Something that builds fans up, instead of tears them down; that empowers them to create for themselves and their communities what no one is creating for them. It is a project I'm deeply passionate about.

And I can't wait until we can bring it to life for you all.

[orbitwebtech]

NodeJS excels in web development with its event-driven, non-blocking I/O model, making it ideal for handling concurrent connections and real-time applications like chat apps and live streaming. Its single-threaded architecture and use of JavaScript, both on the server and client side, allow for seamless development across the entire stack. NodeJS is especially suitable for startups and projects that require fast, scalable, and high-performance solutions.

Java, on the other hand, is renowned for its robustness, security, and platform independence. It is a mature technology with a vast ecosystem and a wealth of libraries and frameworks, such as Spring and Hibernate, which facilitate the development of large-scale, enterprise-grade applications. Java's multithreading capabilities and strong memory management make it well-suited for complex, resource-intensive applications where stability and reliability are paramount.

Choosing between NodeJS and Java ultimately depends on the specific needs of your project. For real-time, scalable applications with a need for rapid development, NodeJS is a compelling choice. For enterprise-level applications requiring high stability, security, and comprehensive tool support, Java is often the preferred technology.