JacKTrocinskI

I'm really glad to hear you made it through such a challenging time in your life. Your strength and determination are incredibly inspiring. I'm curious to know more about your healing process. Did you work on identifying and addressing the root causes of your pain, perhaps through therapy or counseling? Sometimes, personal issues can stem from our familial relationships. Did you find that to be the case in your journey? I'm interested to learn more about how you managed to overcome your struggles and achieve the peace you have today.

CTEs are just a nicer, more readable way of writing a subquery. Also, CTEs can be recursive. In Postgres, CTEs can be useful when used with the RETURNING clause. If you're using the same CTE in multiple different queries, then consider creating a view instead. I wouldn’t use a CTE for lookup values, create a lookup table instead.

K.I.S.S. - Keep It Simple Stupid

It sounds like there might be a larger project management issue within your team, though it’s hard to tell from a single example. Features should solve business problems and should come from your clients and/or users and not from engineers. Are your users complaining about your static solution? If not, then why change it? Engineers should work on things that will add value to the business. Arbitrary performance improvements and code rewrites that don’t solve any business issues should be rejected by your project manager.

My suggestion would be to bring this to the attention of your PM. If that fails, then focus on picking up tasks of high value and visibility. Let the “smart” engineers do code rewrites or performance improvements. You’ll have a lot more to show on your resume, feel a greater sense of accomplishment in your work, and will have a greater chance of getting noticed as a star on your team.

That's not really a great counter argument, can you explain why you think time estimates are worthless? Do you prefer story points instead? How do you schedule a project with your clients?

Are you in a low cost or high cost location?

I would expect job cuts in high cost locations to come first.

They added the MERGE statement!

...and better defaults for the public schema.

Really looking forward to Postgres 15.

The same way Wallstreet does.

Every investment has risks, stocks are not that different from crypto in that regard.

Regulation, once it comes, will help better protect retail investors.

Crypto is still in the early stages, the technology is revolutionary though and I think it's here to stay.