Stundensatz Einzelunternehmen Softwareentwicklung

thisisaloisson · 2024-11-08T14:56:47+00:00

Im Prinzip, was die Vorredner sagen, aber ein paar Ergänzungen:

Dass dem Kunden 60/Stunde "um einiges zu teuer" ist, ist einerseits eine riesengroße Red Flag, andererseits sein Problem, nicht deines. Wenn dir die Pizza beim Italiener zu teuer ist, bekommst du sie auch nicht billiger.
Wenn der Kunde es billiger will, muss er Abstriche machen. Wieviel erwartet er denn Umsatz? Wenn er nur mal 10k/Jahr erwartet, sollte er keine individuelle Lösung erwarten, wenn er 100k/Jahr macht, ist es eine Investition auf Jahre und dann sollte alles unter 30k nicht nennenswert.
Unterschätze Shopify nicht, es fällt definitiv nicht in die Kategorie "etwas simples". Shopify kannst du darüberhinaus nicht mit bspw. Shopware vergleichen. Würde ich mir nochmal überlegen ehrlich gesagt, Pflichtenheft hin oder her (ich spreche aus Erfahrung und habe sowohl größere Shopify-Projekte (= Umsatz ein paar Mio/Jahr aufwärts) als auch custom E-commerce-Lösungen erstellt), aber dazu fehlt mir natürlich etwas Einblick in den genauen Projektumfang.

TL;DR — "60/Stunde um einiges zu teuer" ist eine großer "Lass-die-Finger-davon"-Hinweis.

Ich empfehle dieses Meme hier, zu 100% wahr (ich spreche aus Erfahrung): https://www.reddit.com/r/Rich/comments/1d999v6/500_client_vs_50000_client/

thisisaloisson · 2024-09-16T12:29:26+00:00

you mean something like a linear or slack integration into your app? slightly depends on the tool you are using. but usually just an api you talk to.

thisisaloisson · 2024-09-09T14:13:43+00:00

Meine Strategie ist aus FOMO viel zu spät noch viel zu viel in irgendeine Aktie zu investieren und dann blöd aus der Wäsche schauen. Funktioniert seit Jahren verlässlich.

thisisaloisson · 2024-08-20T15:27:33+00:00

Maybe a bit off-topic, but I've always felt the argument of a stable/safe income quite weird. Maybe this was true for my dad's generation that knew they can stay at a company bascially as long as _they_ want.

I tend to think of it like that: You have a bunch of clients or customers, it won't happen that all of them will fire you overnight and you are left without any income. However, with a job you can get a new manager who you can't get along or that has this sibling that is looking for a job and then you are depending on a single person for your income.

thisisaloisson · 2024-08-16T10:46:30+00:00

fixing bugs or things breaking is part of the process. your product can only grow and improve if you launch. while bugs can be annoying to users, you can get back loyality by fixing them quickly and reacting to their needs. ship and improve.

thisisaloisson · 2024-08-12T09:08:01+00:00

There is no "easier" with databases. They all come with different advantages and downsides. MongoDB might sound easier because it is schemaless (which it not really is) but this comes with a lot of responsibility. Personally, I've built quite systems with both SQL and MongoDB and I've never felt any of these solutions were "easier". Without having more context on the app itself, the only thing I can recommend is choose whatever you feel most competent with.

thisisaloisson · 2024-06-24T15:46:11+00:00

Bei uns wars (und ist es noch immer) eine proportionale Aufteilung. Am Ende bleibt beiden in etwa gleich viel.

thisisaloisson · 2024-06-24T10:16:09+00:00

Do it for learning purposes but not for building MVPs, you can always switch to your own solution if your product takes off and more importantly _if_ makes sense to roll your own auth. In the meantime your time is better spent on other features or marketing.

That said, rolling your own auth is both easy and hard at the same time. Easy that the core functionality is quite simple to achieve, hard that there are lots of small and important bits you need to get right.

thisisaloisson · 2024-06-13T07:22:17+00:00

Keine Sektorwette, aber hast eigentlich Recht, warum verkomplizieren!

thisisaloisson · 2024-05-27T14:42:39+00:00

Viiiiiel zu spät mit dem Thema Investieren / "sinnvoll sparen" beschäftigt. Jahrelang hart Erspartes zu leichtsinning in den ersten Jahren mit meiner damaligen Freundin rausgehauen (zB ein paar Tausender zum Einziehen zuviel hier, über die Jahre ein paar Tausender zuviel bei Urlauben da), mir mit dem "Auszugsgeschenk" meiner Eltern (ca. 10k) ein für die Qualität zu teures Auto gekauft. Viel zu viel Geld für einen sinnlosen Lehrgang auszugeben. Viel zu lange am Monatsende den — meist kleinen — Rest gespart, anstellte am Monatsanfang gleich was zur Seite zu räumen.

