#this is my first codeblr post

[ufoofy]

Let's talk about filtering and mapping! 🤓

I'm working on the menu page for a restaurant, and as someone with very little frontend experience I wasn't sure how to go about parsing through a JSON file to return certain objects.

After some searching, procrastinating, going through this course, and then more searching - I finally came across the documentation I needed here!

So what is filtering and mapping? .filter() and .map() are JavaScript methods.

filter allows you to filter through an array of objects given some logic (want to find all the items with an id greater than 7? filter. Want to find all the items where the name is equal to "burger" that works too, want to add multiple conditions to find all the items with and id greater than 7 AND the name is "burger" well filter has got your back).

map is used to iterate through an array and call a function on every element in it. I used it to map each item to a list.

Here's an example: We have a JSON file of some food items.

We want to grab all the desserts from our menu and display them on the desserts page of our website. It's time to filter!

Keep in mind that the filter method returns a new array with all the objects that we want. In this case when we filter we will get an array with all the desserts.

First we import our JSON file so we can access it.

Next, we create a constant called dessertFilter which will hold our filtered array. dessertFilter will hold all items that have the type equal to dessert. In our example it will hold the chocolate cake object.

Next, we map each item from the new array to a list. This is the list that we'll see displayed on the page. You can choose which properties you want to map. We only map the name, description and price since there's no need for the user to see the item type or id.

Lastly, our return statement contains everything we will see on the page. In our return we have a header and the list of items - we wrap our list, dessertItems in an unordered list since list items need to be wrapped in either an ordered or unordered list.

Here's our result! We can style this with css later.

Cool! so we filtered for dessert but what about our other menu items? Time to make a reusable component.

