4nof

I'm trying to get a database together for a general database for an app I'm writing. - I'm going for low-cost prioritized over easy setup. - I looked into making a sqlite db for each user stored in s3, but that is generally only readonly unless I want to pickup and drop on s3 every read/write, then there's write collisions, in which I would need a queue for transaction to place on the db in sequence. Doable, but more complex than I was hoping. - I could vertically scale a PostgresDB with 200GB , place on a t2.medium instance, and just be done with it there, but sooner or later I will need to scale again, It would be nice to have it as an easy scale. - I've considered CockroachDB and Yugabyte. Yugabyte Terraform has issues I can't solve - something about an ami resource not found, and support has issues open and unhandled from March 2023 on Github, so I'm leaning toward CockroachDB , but licensing is sorta confusing - I want to use this for a customer facing app: https://www.cockroachlabs.com/docs/stable/licensing-faqs I think that CCL should cover it? I guess I can ask on their support.

I saw FoundationsDB , but I haven't really looked at it, how good is it? https://tech.marksblogg.com/minimalist-guide-tutorial-foundationdb.html

Are there any other distributed DB solutions I can look at that can run on EC2 on AWS? Any suggestions or comments would be appreciated. Thanks.

I have 8 years of software developer experience. I took the founders course and was going to do a submission of some past work for YC2022 just to see what would happen. However I stopped short of that because it doesn't seem to be my best work, it doesn't have a large user problem, and it is just a "broken toy" thing.

I would like to figure out what I can do to find a problem first, but I'm not sure of where to look. The cool idea I have for music publishing related startup just has a book reference, no users involved yet :\. tl;dr : What can I do so I will be ready for YC 2023 Fall and submit something decent?

I was having trouble making a non-chromatic scale with the current midi due to all the halfstep calculations. Why should the programmer have to worry about those things? Instead of 24,26,28,29,31,33,35,36 for a c scale, I made it so you can do 1 2 3 4 5 6 7 8 and set the scale, major, minor, offset, in the numbers - I find that easier to program.

Current implementation https://github.com/fornof/atomicnotejs or you can try the alpha-version here- https://geometricfigure.com/atomic/

something didn't map so while the notes shown in the stave slightly off, it plays midi just fine. You will need a midi player to get audio output currently(see github link). It also has an export to midi, I just don't have it mapped to a button yet.

(in console of chrome, to get midi file output, atomic.readMidi("1 3 4 5 6 7 8 9 10")) My goal is to eventually get all the functions here mapped and created:

https://docs.google.com/spreadsheets/d/1DPHKU4RduqJA1jyqMAquuReiLneYmFJJniogQwFT27U/edit#gid=0

For the rules:

1:4 4 3:8 2 1 , plays the first 2 as quarter notes (c and f ) and the last ones as 8th notes.

1.1:4 plays a quarter rest - at least it is mapped to play it 1.3 is a c# , -1.2 is a b flat.

1 is c (for now) it is space delimited.

I'm looking to collaborate on this. It is written in NodeJs, vanilla js (though probably converting to angular sometime soon), message me on github if you are interested.

https://github.com/fornof/rosetty

My goal was to create a dual language viewer as a tool to use at a meetup - basically a lesson plan that people can take home and study if they like. I used the Rosetta Stone as a basis for this simple template. I only have python and javascript side by side, but the section.yaml can easily be added on to add more languages and more sections to each languages. https://github.com/fornof/rosetty/blob/master/sections.yaml

I made this with a Yaml file that has all the paragraphs in it, I used a python script to syntax highlight and url replace google(subject) with google search links. Node.js is used as the basic file server. Tornado could have also been used. Vanilla javascript is used alongside js-yaml.

Further work I would like to accomplish would be to : 1. get sections for classes, inheritance, and string manipulation. 2. Put in Go and Java so someone could compare Java with Python, Python with Go, and Go with Java. each side by side. 3. Make more pages with the yaml as a template. 4. Do meetups!

I have a music notation I am making called HexNoteG9, where 0-9 are modifiers and a-f are notes, 9 is the note g.

This is Twinkle Twinkle Little Star: 24 | this sets default note to a 2^2 quarter note

24 c c g g a a 1g f f e e d d 1c g g f f e e 1d g g f f e e 1d c c g g a a 1g f f e e d d 1c

now , just replace all g's with 9's and you have hex. The 1's are 1/2^1 = 1/2 notes

I have an example of minuet played in HexNoteG9 as well as more details on the modifiers, how to do rests, octaves, sharps, flats, dotted half notes, dynamics, looping, and comments: https://drive.google.com/file/d/1atnHKK4mbMjGrJFFhCk76e9YaTAkiv5y/view?usp=sharing

I want to make a specification that is peer reviewed similar to how the JSON specification looks https://tools.ietf.org/html/rfc7159

My end goal is to standardize a specification so that other people can adopt and use it. It would be nice to build tools off of this with other people.