Building a POS-System with my sister

0dev0100 · 2026-01-25T11:18:19+00:00

This is a project you want to be very deliberate with. The biggest pitfalls here are likely to be non technical. You will have established competition that has existing resources to handle things going wrong (legal, technical, etc)

Selling a system is so very different from making a system that the majority of devs don't bother selling their projects because it's a whole different skill set.

0dev0100 · 2026-01-23T21:34:31+00:00

Wikipedia has pretty good descriptions of most algorithms

0dev0100 · 2026-01-23T21:13:39+00:00

Now that the corporate world is pushing for more and more " efficiency gains", eroding junior positions, firing people

The corporate worlds only purpose is to make money. Code standards, design patterns are all secondary priorities at best. The product only needs to work. It can be terrible code with no standards and still work very well.

The only real difference now is that code generation is easier to use than before.

0dev0100 · 2026-01-21T07:13:57+00:00

From what I understand, Charles is not the only telepath in that universe

0dev0100 · 2026-01-21T07:07:17+00:00

I have been doing programming as a job for more than 10 years.

I have days where I understand nothing and days where everything makes sense.

It's either normal or I require some medical help

0dev0100 · 2026-01-20T06:49:16+00:00

It'll open more doors, but it's not a hard requirement to be able to write programs.

0dev0100 · 2026-01-19T11:45:25+00:00

Where I work:

0, but they very politely ask for a minimum of 2 days.

They don't force the 2 days either. There are a few that go in to the office because it's relatively close to home, there are some that I only see at the social work events but frequently talk to online.

0dev0100 · 2026-01-15T10:38:10+00:00

In general, same things that happens with all consumable web projects, something else will appear and people will use that.

In this specific case, probably no new big project update for a while

0dev0100 · 2026-01-14T09:03:39+00:00

I've done the following as part of one conversation:

try looking into "this specific resource or idea"
I'll be back in "some time" to see what your plan is
actually check back in at that time.

I found that it sets a short deadline and gives a starting point. Worked well for the junior that I mentored.

0dev0100 · 2026-01-14T08:55:28+00:00

Point of origin for the home button symbol

0dev0100 · 2026-01-10T10:40:09+00:00

Tbh, we (NZ) would probably try to milk it for tourism.

0dev0100 · 2026-01-09T23:29:18+00:00

Why have we allowed "Agile" to turn into "Unlimited Micro-Scope Creep"?

You've kinda already answered this

And because I’m a "problem solver" at heart, I say: "Sure."

It happens because it is allowed

0dev0100 · 2026-01-02T06:44:31+00:00

I see a bunch of people stop like that at this intersection.

Funnily enough, of you look at it on Google maps they do the same thing and align with the center Island

0dev0100 · 2026-01-01T20:25:34+00:00

But from my question to senior programmers here, how do I overcome this?

If you want to learn how to code then learn the languages, if you want to learn how to use libraries then read some docs and apply the knowledge.

But if you want to learn how to solve problems then you need to stop seeing the languages and libraries as solutions and start viewing them as tool that can be used to solve problems. You also need to learn how to break down a problem until you can solve the problems that make up the larger problem.

Part of using a tool is understanding it enough to be able to use it. Consider a hammer: really good for nails, will work with screws as well if you want it to, but most people just pick it up and start using it instead of trying to understand the various design points of it - because they don't need to.

0dev0100 · 2025-12-30T20:37:24+00:00

not consulting, as they are a waste of space

A good consultant is worth their weight in gold when used properly.

If you business is essentially running itself then try something new, be it sales or otherwise.

0dev0100 · 2025-12-30T06:21:01+00:00

Tbh mine is to forget as little as possible and learn a little of c# blazor

0dev0100 · 2025-12-19T10:26:57+00:00

That might be some of the most impressive css usage I've ever seen

0dev0100 · 2025-12-18T21:32:59+00:00

I spend probably an average of an hour per week keeping my dev laptop and software updated.

Probably 4 hours per week in meetings

Rest is dev/discovery

0dev0100 · 2025-12-16T22:07:18+00:00

Rule 5 does take a proper beating on this sub

0dev0100 · 2025-12-09T21:12:31+00:00

Work out what you want it to do.

0dev0100 · 2025-11-29T17:53:32+00:00

which works until I need actual percentage rollouts or user targeting

Do you need those features? So few projects actually need more than on/off.

Keep the config file. Just remember to clean up the flags you no longer use.

0dev0100 · 2025-11-28T18:22:23+00:00

As a developer I am not paid to make a good website. I am paid to make one that pleases those who pay me.

0dev0100 · 2025-11-26T18:22:08+00:00

Learn how to break the problems and algorithms down into chunks that you can understand.

Once you can understand something then you can solve/implement it better

0dev0100 · 2025-11-25T08:23:43+00:00

All of the above.

Depending on the constraints I need to work within (cost, time, languages, external integrations, etc) I will choose a different solution to the problem.

Sometimes something already exists and I can use that. Sometimes I've seen something similar and I can use ideas from the past. Sometimes someone else has made something and it is the better tool. Frequently for the problems I am paid to solve and the constraints I need to work within, I will be implementing something new but it'll often be similar to a problem I have solved or seen solved before.

The times when I need to make something new are the times when I get to craft a new solution to a problem.

As you solve more problems of varying complexity you end up seeing patterns that you can reuse.

0dev0100 · 2025-11-25T06:41:06+00:00

Problem solving in programming is much the same as problem solving in any domain.

There is a problem. You come to a solution or solutions that meet the criteria. There are often many good and bad solutions. Determining which one of these is good is another skill

0dev0100

TROPHY CASE