The code is almost the same, but to make this component reusable we create an interface. Interfaces define objects and specify their properties. We specify an object called filterSearch that will act as a placeholder - we set it as a string since the item "types" in our JSON file are strings. (I'm using typescript which accepts interfaces but i believe vanilla javascript does not).

Now lets see the component in action

Import the component so we can call it.

When we call FilterMenu we have to include filterSearch from our interface. The component needs to know what we're looking for. Here we can set it to any valid type like "dessert", "drink", or "appetizer" and it will display them.

Woo! now we're filtering and mapping with one line of code! and we can reuse it for our other pages too.

Last thing, these methods are chainable! you can connect them and have the same logic in one constant.

Before reading the documentation, I had seperate JSON files for each menu category and was reusing the same code to map each file on each individual menu page. It was a lot of duplicate code, not great. Now, I have a single JSON file and a reusable component. It's satisying how clean it is!

Learning on your own can be frustrating sometimes, it can be hard to search for solutions when you don't know where to begin. I had never heard of filtering or mapping before this. If you're ever stuck keep pushing! there's so many resources and communities out there.

p.s. I'm open to any suggestions!

[izicodes]

Hi, Hello! It’s me, Izzy and I am back from a very long break!

For those who don’t know who I am and just saw my post, I’m Isabelle but Izzy for short (and even shorter, Izi)! I run a Codeblr blog which I post about anything coding! I try to strictly only talk about coding, programming and computer science, but frankly, I ramble on about something else eventually! Hope you’re doing well!

Now, I know I said I wouldn't come back, but that was because I suddenly became stuck on what to post about and wanted to give myself a break and figure out how to do things on my blog and my online presence in general!

So, in summary, I am back from my break very inspired and eager to help more people get into programming / get better at programming! I will go on to talk about exactly what I have been doing during my break later on in this post, but wanted to say thank you to everyone who messaged me throughout the months and saw how I was! Very thought and extra blessings from God to you, please!

Working at my new-but-not-so-new job!

Yes! So, obviously, as a 21st Century girlie, I am working! Still at the music company that I started back in January! Now that I am 8 months into the job, I feel now I am fully immersed in the job and the projects and not feeling like an outsider! I went on multiple out-the-office events with the whole company and it was nice! Some I couldn’t attend because of religious reasons, but I still had fun! I got to meet a lot more girlies at my office that I don’t usually talk to (because I’m still the only girl in the frontend engineering team but there is a backend girlie but we don’t work close together so… distance)! Cheatingly, I am always ticking the box of “code every day”! However, work has made me do more UI/UX designing + frontend programming websites which I love! Always wanted to be both and not just one or the other! We are allowed to have 2 job titles, remember? (But make sure the salary is in accordance, of course, ~)

Learning new technologies! (for fun, obviously)

By “for fun” I mean personal reasons, the technologies I learnt on a whim were not for work but because I needed to learn them for personal projects I wanted to learn! I stress again; it’s more fun to learn something because you want to and not because you have to! So, I have been learning how to create desktop applications using ElectronJS and ReactJS (React has become my best friend!). Me now compared to me when I started my break is 10x smarter I feel like! My brain has definitely expanded somewhere…!

Latest project?!

Inspired by study productivity apps and wanting to track my Korean language progress, I am making a desktop application called ‘eStudySpace’! It would be my own personal app, but I want to see if I can actually pull something like this off! Right now I have not coded anything because I want to work on the design aspect first (which is smarter and a time saver in the future), so I have been on Figma for the last 2 weeks coming up with designs!

(It looks bad, I know this is like idea no.3287368 ugh...)

Miscs

I have been learning Korean for 4 months now. 

I have plans to move to a South-Eastern country, The Philippines? Singapore? Unsure!

I do have plans to switch to a new career but that’s more like 5 years into the future! But right now, I’m happy where I am at!

[a-fox-studies]

And just like that, a year has gone by.

Hello, I'm Iris, a disabled undergrad student navigating through life. This year has been CRAZY.

If I think about it, 2024 has been a year full of treatments that haven't worked, my disability getting worse, so much pain, so much failure. I completed my first year of undergrad, and figured out routines for myself, and decided how I want my day to be structured. And I think those can count as wins too.

But I think the biggest win of all was that I made it. I made it through this hell of a year.

Looking back, a lot of people have helped me, knowingly or unknowingly.

Thankyou @studaxy for never leaving my side.

Thankyou @sadiests, @winryrockbellwannabe, @inkblotfeathers for being the positive force and motivation I needed.

Thankyou @guz013 for being patient with me lol, I know that I can be a handful sometimes.

Thankyou @montecarloedexistence for just every conversation we've had lol, you're amazing.

Thankyou @sapphicacademic for starting the AMAZING studyblr server, we even had its 1 year anniversary in november! You have changed my life, even though it may not seem like it.

Thankyou @moose-mousse for keeping the codeblr server alive and also helping me whenever I needed help and explaining concepts to me patiently. Your git tutorial is amazing!

Thankyou to all my followers, moots, others who I might forgotten to mention, and anyone who decided to like or reblog or even read through my posts. It means a lot to me <3

I don't have many high expectations of 2025. Maybe I'd complete writing my first book. Maybe I'd lose some weight. Maybe I would get cured. Maybe not. Either way, I'm excited for what the future holds for me. I am excited to meet new people, share new ideas, have deep conversations about life and goofy talks about nothing in particular. I'm excited to give all the love in my heart to the people around me, to gain opportunities to help and make other people's lives better. I'm excited to continue this journey of life, even though it sucks sometimes.

Here's to 2k25!🥂

[iz-codes]

Intro post

Hi, I'm Iz! I'm making a studyblr/codeblr to try to hold myself a little more accountable with work, school, etc. My day job is mostly writing Python and I'm currently working on a master's in computer science (in my first semester right now). I'll try to post daily progress updates and maybe pictures. If I remember to update this post then at some point it'll list tags I use!

[eroz-codes]

Education_Developer Project Lifecycle

I see a lot of people here on codeblr want to start some project but, not really know the best way to get started. To rectify this, hear is my very in depth guide on how to get started. Read this entire post (some of these are started early but its milestone is later).

Note, I highly suggest the use of Github and will be referencing some things that are specific to it (like Wikipedia pages). If you prefer some other method that's fine just be aware you may be making your life harder than it needs to be.

Milestone 1: Form Teams

Find your people, exchange contact information and determine a time to meet up, consistently. If you are working solo, ignore some of the instructions for this section. That is not to say ignore the parts about consistency and time management. In fact, because you are working solo that should be even more important.

At the first meeting establish chat service (teams, slack, google chat, discord). Establish the frequency of the meetings and how often everyone should check their messages (ex: every 24 hours). Discuss the options about the project.

Platform: Android, django, iOS, react native, etc.

IDE: Xcode, WebStorm, VSCode, etc. Note that modern IDEs now have built-in methods for sharing your editor view with teammates: code together, code with me, etc.

Backend: firebase, postgresql, not needed, etc.

Libraries

APIs you will access

Package manager: npm, yarn, gradle, etc.

Finally, discuss the roles you all want on the team, what should one person focus on, who is the manager, editor, client rep, tester, researcher, repo master, master of specific tech, analyst etc.

Deliverables:

Add a wiki page (or more) to your repo titled "Team Organization" and list there the decisions you made from above, along with any pother pertinent information for the team.

Add a page to your wiki titled "Project Description" which should be kept updated as you make decisions about your project. It should contain these sections:

Description: a short description of your project,

Technologies: a list of the technologies you plan to use: frameworks, libraries, hosting services, etc.

Client: your client's name and contact info, if you have one, otherwise just say "Startup."

Milestone 2: Personas and User Stories

If you have a client who wants you to build the app, or you have identified a group of users for your app, then try to meet with them. Ask them what they do? (that is relevant to why they will use the app), why they want the app? how do they currently do the things they want the app to do? etc. If this is a startup answer those questions and more.

The point of this section is to better understand the users of this website. You need to make personas and user stories and record them so that you can reference them as you complete this project. It is very easy to loose sight of who will be using your product and assume they know more than they actually do.

Deliverables:

Add at least three personas to your wiki. These should cover 3 distinct user-types for your app. Each Persona must have a name, photo, and personal history.

Add a "User Stories" wiki page with at least 9 user stories covering the most common use cases for your app. They should all be of the form: As <the name of one of your personas> I want a <feature> so that I can <satisfy a need>.

Milestone 3: Design

For those that are more artsy than everyone else, now is your time to shine. Use a tool like Pencil, figma, justinmind, balsamiq, mockflow.com to design your product.

Your design should include:

An image for each of the major screens and dialogs of your app. Show all the widgets in their proper placement. Name each screen and write some text to explain how actions in one screen will lead to other screens.

In the case of a widget-free apps, you should include diagrams for all the major 'areas', animation stills that detail the most common animations and game mechanics (for example, Super Mario would have a set of drawings showing Mario jumping, punching up, and landing on a Goomba's head), as well as story boards if they are more relevant to your game.

A goal of the design is for you to think about the usability of your app. Try to 'use' the app in your mind: simulate how a user might use the app. Printing the screens into sheets of paper of the correct size and shuffling them as you pretend to use the app is a very common way to test the usability.

Another goal is to save you time. Remember that making a change now, like adding or deleting a screen, is a thousand times easier than if you wait until after you have written the code.

Deliverable: Add one page to your wiki called "Design" and add the images of your design here, along with some textual description of each screen and what it is used for.

Milestone 4: Requirements

This will be the main requirements document for your project. If you were charging a client for your work, this document would form part of that contract, specifying exactly what features your software will implement. The other part of the contract would be the payment details.

The document includes the design you made before (so, embed or add links to those images) but extends on that with detailed descriptions of all the desired features.

You will also mark each feature with one of:

Required: Core functionality of the app. Must have these for it to even start working.

Desired: Added functionality, usability, features, cosmetic features.

Aspirational: Other cool stuff you would like to add

Remember: all good programmers should understate what can be done and then over deliver. If you think something is going to take you 4 weeks, tell the client it will take 8. Then, when it inevitably takes you 6 weeks, you will seem ahead of schedule. On a similar note, if the client is asking for a lot of shit, say no. Now is not the time to be a people pleaser. If you want to please them, do it as a surprise addition, after basic functionality has been achieved.

Roughly the required features are those that need to get done first before anything else can even get started: things like logins, navigation menu, connection to backend, etc. They lay the foundation for building the app. An app that only implements the required features will at most get a passing grade in the class: 70.

The desired features are what make your app worth using. They make the app functional, attractive, and easy to use. Roughly, an app that implements all the desired features gets a 90 in the class.

The aspirational features make your app a professional-quality app. Implementing some of these moves it towards 100.

Deliverables:

Make a Requirements wiki page and list your requirements there.

Each item should succinctly explain a feature.

Each one will have a number. You can add sub-numbering, 1.1, 1.2, 1.2.1, etc. if you want.

Each one will be marked as either: Required, Desired, or Aspirational.

Add all the Proof of Concept Issues to your GitHub Issues with label:enhancement, milestone:Proof Of Concept. These are what you will implement first.

Milestone 5: Research

As a developer, you need to be intimately familiar with the technologies you are or could be using. You need to understand the pros, cons, and requirements of each library and platform that is relevant to your project. Thus, you need to be up to date on technology and, since technology seems to be always changing, this will be something you need to do throughout your career.

Specifically, you need to

Know about the various platforms available to you: their options and limitations.

Know about the various libraries that you can use to make your work easier.

Download, install, and build sample 'Hello world' apps using the most promising technologies. It is not enough to just read about it, you have to do it in order to learn.

Learn how to use the specific framework+libraries you choose to use for the project by building little apps with them.

Learn to use your package manager.

All of the above needs to be done before you start coding together with your team. Do not assume your teammates will teach you. You are responsible for learning.

This milestone will take a lot of time and work, which is why you should start working on this milestone as soon as that first meeting occurs where you discussion options.

Deliverable: Create a separate repo (I suggest naming it research-<projectname>) where you will place your sample project built using your team's chosen framework. The project will be more than just "hello world", or cut-n-paste from a tutorial. Start with tutorial code but, add you own code to their code. The app should have some minimal interactivity: user enters some data, program does something with it and shows the user.

Milestone 6: Architecture

Now that you are comfortable working with your chosen framework, you will write a document that roughly describes the big parts of your code. The structure will depend a lot on your chosen framework.

If you are building a webapp then you will probably list the set of database tables (models, for example: rails:ActiveRecords, meteor:Collections, etc), the set Views, and the set of Controllers. For webapps you should also list the of your URLs app, and what lives at each one.

If you are building an Android app then you will list your Activities or Fragments, along with their corresponding Views, as well as your model Java classes. You will also list your database tables (firebase, sqlite, localStorage, etc) if you need persistence, which almost everyone does.

Think deeply about your design. Go over the most common use-cases and check how those will be accomplished in code: which methods will be invoked? do the methods have references to all the objects they need in order to perform their job? Remember that your main goal is *de-coupling** the various classes: the fewer references (method arguments, global variables) they need, the easier your life will be.

Deliverable: Add architecture document to the wiki containing:

List all the languages/frameworks/libraries/services/APIs you plan to use. Explain how they will tie together. For example: This will be a native Android app written in Kotlin, using the android.graphics library, using firebase real-time database for cloud data, and firebase authentication for user accounts.

What package/build manager will you use? npm, gradle, yarn, flutter, pipenv, etc.

List what each person will work on. Everyone must make significant code contributions, or they will fail the class, see Syllabus.

Make sure all the images (if any) are embedded in the wiki page and hosted at GitHub.

Make sure the wiki page is easy to read.

If you are building a webapp:

Deployment How will you deploy? Which hosting provider(s)? Automation? Scripts? Explain.

Are you using Virtual Machines (vmware, vbox, etc) or Containers (docker) for development or deployment? Explain.

Is it a SPA or traditional? or mix? Explain. (My web application development lectures explain the difference.)

List of URLs you will implement. Explain any search arguments in English. Link (actual hyperlink) each URL to the page it shows in your Detailed Design milestone.

If implementing a REST API, document it. List all methods, parameters, and give English description of what they do.

The Views of your app. Embed the images from your Design Milestone. Typically, a webpage includes multiple views. For example, this webpage has a Header, Menu, and Content views (at least).

The Database schema: set of tables/documents with list of attributes and their types. Describe each table and attribute in English.

List of common queries you expect will be needed. Do any of then need to join tables?

If you are building a mobile or desktop app:

Release: How will you create and deliver a binary to testers? Explain. Note that the testers include us (the teachers of this class, when we grade your app). You must deliver a simple to install app: double-click to install.

Are you using Virtual Machines (vmware, vbox, etc) or Containers (docker) for development? If so, explain.

The Models for your app. These could be UML class diagrams, or just models with attributes (with type) and descriptions (in English).

How will your app maintain state? in memory? or database? or both? Note this in your Model Classes.

If you are using a db-backend (say firebase) then include the Database schema: set of tables/documents with list of attributes and their types.

List of common queries you expect will be needed. Do any of then need to join tables?

The Views of your app: name, describe. Embed the images from your Design Milestone. Typically, one page in the app is composed of multiple View elements.

Below will be complete as I do for my Capstone project.

Source Control

Ethical, Legal, and Security Considerations

Proof of Concept (PoC)

PoC Demo

Testing

Beta Release

RC1 Release

Quality Assurance

Website

1.0 Release

Final Demo Video

[codemerything]

building for fun & learning too

The last programming-related post I made was a while ago, you can check it out here and I hope to update it soon too. I have been learning in private without sharing (working on sharing my progress I hope I have the strength). I'll share new concepts I encountered while building projects and maybe talk about them more.

I recently started building Jokes Hub, I'd like to think of it as a repository for jokes and I want it to grow into a huge huge, where you can generate jokes with just a click; a twist to the generic "Joke Generator App".

Concepts or things I encountered for the first time while building Jokes Hub 1. Clipboard API: I needed people to easily copy the jokes and share them with friends but I also needed it to show the user that it has been clicked and that's how the research led me to

Code explanation: When a user clicks on the button "Copy Button" (on the left), it copies the content of the ".JokeText" into your computers clipboard and changes the text to "Copied" (on the right)

and reverts back to the text on your left after 500ms to let the user know they can copy more.

Please feel free to contribute to this project I would love to build this with everyone on codeblr, no pressure. It's just for fun, just clone the repo and let's build this together. I am sure I can learn a thing or two from you! Have a great week.

[brightgreendandelions]

i can also be found here: @green@mk.absturztau.be

horny sideblog: @darkmagentapetunias

backup sideblog with more reblogs: @brightergreendandelions

Pinned Post

hi! i am a person here (tumblr) and there (neocities pronouns)

you can call me Green or Dandelions!!

all my mutuals are very cool! and some of them are even Important and Popular!

some organizational tags (they are clickable!!):

#textpost -- my posts that aren't reblogs

#ask -- asks asked of me

#ask answered -- asks asked by me

#slugcat chronicles -- my rain world let's play

#queue -- self explanatory

#rain world -- is a fandom i like

#secret colors -- posts with custom html colors

#greenposting -- posts about me

#codeblr -- coding posts

Notable Posts:

the post about keyboard switches

the post about my moots

the list of my neurodivergent-ish traits

my first post about Math

my post about imap

a post about redditors being horny. for more horny activity refer to my alt blog

a viral post about egyptian boyfriends

⚠️under construction⚠️

(the rats are still making this post)

[mousiecat]

♥ ♡ Intro Post! ♡ ♥

post update (10/17/23)

uhh okay so eventually this will be more about coding again but I've been too busy

but I'm just gonna reblog and talk about whatever

---------------------------------------

Hi, I’m mousiecat 🐭🐱

I'm so excited to participate in the Codeblr community!

I'd love it if you checked out my Neocities!

If you're on Neocities, you can follow me here :)

♥　♡　♥　♡　♥　♡　♥ 　♡　♥　♡　♥　♡　♥

First, my main tags:

meow squeak - me! my own posts! includes asks

Reference - coding info to refer back to

Resources - useful tools and libraries

Learning Resources - tutorials, games, projects, or webinars for learning

Web Accessibility - learn to make things more accessible!

Goodies - yummy pixels and art that creators have shared for public use on your webbies ~ (always follow creators' crediting guidelines!)

♥　♡　♥　♡　♥　♡　♥ 　♡　♥　♡　♥　♡　♥

Read more for more about me!

Coding Origins

The golden age of Neopets! It was an HTML/CSS wonderland! You could catch my kid self building Sailor Moon guilds, spicing up my shop, and customizing my pet pages.

♥　♡　♥　♡　♥　♡　♥ 　♡　♥　♡　♥　♡　♥

Coding Rebirth

A bit ago, in a fit of nostalgia, I surfed Geocities archives and longed for the days the creative web still existed. Then I realized...HTML/CSS are still around, and people are still making cute, fun, independent sites with it. You don’t have to resort to uploading content to some billionaire’s website--you can still make your own!

So, I got on the Neocities train, and I've been really excited about the endless possibilities with coding! I especially love that, if you are able to access a consistent computer and internet connection, you can do everything else for FREE! Learning, creating, publishing, all of it. Kinda kickass.

♥　♡　♥　♡　♥　♡　♥ 　♡　♥　♡　♥　♡　♥

Currently Learning:

HTML/CSS, and soon JavaScript with FreeCodeCamp

Learning a bit of Python with Udemy (mostly to connect with a local lesbian coding group)

Attending random Meetup coding events until I find my groove~

♥　♡　♥　♡　♥　♡　♥ 　♡　♥　♡　♥　♡　♥

Goals:

My primary goals are fun and creativity! I especially wanna make cute lil games and activities for silly webpages :)

More and more, I also want to find ways to use coding for liberatory organizing, especially abolition, sex worker advocacy, and reproductive justice work. So far I've made a cute page for an event, and I've got some ideas for simple educational games :) I'd love to strategize beyond this ~~~~~

Down the line it could be really cool to get a paying gig, but it's not my central motive

I just want to keep learning more so I have a better sense of all the possibilities!!! Let's get this party STARTED!

♥　♡　♥　♡　♥　♡　♥ 　♡　♥　♡　♥　♡　♥

Codeblr Goals:

You know…I’ll post when I post and I won’t when I won’t! I have ADHD, so out of love for myself I don’t give myself assignments when I don’t have to. So, I’m not trying to post every day or anything. I just want a lil outlet for it when I’m feeling it! I love learning from everyone here, and it would be amazing to make connections!

[moose-mousse]

What to do when you spot a broken website

I am a very firm believer in either sticking to your principles or update them.

So when I got this error while I tried to search for C/C++ on my national job portal:

My first thought was "Huh, that is sorta funny" (especially since the code to show me the email address to report this error to was ALSO broken... meaning that whoever made the code that should run if the website broke... never tested it). And then I realized what I was looking at.

And at that point I think I had a ethical duty to notify people to get this fixed. FAST. Why?

It comes under "You are responsible for your choices". With it being understood that doing nothing is also a choice, and that taking a job where you work for, and help a company with doing evil is NOT a choice, if that is the only job you could get (IE, you did not have the power/money/mental health/time to make a choice)

It is now fixed*, so I wanted to make this post for all in the little codeblr community doing any front-end work. Web or not. With 3 lessons to learn from this.

First thing to get from this: "Everyone makes mistakes". This is one of the reason good code is not code without errors. It is code where it is easy to make changes and fix errors. You then try to find as many errors as you can with code reviews, automated testing, having a work environment that does not punish human errors( which encourages people to HIDE errors ) and so on.

Second thing: "Sanitize your user input. Always". Write code that assumes that every single user wants nothing more than to break your code and exploit its vulnerabilities.

This had NOT been done here. This error shows that characters in the string that was made from my search terms, was being run as code. As in, I, or anyone else, could run code in the middle of this javascript code. Meaning it is possible that someone could write code as part of their search that would make the javascript code do... whatever they wanted to. Including deleting the entire backend database. Or steal the info. This is why you ALWAYS sanitize your user input. Basically encode all potentially dangerous characters as something else while working on them. There are libraries like validator.js and express-validator that will do it for you, if you use javascript.

And the third thing. "Do NOT investigate further" . As soon as you confirm that your user input gets treated as code, you contact whoever is running it. If they do not take the threat seriously and it is still there after a week or two, contact established press with this info. You may read about so called grey hat hackers, who unlike black hat hackers(who is people wishing to do harm) or white hat hackers(Who are hired to try to break into a companies software to test it), are trying to find security flaws with good intentions, but are unaffiliated with whoevers code they are trying to break into. In an ideal world, doing that, and then contacting the company, SHOULD result in the company thanking them . But often it also leads to the company suing. And winning. Since breaking in to show that it is possible, is technically still breaking in. So do NOT start testing what you are able to do with the exploit you found. Report it to them, and check a weeks time later if it is fixed. If it keeps being vulnerable, contact the press. The site fixed this error after half a week. But they did it, not by encoding the dangerous characters into something else, but to simply remove them all from the user input string. Meaning that I still cannot search for "C++". Now I just get any job that contains the letter "C"... I mean... it is better... So if you take user input, and it does not brick your code in dangerous ways. You are doing better than whoever coded this for the Danish State :p

[mckencodes]

Hello World!

This is my first post into the studyblr, codeblr community! This will be a coding/software development blog. I decided to start posting here to give me motivation to be more productive, keep track of my progress, and maybe meet/interact with other people. I’m not too sure how this works so pls be kind.

Some basic facts about me:

My name is Mckenna

My pronouns are She/Her

I’m based in the USA specifically the Southeast

My biggest interests are web development, VR gaming, and mobile app development.

Strongest languages are Javascript and Python. I’m currently learning JavaScript frameworks, mostly React.

Main account: @softpaperback

tags: daily logs // weekly logs

-- updated: 6/15/24 --

[ghostedcat-2nd-remix]

My Data Visualization Project isn't working (for now)

Hi everyone,

I hadn't been updating my codeblr blog since I made my first post. I've been dealing with transferring to another university and the up's and down's of my mental health.

I've been using the Odin Project to learn more HTML/CSS fundamentals, but I decided to work on a data visual project I did from a class a couple months ago.

AND THE THING DOESN'T WORK ON THE IDE.

For context, I took a class about using D3.js to visualize data, mostly using .csv and json files. To use it, I have to put a link in my html file, something like this "<script src="https://d3js.org/d3.v7.min.js"></script>". It's been a hot minute since I looked into it. But then today I saw that the library is only hosted on Observable. And the file they have to use it on a IDE has errors, and the whole file with thousands of characters is ONE LINE.

So now I have to learn to use Observable so that I can get my project up and running. I was really proud of it too.

*Le sigh*

So this could be Codeblr Day 2.

[izicodes]

Hello Loa. I kept thinking about making a post, but I thought it was too emotional of me and I don't like to be so emotional. But I just wanted to thank you for all your time invested in this community (you could be using your time to do something else and you're here) because codeblr really started with you. You spend your time writing texts gathering resources, giving support and always encouraging and sharing new profiles that are starting. This is very big and important. And that's why I also like to call you the queen of the tumblr code community . Once more, thank you.

