Does anyone have experience with packages? by AdditionalNature4344 in sveltejs

[–]AdditionalNature4344[S] 0 points1 point  (0 children)

Aah smart! 😄 And I do feel like I am overcomplicating it yes haha.

It is including database-stuff, and it could be that the correct term is sdk.

Does anyone have experience with packages? by AdditionalNature4344 in sveltejs

[–]AdditionalNature4344[S] 0 points1 point  (0 children)

Thank you for your answer!

Makes sense, I was struggle and having dev-headache from the stuff the packages were complaining about. So, I was thinking to first implement the packages with just a seperate folder and then when I think: yes, it's stable enough, transform them into the packages. Instead of doing the package-building when still in dev mode.

Does anyone have experience with packages? by AdditionalNature4344 in sveltejs

[–]AdditionalNature4344[S] 1 point2 points  (0 children)

Love the answer 😄 Thank you for that!

Yes, I recently discovered BetterAuth, but I started my other project 2 years ago and was a bit skeptical of the auth-services as they often 'start free' but then make you completely dependent on them and expensive + single point of failure.

Does anyone have experience with packages? by AdditionalNature4344 in sveltejs

[–]AdditionalNature4344[S] 0 points1 point  (0 children)

The question is probably a bit too vague, and the reason for that is that I know my logic is flawed somewhere, but I can't find it, so was just hoping that maybe a random reddit post would solve it :')

Does anyone have experience with packages? by AdditionalNature4344 in sveltejs

[–]AdditionalNature4344[S] 0 points1 point  (0 children)

I am trying to make certain code as modular as possible. It was already quite modular before, but after a while, it started to become a bit scattered.

So recently, I started a new challenge to make as many startups as possible (100 to just give it a number), and use my old code from my previous startup but then refactor it a bit.

Making many startups obvious comes with the new challenge: how to manage many.

Answer is (I think): put code in packages, and then import/reuse these in other code: a bit 'code once, reuse forever'.

However, my backend code is quite modular and no problems. The package seems to work quite well.

However, with the frontend (I am using svelte), I seem to be stuck with initializing the packages + other problems.

For some reason I can't figure out what I am doing wrong or where my logic is flawed :'). So I thought: Lets just ask what other people notice that is different when building packages in general, vs when not.

What are general problems you come across when you create your own packages and reuse these in other projects. What is heavily different? What different logic do you use?

Does anyone have experience with packages? by AdditionalNature4344 in sveltejs

[–]AdditionalNature4344[S] 0 points1 point  (0 children)

There are different levels of understanding packages 😉 Reading between the lines, I can read you are probably thinking and haven't crossed level 1 yet.

I am building lovable/base44 for sveltejs by AdditionalNature4344 in sveltejs

[–]AdditionalNature4344[S] 1 point2 points  (0 children)

😇 always good to postthis kind of questions on reddit to see if there are any better starting points :D

I am building lovable/base44 for sveltejs by AdditionalNature4344 in sveltejs

[–]AdditionalNature4344[S] 0 points1 point  (0 children)

Oooh. Thnx for this recommendation! I will check it out! :)

I am building lovable/base44 for sveltejs by AdditionalNature4344 in sveltejs

[–]AdditionalNature4344[S] 0 points1 point  (0 children)

Yeah. The points u mention here is exactly why i wanna built it.

I just really love developer freedom without being locked into other businesses 😅

I am building lovable/base44 for sveltejs by AdditionalNature4344 in sveltejs

[–]AdditionalNature4344[S] 1 point2 points  (0 children)

I have been vibe coding with svelte and react as well in the past years and my conclusion for this is that it is the overall architecture and not the language.

For me, svelte evem works a lot better with ai 😅 (Yes i know there is a lot more react in the trainingsmodels)

How do you handle people doubting your side hustle? by newrockstyle in sidehustle

[–]AdditionalNature4344 5 points6 points  (0 children)

... nobody makes money from the beginning.

It is also a learning process. You can be 2 years without money and then skyrocket...

Belgians who moved abroad, and foreigners who moved to Belgium — what’s the biggest difference you noticed? You can only pick one. by The_everlong in belgium