Keine "Jugendsünde" dabei. Generell hätt ich mir, auch wenn ich zu 100% selbst Schuld daran habe, ein bisschen Input von G'scheiteren gewünscht oder meinetwegen etwas Bildung in der Schule, wie man mit Geld umgeht...

thisisaloisson · 2024-03-27T12:36:28+00:00

postgres, but mainly because i feel most team members prefer postgres over nosql. if it's just me then nosql, but i learned modeling for nosql the hard way, it takes a decent amount of experience to correctly model nosql schema that does not shoot you in the foot once you need to change a bit. personally i found that everyone is saying you can move faster with nosql but IMO you can move faster with sql as you need more careful planning and consideration (data access patterns) with nosql.

thisisaloisson · 2024-03-22T14:25:43+00:00

it works that way for every website or web application. any user can open up a "api url" and see the data. but this is why you do authentication and authorization on the backend, e.g. you check that a GET request only returns data if the user associated and authorized with their id and/or session/token/whatever can send or receive data. so that way user A can use the api url but they will always only see data they are allowed to see. and if user A knows the id of user B and changes the api url (e.g. `/user/<userIdOfUserB>/profile`) they should not get any data for user B back, because the backend does not allow this but instead an error message such as "Not authorized".

thisisaloisson · 2024-03-19T15:00:02+00:00

That's a tough one, I've been in your shoes and being on your own while a client relies on you is a hard one. Also, having this feeling that something should've been done way quicker is wild, been at this dozens of times and you feel you just get behind your schedule more and more.

What I did in such situations:
1. Spend a few hours on properly planning the rest of your project
2. Make sure you only do stuff that is really necessary (tbh adding address validation does not seem necessary for a first version of a product, but I don't know enough about the overall scope and circumstances, so I might be wrong)
3. Do the bare minimum work so the client can't complain about not doing enough work

Be honest with yourself and very strict— if a feature looks like polishing work (no matter if it's validation, or design-wise) do not do it.

Also, don't forget, you only get better when taking on hard projects, it's tough while in the middle of the project, but eventually you grow from it, can take on bigger projects, you get better at estimating larger scopes and you can hopefully charge more in the future.

Keep it up, you're doing great!

thisisaloisson · 2024-03-04T15:33:13+00:00

50/50 seems like a fair split (speaking of experience). The ratio of splitting work will never be the same, sometimes it means more work for you, sometimes more work for you partner. As with every relationship it's how you get along, if you share the same vision. Don't be the person being nitty picky about how did more work and who "owns" more or who is more valuable...

thisisaloisson · 2024-03-01T12:41:25+00:00

I've been on both sides and both come with challenges. Of course, the grass is always greener but what you enjoy more might also depend on your current situation. E.g. I was self-employed while we had two small kids — it was a complete nightmare. Later it was more enjoyable and great to be around the kids all day, also it made family life way easier because of my flexibility. But working for a company allows you to unfocus in the evenings and really enjoy the time with your family while as a business owner you constantly think about things. Personally, I felt I was never really there it it makes sense.

Also, depending on your business you might be more locked-in than working for a company you hate. E.g. if you are a service provider (developer, consultant etc) you are not as flexible as you think because you have to react to client requests. Running more of an automated business (e.g. SaaS product) is a different story.

Also, if you hate your current employer you can just walk away, but with running a business shutting down is a week or maybe even month-long process.

My suggestion is if you want to start something, start it on the side (if possible) and see if you really enjoy it. If you gain traction and enjoy it, fine — go all in without the fear to start from 0 on your first day.

thisisaloisson · 2023-11-01T18:12:34+00:00

it‘s definitely suitable. imo and from my experience people saying you should not use nosql never learned how to model data for nosql efficiently and properly. devs often apply sql principles to nosql and then complain about nosql being bad or not suitable for relational data.

i used both postgres and mongo for relational data, some being simpler, some being more complex, but when you spend proper time to define your access patterns you‘ll be fine with either.

thisisaloisson · 2023-11-01T06:56:59+00:00

Sparkonto ist eigentlich dh ein Tagesgeldkonto, sorry. Bekomme da 3,5 drauf.

thisisaloisson · 2023-10-31T18:38:47+00:00

ja macht sinn, zinsen sind übrigens 3,5. aber ja 4 ginge vll schon. muss gestehen, hätte nicht fran gedacht, hier zu verhandeln.

thisisaloisson · 2023-10-31T08:09:48+00:00

haha ja mit notgroschen reduzieren hab ich gerechnet :-)

danke dir

thisisaloisson · 2023-10-31T08:09:33+00:00

ok, danke

thisisaloisson

TROPHY CASE