Now to close, if you want to answer. What advice would you give to your past version and what do you think could help others at the same time (regardless of what it is)?

Hiya Bea! 💗

I'm truly moved by your message and honestly, there's nothing wrong with being emotional. It's heartfelt messages like yours that make all the time and effort spent on this community worthwhile~! 🌷

When I started this blog, there were two blogs I could find that were “codeblr��� related that I followed! Sadly after a month, one deleted their blog and the other stopped posting so, to me, I was the only one left. I continued to post because I hoped to create a space where everyone who shares this love for coding could learn, grow, and connect. I wanted a Codeblr community and I wanted it to grow! I’m even more happy that now there’s lots of more women programmers to connect with as well! To know that me posting about my code for the day made such a difference is incredibly rewarding~! 🌻

I think a few months after I created my blog, you @web-dev-with-bea came along, around the same time @code-es joined too! I was sooooo excited as I was like “New coding bloggers! Yay! And they’re girlies like me? Double yay!” and started interacting with you two more! I loved see you two post about your progress~! 🌹

It's been a pleasure watching this community blossom into the vibrant digital garden that it is today. Each new 'flower' (or coder, in our case) brings a unique color and beauty to our shared space. I may have planted the first seed with my first post about learning Java, but it's thanks to everyone here, including you, that this garden has grown so beautifully~! 💐 (Trying to be poetic…)

