#Software development

[therian-database]

Hello there!

so, here's the deal:

I, a burnt out autistic highschooler, want to create an app for therians (as a therian myself).

Here's the basic features:

A database full of information on as many animals as possible (that can and will be updated!)

Blank templates for otherkins!

Each user has a profile- public or private- and can add theriotypes and notes about those theriotypes!

A journal feature where you can add pictures, drawings, and notes to a digital journal, similar to a glorified notes app lol- and you can make certain parts of your journal public or private!

Packs!

What are packs?

Have some word soup as an explanation: Basically if you want to create a pack to either make friends or add your friends, you can submit a pack request, where you explain why you want to make a pack and if you have specific people in mind to join, and I'm thinking that I don't want it to be like everyone has their own pack or whatever so that's why it has to be approved and stuff like I don't want too many different packs. Basically it's like a discord server or an amino thingy it's a big group chat and the pack creators can set up virtual events and send out pings like "hey! Join this zoom call if you wanna do some arts and crafts!!" Or smth like that

It's a database and a community!! If you would like to help out, please please please send an ask!! I would love all the support I can get!

P.S.

BE NICE AND DRINK WATER

[irradiate-space]

Last week I spent 30 hours debugging a problem in our code that turned out to be a 5-year-old bug in an industry-standard open-source third-party library.

You betcha I wrote that up in my local team chat, my company chat, my ticket manager, and in a dry comment on the relevant third-party issue tracker.

least favorite part of job is how they expect me to write bland pull request descriptions for shit that fucking broke me. "ensures the frobnicator tool preserves the new frobnicator metadata fields instead of burying them under a tree by the light of the full moon," i write. "note that google.protobuf.json_format defaults to exporting fields in camelCase rather than snake_case, but bufbuild's generated load-from-json code refuses to even acknowledge the existence of camelCase fields, ignoring them as an Edwardian society lady might disdain a bootblack. this diff may be only ten lines long but the process of creating it has destroyed my will to live. let's all join hands and walk into the bay together so we never have to think about camel case or protobuf oneofs ever again."

and then i backspace all of it and write something normal

[american-boyboss]

[geminisee]

x

[heart-ghost-studyblr]

Getting old is interesting. I've always been a middle ground between sports (skateboarding, surfing, jiu-jitsu) and an avid student. Over time, it's clear that you can't keep trying the same tricks, just as you can't study the same way.

Today, as I'm writing an article about event-driven architectures, I realize that final exams in college were much easier, just like it's not as easy to jump the same stairs on a skateboard as I did when I was 18. In the image, you can see my favorite note-taking app, Obsidian, and my Neovim terminal. I'm diving deep into Java, and for that, I'm taking a Spring Boot bootcamp offered by Claro through the DIO Innovation One platform.

[nixcraft]

[sreegs]

the past few years, every software developer that has extensive experience, and knows what they're talking about, has had pretty much the same opinion on LLM code assistants: they're OK for some tasks but generally shit. Having something that automates code writing is not new. Codegen before AI were scripts that generated code that you have to write for a task, but is so repetitive it's a genuine time saver to have a script do it.

this is largely the best that LLMs can do with code, but they're still not as good as a simple script because of the inherently unreliable nature of LLMs being a big honkin statistical model and not a purpose-built machine.

none of the senior devs that say this are out there shouting on the rooftops that LLMs are evil and they're going to replace us. because we've been through this concept so many times over many years. Automation does not eliminate coding jobs, it saves time to focus on other work.

the one thing I wish senior devs would warn newbies is that you should not rely on LLMs for anything substantial. you should definitely not use it as a learning tool. it will hinder you in the long run because you don't practice the eternally useful skill of "reading things and experimenting until you figure it out". You will never stop reading things and experimenting until you figure it out. Senior devs may have more institutional knowledge and better instincts but they still encounter things that are new to them and they trip through it like a newbie would. this is called "practice" and you need it to learn things

[moose-mousse]

Ok. I am going to let you in on a secret about how to make programming projects.

You know how people write really good code? Easy to read, easy to work with, easy to understand and very efficient?

By refactoring.

The idea that you write glorious nice code straight is an insane myth that comes from thinking tutorials is how people actually code.

That is because programming is just writing. Nothing more. Same as all other writing.

The hobbit is ~95000 words.

Do you think Tolkien created the Hobbit by writing 95 thousand words?

Of course not! He wrote many many times that. Storylines that ended up scrapped or integrated in other ways, sections that got rewritten, dialog written again and again as the rest of the story happened. Background details filled in after the story had settled down

