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.

They are refering to a meme a Dutch guy created

Link?

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.

It’s like people have never read any books about software project management. While coding skills matters, most failures isn’t due to lack of language knowledge or coding speed.

Exactly. I've repeated this a lot this month: Coding is the easy part.

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

Which IIRC is named for that geometry thingie GP mentioned, that this method uses to represent the problem, with the solutions being vertices/edges of the thingie.

Interesting, TIL herpes is top of mind for me, but not for most of HN.

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?

For deadlines i use a week based paper calendar and setback can be handled by negative time entries, like:

  01.15-00.00 refund for issue 6789 (75mins)

It's not ideal but it barely happens.

Another minor issue is that my parser currently does not support overnight shifts like

  2022-11-15
  - 23.45-01.18 another task

These have to be divided into 2 separate ones:

  2022-11-15
  - 23.45-23.59 another task
  
  2022-11-16
  - 00.00-01.18 another task

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.

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