api VS Sentry

The composer.json and project configuration is lightened as much as possible: unused packages and classes are removed, platform-check is disabled, and classmap-authoritative is enabled.

Running Sentry Wizard... version: 3.13.0 | sentry-cli version: 1.75.2 Sentry Wizard will help you to configure your project Thank you for using Sentry :) Skipping connection to Sentry due files already patched ┌ Sentry Next.js Wizard │ ◇ ────────────────────────────────────────────────────────────────────────────╮ │ │ │ The Sentry Next.js Wizard will help you set up Sentry for your application. │ │ Thank you for using Sentry :) │ │ │ │ Version: 3.13.0 │ │ │ ├───────────────────────────────────────────────────────────────────────────────╯ │ ◇ Are you using Sentry SaaS or self-hosted Sentry? │ Sentry SaaS (sentry.io) │ ◇ Do you already have a Sentry account? │ Yes │ ● If the browser window didn't open automatically, please open the following link to log into Sentry: │ │ https://sentry.io/account/settings/wizard/authtoken123/ │ ◇ Login complete. │ ◇ Select your Sentry project. │ myproject-126kk132c/javascript-nextjs-f9 │ ◇ Installed @sentry/nextjs with NPM. │ ◆ Created fresh sentry.server.config.ts. │ ◆ Created fresh sentry.client.config.ts. │ ◆ Created fresh sentry.edge.config.ts. │ ◆ Added Sentry configuration to next.config.js. (you probably want to clean this up a bit!) │ ◆ Created src\app\sentry-example-page\page.jsx. │ ◆ Created src\app\api\sentry-example-api\route.js. │ ◆ Created .sentryclirc with auth token for you to test uploading source maps locally. │ ◆ Added .sentryclirc to .gitignore. │ └ Everything is set up! You can validate your setup by starting your dev environment (`next dev`) and visiting "/sentry-example-page". If you encounter any issues, let us know here: https://github.com/getsentry/sentry-javascript/issues 🎉 Successfully set up Sentry for your project 🎉

I may use Flask-Admin initially to offload the "CRUD" operations to have an initial prototype fast but then drop it ASAP because I don't want to write a "flask-admin application" to fight against later on. If the application is mainly "CRUD", then Flask-Admin is suitable.

Now...

Would you do a breakdown/list of all the jobs you've done by sector/vertical and by function/role and by application functionality?

- [0]: https://flask.palletsprojects.com

- [1]: https://flask-admin.readthedocs.io/en/latest

- [2]: https://flask.palletsprojects.com/en/2.3.x/patterns/celery

- [3]: https://sentry.io

- [4]: https://posthog.com

- [5]: https://www.docker.com

Personally love the type system and its relationship with the dev. tools; feel naked without the dealing with the compiler's panic attacks by now. Several influential libraries and packages (babel, caches, sentry, to name a few from the many) seemingly bolted the superset into their backbone so far. Also read dev. logs from people and companies like AirBnB who claim that the TypeScript was a good influence for productivity and documentation to their codebases.

It's probable the core will always remain closed. That's both a business and practical decision. However, much like how Sentry have some of their services open-source, we may follow that route.

>As now we've introduced some peers code review, automatic testing on most critical stuff (but since the codebase sucks these aren't really reliable tests)

They may not be "reliable", but these are your safety net, or harness, so you don't fall. I wrote about similar issues, for instance here: https://news.ycombinator.com/item?id=26591067 and, given your promotion, here: https://news.ycombinator.com/item?id=37211796. It contains a few steps starting from "So...".

You can add monitoring, something like Sentry (https://sentry.io) will capture exceptions that were not handled that you have not seen because the stack trace is buried in hundreds of pages of logs or something. It groups them by exception and counts them. It's pretty awesome. (https://docs.sentry.io). It supports around 108 platforms (Java, Python, JavaScript, etc.). This lets you see the exceptions and makes prioritizing easier (which ones are the most frequent, which ones impact the most, etc.).

If you don't have them already, issue templates are really useful and the comment I linked to explains why, but here's an example of an issue template (again, you can configure them for different types of issues so team members select from a dropdown for a bug or a feature):

Sentry, another BUSL licensed project, seems fine? https://github.com/getsentry/sentry/graphs/contributors

Usually you would use a tool like Sentry or Rollbar to catch and report errors. Those tools improve developer experience, however we should also think about user experience — and there is a way to make it more pleasant. What if when your users experience an error, we display a typeform to collect additional feedback from the user?

Another good open source project you can learn from is Sentry (https://github.com/getsentry/sentry/tree/master/src/sentry).

...and then view these logs in a browser with a Web UI, such as Sentry.io or Splunk.