gashmol

Statecharts are too complex IMHO. I prefer to compose simple state machines to model a complex behavior instead of building one giant statechart.

It's guerilla marketing :)

Yes it is, but timing is key. Not too early and not too late.

Blaming the user again aren't we?

Patience.

You can do user testing and have developers watch.

Aside - It's funny to me how many developers still don't like to call their craft engineering and how fast LLM users jumped on the opportunity.

I'm pretty sure every engineering field calls it designing. Perhaps software devs feel a need to inflate what they actually do.

Aside - Why do we need the word "architecting" anyway? Why not just use designing?

In no particular order: Decide on the scope in advance. Beat procrastination. Beat perfectionism.

Ideas don't make money, businesses do.

That would be imperfect.

IMHO there are plenty of available and cheap .com domains but you have to be creative. From my experience ai tools aren't creative enough for coming up with unique and good sounding names.

https://en.wikipedia.org/wiki/Considered_harmful

They are refering to a meme a Dutch guy created

The layoffs and/or pay cuts are coming this year.

I don't see companies keeping large engineering head counts when they can get working software in minutes from specs.

So, I suggest you become better in writing software specs.

Writing specs is safe for the foreseeable future because:

1. There is still no ai architecture that is comparable to human brain other than rot memory.

2. There is no enough data to train a model from such architecture if and when it's invented.

I thought it's related to the simplex method in linear programming

So far I've managed to overcome the itch to write my own solution for this problem. It is tempting though.

How do you handle deadlines and setbacks?

Trello was the first tool I used. Drag & drop and the whole UI was fun but it's hard to see the big picture.

I'm working on a tool to automate 80% of my job as a software developer. It's too early to share but the basic idea is specification in, working code out.

IMHO the crutial word is not premature but rather optimaization. Not everything is an optimazation.

Merging two loops into one is an optimazion that should be postponed until it's necessary and the system have been profiled.

Joining two large lists by a hash join instead of a nested loop is a design decision that should be made at the outset.

From my experience unless you have some undelining conditions you can stand for most of the day. I got used to it in a few weeks time and got ridden of my lower back pain. Perhaps stand as a default and take sitting breaks as needed?

What's the source of the changing priorities? Perhaps you could delay your reaction to the source of the changes?

That's insightful. What would you say the most important documentation is?

Did you try a standing desk?

I figured if you don't have a job or are working in a bad environment everything else is negligble.

How often does it actually happen?

Where does it hurt more, in new dev or maintenance?

Managers.