6

It wasn't really the project itself, but more the execution of it

Last semester we were tasked with writing a new programming language from scratch. We were a team of six people, everything went great to begin with. We discussed language features, the framework runtime it should run on and even what language to write it in.

Fast forward two weeks, nobody is doing anything but me, the two dudes tasked with helping me were both no-shows and the others were busy documenting the syntax and semantics of the language.

I basically ended up having to write the whole language myself with no breaks no help and no guidance.

A few weeks before deadline I completely burned out and couldn't do anything other than just sit and stare at the code; mentally exhausted and not in a mood to do anything other than doing mindless unrelated tasks. But alas work had to get done.

And it did get done... Sorta.
Our beautiful statically typed, statically scoped concurrent programming language that was supposed to compile to BEAM code was neither statically typed, statically scoped, and the output ended up being half-working elixir code that only worked on the most specific of cases.

I don't want to work with those guys again.

Comments
  • 0
    getting a partially working language is an achievement unto itself. But having 90% working project with few critical bugs would be ideal. Keeping working hard mate, its not what you get from others that is valuable it id ehat you can give yourself that can truly make a difference in your life. Stop depending on others.
  • 0
    @liveCoder I gave myself a fried mind...
  • 0
    @Fixxel one decided to re-take the semester, so he didn't get credit. The other failed the exam
Add Comment