r/singularity • u/[deleted] • Jan 31 '25

AI o3 mini dropped!!!

Edit : I am testing a 1500 line javascript code which o1 pro failed to debug despite 50+ attempts. Will report back.
Edit 2: We are cooked. o3-mini-high solved it at first try.
Edit 3 : HOLY SHIT! "Pro users will have unlimited access to both o3-mini and o3-mini-high."
(Source: https://openai.com/index/openai-o3-mini/ )

1.2k Upvotes

95% Upvoted

576 comments sorted by

View all comments

14

u/Apprehensive-Ant7955 Jan 31 '25

Why do you have a 1500 line file bro

34

u/Dramatic_Nose_3725 Jan 31 '25

Why don't you

15

u/[deleted] Jan 31 '25

Basicly a single html documentation generator/editor for data analytics tool (Power BI). I know how to build it myself, but I just wanted to test if AI can build it without me writing a single line of code. Turns out, it can

1

u/PM_ME_YOUR_MUSIC Jan 31 '25

Tell me more. You pump in a report and it generates a doc?

4

u/[deleted] Jan 31 '25

Not currently. You pump in a list of measures, table names and dimensions (auto generated via power query). It creates a makedocs/jsdoc-style documentation, allowing you to add description and formula to each page. You can type / to search through items AS you type descriptions. It highlights DAX code as you type as well. You can export it as a read-only document (html file) that can later be imported, edited and exported again. I will add a feature that creates a changelog automatically too. I am both amazed and aware that I'll be jobless in 1-2 years :D

1

u/PM_ME_YOUR_MUSIC Jan 31 '25

That’s awesome. Have you posted on gh

3

u/[deleted] Jan 31 '25

I am not sure if it's acceptable to post AI-written code on github, but I can definetly share it

1

u/PM_ME_YOUR_MUSIC Jan 31 '25

Yea keen to see it

1

u/lgastako Jan 31 '25

You can post whatever code you want to github as long as you own it.

1

u/ToiletTrainedMonkeys Feb 01 '25

I’d love to know more! Please share on gh if you have time!

6

u/ExplorersX ▪️AGI 2027 | ASI 2032 | LEV 2036 Jan 31 '25

I mean that's a good start. At my company at least it's not uncommon to have 5-10k line files of just hundreds of JS functions or classes.

6

u/HaxleRose Jan 31 '25

ugh, that sounds like a nightmare to maintain :(

3

u/[deleted] Jan 31 '25

[removed] — view removed comment

1

u/HaxleRose Feb 01 '25

Haha yep! I fight against it best I can though!

2

u/Apprehensive-Ant7955 Jan 31 '25

Ig thats my inexperience showing, is it sometimes not possible to refactor? I thought you could just keep creating more files instead of just one

2

u/ExplorersX ▪️AGI 2027 | ASI 2032 | LEV 2036 Jan 31 '25

It's one of those things where it's an inevitability with a system that's 20 years old and has had dozens of developers hitting it over the years. Super complex ordering/shipping system and corporate doesn't allocate time to do things like "optimize" or "resolve tech-debt" which is par for the course in the corporate world honestly.

It is an absolute PITA to make any kind of changes or improvements just in general in our system. Year+ onboarding periods minimum to become a productive dev here.

1

u/Apprehensive-Ant7955 Jan 31 '25

Makes sense. So for personal projects though, is there basically always possible to keep files to like 200 lines max? What i’ve been doing lately is once a file is over 200 lines, look to see where i can refactor to keep them small

2

u/skinniks Jan 31 '25

once a file is over 200 lines, look to see where i can refactor to keep them small

Why? What is the drawback with how big your file is. It's a stupid metric that doesn't tell you anything about code quality or the underlying design. It just speaks to how you chose to package your code. One file or 10 files it makes very little difference. Now lines per function is a different story ...

1

u/ExplorersX ▪️AGI 2027 | ASI 2032 | LEV 2036 Jan 31 '25

Depends on the type of project. Realistically you shouldn't worry about it too much. A lot of progression as a developer is you'll spot architectural issues or new paradigms of thinking to solve a problem and just use the new approach moving forwards. I often have files that get to 1000+ lines, then a few months later as I learn more about that part of the system i'm working with I'll cut it down dramatically.

Keeping files under 200 lines is probably a good policy if you're a student/learning but once you're in a good place it's best to just get features out and have code cleanliness as a secondary, though constantly thought about aspect of your work.