As for the title 'queen of the Codeblr community', I humbly accept 👸🏾 but only with the understanding that a queen is nothing without the support. I want to thank YOU, as well. Your participation, your eagerness to learn and contribute, help and encourage literal strangers on the internet, are what truly define our community~! 🌺

Lastly, if I could reach back in time to speak to my past self, there are several things I'd say, which I believe can also serve as advice to others:

Start where you are with what you have

Embrace failure as a part of the process

Consistency is key

Don't shy away from asking for help

Celebrate every victory, no matter how small

Be your own cheerleader

Keep the bigger picture in mind

Take care of yourself

Thanks Bea for this amazing ask 💗

[a-fox-studies]

Little update from my end . . .

I haven't been posting a lot lately because my health has been deteriorating a lot. I'm trying to come to terms with my new symptoms but it's really hard and its taking a toll on my mental health. I was supposed to attend my practical exams today but this morning I couldn't take it any longer and broke down completely. I flared up so bad and I decided to prioritize my health over academics. I still have three practical exams to attend but I decided I'll retake them the next year because I don't think my body will be able to handle studying anymore and I'm scared something might happen to me if I overexert myself any further.

So this means I technically completed my first year of uni!!! That's a good thing, right?

Anywho, I'm going to take all the rest I need before starting on the activities I've planned for the "holidays", because my brain really needs the "do nothing period" to recover from whatever the hell these past three months were. Special shoutouts to @studaxy @sadiewayne @winryrockbellwannabe for getting me through my first year, y'all are blessings to have in life <333