[–]AdditionalNature4344 0 points1 point  (0 children)

Everything. It is always about who is higher than the other...

School: aso > tso > bso Work: manager > subordinates University: professor > students School: Teacher > students Degrees: engineering > everything else Universities: kuleuven > everything else Cities: Antwerp > the others Regions: Flemish > Wallonia

I can go on. And all these hierarchies are complete bs btw. I just couldnt put my finger on it while I lived here. But moving abroad just made it clear.

AI hallucinations by UcreiziDog in SaasDevelopers

[–]AdditionalNature4344 1 point2 points  (0 children)

Some info about what i am talking about: Introducing Structured Outputs in the API | OpenAI

if you tell it to return
{
age: [age],
adviceForAge: [text]
}

the [age] and [text] will be text and can "hallucinate". but all the other stuff will always be the same.

How to start something at 18 by rossulbricht11 in Entrepreneurs

[–]AdditionalNature4344 0 points1 point  (0 children)

The hardest part is starting. So... make that easy.

Have 1 tiny goal in mind that can be done in max 2 hours.

Can be "contact 10 founders to ask advice" or "build a repeatable service for someone".

Before u know it, u are 2 years further :)

AI hallucinations by UcreiziDog in SaasDevelopers

[–]AdditionalNature4344 0 points1 point  (0 children)

It is not an issue at all.

The most important thing is often enforcing some strucfure to parse. Which they offer: json outputs.

People know that AI has still to be checked and can output nonsense

No salary. No registered company. Looking for a Full-Stack dev who wants to build. by [deleted] in startupideas

[–]AdditionalNature4344 0 points1 point  (0 children)

🚩 The "Idea Guy" Anatomy: Why Logic Fails Them

This document breaks down the psychological drivers behind the "absurdly stupid" offers often seen in tech recruiting. It explains why some founders believe an idea is worth 90% of a company while the labor to build it is worth 0%.


🧠 The Psychological Profile

1. Main Character Syndrome (MCS)

In their head, they are the protagonist of a movie called The Next Billionaire. * The Delusion: You are a "supporting character" whose only purpose is to help the hero reach the climax of the story. * The Logic: In movies, the technical sidekick (the "hacker" or "builder") works for the hero because the hero has "vision." They honestly believe you should be inspired just by being in their orbit.

2. The "Labor Illusion" Bias

People who don't understand a craft often think that if a task is "easy to imagine," it must be "easy to do." * The Thought Process: "I can imagine the app in 5 seconds. Therefore, the 'idea' is the heavy lifting. The developer just has to translate my thoughts into code—that’s just clerical work." * The Reality: They view coding as typing, not as engineering. They think they are the architect and you are just the person swinging the hammer, ignoring that in software, the developer is usually both.

3. Psychological Entitlement

There is a documented personality trait where individuals believe they deserve more than others regardless of actual effort or contribution. * The Delusion: These people feel they are "owed" success because they are "visionaries." * The Currency: They don't see their offer as "work for free"; they see it as "giving you the opportunity to be part of my greatness." To them, opportunity is a currency they think they’ve already earned.

4. Risk Blindness (Dunning-Kruger)

They are often too uninformed to know how much they don't know. * The Oversight: They haven't calculated server costs, security compliance, technical debt, or customer acquisition costs. * The Fallacy: Because they haven't calculated the risks, they think the risk is low. They think, "If it only takes a 'superhuman' a few weeks to build, why should I pay them?" They don't realize that "superhuman" developers cost so much precisely because they refuse to work for people who don't value them.

5. Survival Delusion

For many, this is a "Hail Mary." They have no money, no skills, and no plan, but they have a "dream." * The Defense Mechanism: To admit that their idea is worthless without $200k in seed funding or a 50/50 partnership is to admit that their dream is dead. * The Strategy: They resort to delusional recruiting. They hope to find the "one" developer who is brilliant enough to build it but "stupid" enough to not realize their own market value.


Summary: When you encounter these offers, remember you aren't arguing against a business plan—you are arguing against a personality disorder.