#software development.

[geminisee]

x

[development-stratagem]

Laravel stands out as a powerful backend framework for mobile app development, offering a host of features tailored to simplify the development process. With its intuitive MVC architecture, flexible testing options, and extensive documentation, Laravel empowers developers to create scalable and robust applications. Its popularity, supported by a large developer community and a range of successful use cases spanning from e-learning platforms to CMS systems, highlights its versatility and reliability in meeting diverse app development needs.

[nyaa]

北へ。/ Kita e. White Illumination (1999) Sega Dreamcast

[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

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

[nixcraft]

[dammjamboy]

BETTER CALL SAUL!

[computer-nerd-girl]

[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

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

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

[development-stratagem]

Boost your Angular app's online presence and make users happier with these easy SEO tips. Start by making your URLs straightforward and filled with keywords related to your content. Also, tweak your meta tags to catch the eye of search engines. Focus on creating quality content that users find valuable and engaging. To make sure your app ranks well in search results, use server-side rendering and deal with duplicate content wisely. Enhance your app's speed and user-friendliness by linking to relevant internal and external resources. Keep an eye on your SEO progress using analytics tools, so you can keep improving over time. Want to know about how to build a seo friendly angular application(Read More)

[wayfire-official]

Tonight I woke up at 4am due to considerable stomach pain, and in my half-sleep I was very convinced that it was because of a bug in a script my belly was running, and I spent half an hour dream-debugging it to no avail until I finally realised that my belly doesn't run scripts

[locusfandomtime]

you can really tell the different audience demographics of Lifesteal vs Hermitcraft by the comment sections because the average spokeishere or whatever comment is like “LIKE THIS if you are a real Spoke fan!!! ❤️👊😎 if this comment gets 100 LIKES ill tell my mom to subscribe 🤪 who else is watching in 2028❓❓😂” whilst the average ethoslab comment is like “my wife is giving birth but this is more important”

[mapsontheweb]

Software Engineer Pay Bubble Map of Europe

by zuhayeer/reddit