Stay tuned for langblr, codeblr and other non-uni related fun posts once I recover a little :D thankyou for sticking with me for more than a year, really grateful to all of my followers <3

[vexacarnivorous]

Coding Language Tag Game!

Rules: Talk about your most favourite and least favourite coding language, and tag more codeblrs to do the same!

Tagged by: @a-fox-studies

I think this is actually a very funny tag game for us to start with because:

While I have written at least three lines of code in like eight separate coding languages, I've only written at least four lines of code in about three, so you can imagine how much I don't know (which is everything, btw);

There is no second point. I genuinely only have real experience in Python, HTML, and CSS, & even then I'm certainly no expert in any of them. I'm a baby codeblr really

That said: I love the versatility of Python, I think it's sexy af, and it was my first coding language. Sentimentality at this point demands it be my favourite. I also love Malbolge, which is ACTUALLY the worst programming language, but I think it's extremely funny performance art. Please look at this tumblr post

The worst: can I say Python again (/j)? Hmm... no, I guess maybe Assembly? We had to take a look at it in class once and I had no idea what was happening at all, but the other day I was listening to Darknet Diaries and this one lady was talking about Assembly with such love and passion that it's kinda motivated me into looking at it again

No pressure tags: @maiacodes, @wallf1ower, @zoeythebee, @tiredcoding, @inkcipher, @kitkatcodes, @404icy, @web-dev-with-bea, @code-es (I want to get to know you guys, but dwbi if you guys don't want to join in!)

[codemerything]

Coding Language Tag Game!

Rules: Talk about your most favourite and least favourite coding language, and tag more codeblrs to do the same!

Tagged by: @a-fox-studies @wallf1ower

Killing two requests with one post, Thank you guys for tagging me I haven't written anything here for a really long time and I love that you guys thought of me, Thank you.

I will start with least favourite but not for the reasons you guys may think: C

Circa 2019/2020: My C teacher was really good at explaining C and giving us exercises but that was just it. We didn't build anything mindblowing and the syntax was just too cumbersome for a small task, so many lines of code for doing something really small it didn't seem like it was tech-forward and I just thought they had to be other languages that could do this with less code and better syntax.

My favourite is Python and Javascript

Python-- When I was probably in my early teens when I first saw "Nikita" she was talking to her computer and it could talk back to her, when I first researched Python and was learning it in 2021 I just knew that was AI Nikita had in her hideout was done with Python, those were my first thought and I immediately jumped on it and learned the basics, the syntax was easy to understand, it was straightforward, really great if you ask me but I had to abandon it because at the time I couldn't find a community and this was pre-CHATGPT so... I would get lost and googling was a lot. Things have changed since 2021 and I would love to revisit it sometime.

My ultimate favourite is Javascript:

I'll list why:

There's a wide community of people using it, you will never feel alone.

It's a multi-purpose language, you can use it to build almost anything and it just keeps getting better.

You don't need a special teacher, school or compulsory to learn the language, you can just learn from the web there are loads of free resources and most of it is free. $FREE.99

I love how everything in Javascript is somehow connected, the language has so many easter eggs and the deeper you get into the language the more you'll discover it. "Oh, so a method is basically a function but a function in an object! Wow!" It's just a beautiful language.

Thanks for reading! I'm tagging: @cherrypikkins @xiacodes @codelore @web-dev-with-bea @crazypaine

[cyndaquirl]

Coding Language Tag Game

thanks for tagging me, @a-fox-studies !! honestly i hardly ever post about anything cs related on here and i just reblog things i like, but i love talking about this stuff to thank u for thinking of me.

Rules: Talk about your most favourite and least favourite coding language, and tag more codeblrs to do the same!

Least favourite: honestly, idk if this is an unpopular opinion or not, but probably Java.

My reasoning is that there’s really nothing Java can do that another language can’t do better. If I wanted to write fast/efficient code, I would choose C or Rust. If I wanted to write expressive or visually satisfying code, or if I wanted to just quickly throw a program together, I would choose Python. To me, Java is pretty clunky. Although it does have its merits, it’s definitely not my favourite to write in. Despite this, it’s probably the language I have the most experience writing in since so many of my programming courses have used it lol. Also, Java taught me OOP, so I have to give it some credit for that.

Favourite: I can’t rly choose one so I will say both C and Python

C was the first (real) language I learned so I will probably always have a soft spot for it. I also think C is one of the most important languages to learn because it forces the programmer to actually learn about the computer itself, since memory management is so manual in C. I truly think that understanding the machine at a fundamental level makes a much better programmer. Also, C can be wicked fast if you know what you’re doing.

And I love Python because it’s so easy. It’s simple and beautiful and has a ton of really powerful libraries. It can be a little slow, but it makes up for it with how intuitive it is to write with. There’s nothing more satisfying than finding a way to translate a relatively complex algorithm into, like, 3 lines of Python code. I use Python for my ML projects and it makes the code much more readable. I don’t always love the dynamic typing, but it definitely comes in handy sometimes.

(idk who to tag who hasn’t already been tagged, so if ur reading this consider urself tagged if u want to be)