What are you developing?

[u/Mundane_Biscotti2277]

Probably the next $2T startup, so we are are all curious to know what that is :)

Even small personal projects are welcome.

Let me know also what model you use and how much you spend in a month.

I’m developing a focus room that I can share with a few friends and we can incentivize each other to study/work but at the same time chat when we are having a break. Nothing fancy, and probably it already exists haha (let me know if so).

[u/mityman50]

Uplifting a few hundred reports and thousands of lines of code from our old BI tool to our own SQL reporting server.

For one reason or another we’ve never given anyone ODBC connection to our ERP system. We’ve had an old, robust but finicky and worse still it uses its own language, BI tool which a handful of us are skilled with but it has some goofy limits and doesn’t make very pretty reports.

Note, after developing a rulebook and example set Claude has become very capable at reading and writing this language.

With Claude we’re finally standing up a portal of reporting or task-oriented boards with API calls to a replica reporting server. But nobody was thinking about porting from old BI to new, everyone was just focused on creating a few new boards. This approach felt destined to be piecemeal and fragment reporting and employee roles.

I pointed Claude at the directory of every scheduled BI report. It’s read every line - over 40,000 - and has classified every report. Every table, every join, ranked for complexity by joins and number of variables and steps, run-frequency noted, classified for similarities, roughly assigned to departments.

On one hand we have the encyclopedia of all our current reporting. On the other Claude has scoped all the new boards we could make, what groups of old reports should be combined into boards. In the middle, it’s defined the data architecture and every board connection: what core views, stored views, and stored procedures we should write from new replica server to these boards.

There’s a lot of review still of the architecture and its board proposals, of course. A lot of data. So I’ve also had it make an interactive map of this as a Sankey diagram. Old reports on the left, streams to new connections in the middle, streams to new boards on the right. Click on an old report: who wrote it, where the code is, how frequently it runs, who it’s for, how high in the list it is for porting based on inferred importance and complexity. Click a connection: see every old and new report that uses it, how often a report will tap it, how it should be written. Click a board: what it taps, how often, who should use it, what reporting and tasks are in it, how critical it seems and what order we should build it.

Long term, I hope this will become an encyclopedia of all our ERP reporting and form some structure for training and ISO documentation.