This is just a bad take. If any understanding systems is the best skill to have now . All the LLMs can write the code some better than others. But understanding systems is what lets you know what to ask the model to do. It differentiates great software from slop.
the engineers who think there’s any value left in “being technical” are coping
zero value left after fable
no, not even “understanding the systems” or “architecture”
@EOEboh It depends on the task. Highly critical tasks I do read through. Otherwise it’s not really necessary unless I have a lot of time. If you setup your agents properly it’s not really an issue but I should mention then I do a bunch of reviews before merging to main.
@foderking That isn’t an excuse not to write your own auth. You should tell people to learn how to write auth following all the best practices. Vulnerabilities will always exist even is auth in auth as a service platforms.learning how to identify and address them it’s a part of engineering
Rolling your own auth doesn’t mean you write everything from scratch. There are auth libraries you can build your auth own. But saying rolling your own auth is a bad idea is something I can’t get behind
@akinkunmi Now the action notification service can then determine how to handle multiple notifications like sending one with the message described above
@akinkunmi If the the message: are less than 100 . Imagine 78 notifications but more aren’t coming in. Your system can send the notifications after some time (configurable ideally) even if the batch size is not up