Writing. Is. Rewriting.

Coding. Is. Refactoring.

Step 1 in programming is proof of concept. Start with the most dangerous part of your project ( danger = how little experience you have with it * how critical it is for your project to work )

Get it to do... anything.

Make proof of concept code for all the most dangerous parts of the project. Ideally there is only 1 of these. If there is more than 3 then your project is too big. ( yes, this means your projects needs to be TINY )

Then write and refactor code to get a minimum viable pruduct. It should do JUUUUUST the most important critical things.

Now you have a proper codebase. Now everytime you need to expand or fix things, also refactor the code you touch in order to do this. Make it a little bit nicer and better. Write unit tests for it. The works.

After a while, the code that works perfectly and never needs to be touched is hard to read. Which does not matter because you will never read it

And the code that you need to change often is the nicest code in the codebase.

TRYING TO GUESS AHEAD OF TIME WHAT PARTS OF THE CODE WILL BE CHANGED OFTEN IS A FOOLS ERRAND.

( also, use git. Dear god use git and commit no more than 10 lines at once and write telling descriptions for each. GIT shows WHAT you did. YOU write WHY you did it )

Is this how to make your hobby project?

Yes. And also how all good software everywhere is made.

[la-principessa-nuova]

I made a support request with a vendor asking if there’s a way to leverage the logic they already have for determining what counts as a business day (it is very critical that this is done exactly correctly and that it never breaks in the future if nobody is maintaining it) when using their API since I didn’t want to have to maintain a separate source of truth for it, and in their response they said:

it is not too hard to do date/timestamp arithmetic

which any developer who has done date/time arithmetic knows is the understatement of the century

Famously everyone thinks so until they take down an important system by forgetting about DST, or leap years, or that leap years don’t happen every 100 years, or that they do happen every 400 years, or not considering implications of people using different calendar systems, even if they’re just slightly different like having weeks start on a different day, or they consider whether the first week of the month is the first full week or the partial week before that, or they format it in a different order.

Then when they finally think, “OK, but I know about that,” then they learn about the leap second, or the negative leap second.

So yes, date math is “too hard”.

[mlembug]

the current landscape of webdev needs to know that I don't need web applications that scale up to millions of users, I need web applications that scale down to 5 users or less

[blur-from-the-north]

November 1, 2001. Oulu, Finland. Agfa ePhoto CL18.

This was my workstation at the software development job I had at the time. As you can tell from the amount of caffeine implied. This office was at Technopolis in Linnanmaa. The company isn't there any more. It's nowhere.

[jay0fspad3s]

I swear that half of programming is staring at your screen going "how do I do this" and the other half is figuring out why something doesn't work and being like, "oh duh I'm just fucking stupid"

[sillygarlicbrind]

IM COOKING SO HARD RN, IT FEELS LIKE IM GONNA BE DONE IN TIME, HOLY SHIT

This is my first time doing genuine pixel art istg. OBV ITS NOT DONE YET BUT LIKE???

[izicodes]

C# Study Links | Resources ✨

As I am starting to relearn C#, I thought why not share some links that have helped me in the past and what new ones I will be using this time to learn! I already made a similar resource post (post 1 | post 2) for C# in the past but why not a new one? 🤗

Microsoft Learn - LINK

C# Station - LINK

YouTube - LINK

SoloLearn - LINK

Codecademy - LINK

Learn C# - LINK

C# Yellow Book - LINK

C# Programming Guide - LINK

Tutorials Point - LINK

Roadmap to ASP.NET Core Developer (C#): LINK

C# Subreddit - LINK

Dot Net Perls - LINK

C# Coding Conventions - LINK

The Ultimate C# Guide For Beginners - LINK

That's all for now! If this does interests you, do check out the other posts (1 | 2) I made of other C# resources!

Happy coding/programming! 😎💻👍🏾

[heart-ghost-studyblr]

I found myself surrounded by companions daring to tackle a real software architecture challenge. We shared a good wine and cheese to conquer it together! (Unfortunately, there’s always something waiting to be dealt with on Monday.)

The glow of my Neovim terminal in Monokai theme reflects my rhythm — a guy who doesn’t stop on weekends but knows that balance isn’t about being all-in, all day.

The setup screams character: a seamless fusion of productivity and comfort. Lazygit commands at my fingertips, a Ghibli-esque avatar paired with Neofetch adding a touch of Tumblr aesthetic, and a playlist of Korean indie OSTs playing in the background to add depth to every keystroke.

This is how I drive — in code, creativity, and moments that are unapologetically mine.