glassprongs

Been there a few times, plan to keep visiting. Hopefully those scripts you wrote and threw away were designed and written at the highest level of professional competency.

IIRC the solution steps should be Step 1: make it work, Step 2: refactor, Step 3: optimize. I think you did Step 1: unoptimize, Step 2: undo

When I worked in enterprise we didn't release software until we ensured quality.

The dev was responsible to test their software before they push their commit - QA's job was not to find bugs from lazy developers.

Our time estimations for tickets included additional time for writing tests.

All PR had to be reviewed for bugs, security, performance etc.. the author ws responsible for getting someone to review it if they wanted it released.

The dev was required to communicate to with QA and explain if any other systems or functionalities were be affected by a change.

Everything was be tested on staging before going to prod - absolutely everything with no exceptions.

Regression tests were never skipped.

If something couldn't be tested then we had to logically deduce why it could not cause an error.

After a release we ran smoke tests and would immediately roll back if any issues.

Protect from jobs being sent overseas.

I experienced Adobe's toxic business practices years ago when I tried to reduce our DC license count by 1. It made me no longer want to work with them.

Nice work

The lack of hotkeys, weak window management and finder are also failings for me. The mouse curve/acceleration used to terrible, either I got used to it or they fixed it at some point.

Our lawyer said we can for functional cookies so we now require those. For statistics and marketing we still ask for consent.

It is 100% legit. Typing this from Win xp.

These are some properties I see bad code having

  * insecure
  * doesn't work
  * lack of checks and validation leading to unhandled states
  * inconsistent style and method
  * difficult to understand for wrong reasons
  * spaghetti with too much coupling
  * poorly optimized and inefficient

  - Size: 27" to 34"
  - Resolution: 4k, 3440x1400 or two x 2560x1440 monitors.
  - Refresh-rate: 100hz+, absolutely not lower than 60hz
  - Latency: as a small as possible, no greater than 5ms
  - Ultrawide or not: my take is extra pixels + screen size is immersive but you get that also just by going up in res + monitor size.

  I don't have 5k+ or 120hz+ monitors so I can't chime in on those.

  If your programming has you managing a lot of apps and windows at once then I recommend 2 monitors.

If I plan to use the knowledge then I either apply it immediately or take notes so I can apply it when ready.

If I don't plan to use the knowledge then I take away an over simplification of the topic and any thought provoking key points.

That is some nice batch scripting kung-fu.

When I started coding it was copying other people's code and running it. I didn't deal with anything else such as libraries, modules, frameworks, complex environments or advanced features.

I recommend starting with Hello World. From there add code and methods to that working tutorial and see how far you can go. When comfortable, start making your own app from scratch. Reading + copy/pasting people's code will be a large part of learning a new language.

For tutorials that add complex features, be aware that they have more advanced error situations which require more experience to get out of.

Very cool. How many of us did it take to DDOS the server? It doesn't load for me either :)