How Tasty is Your Software?

Not delicious enough, that’s the answer! But, thankfully, you have already stumbled upon the solution!

Here at 1736, it’s been a yearly problem. We’re big on imagery and spirit awards. It’s kind of our jam.

Sometimes, we find ourselves thinking, How can we extend our food theme to every part of the team?. Can we theme our software???

Sure, we’ve tried some light puns here and there.. But we never quite figured out how to go deeper.

Until now.

We have written a robot software suite which allows your robot logic to be implemented in Chef.

Chef is a highly expressive technically Turning-complete programming language designed to allow your programs to be formatted like recipes for delicious foodstuffs.

Chef is an organic choice for programming: Everyone loves food, no one can live without it. Modeling your syntax after food ties it to some of the most base motivations we have as living creatures.

Chef is an efficient use of your time: You can indulge two hobbies (coding and cooking) simultaneously.

Chef reduces hard disk clutter: With a bit of care, you can encode your grandma’s prize-winning recipe for chocolate chip cookies and that Machine Learning LQR State-Space Extended-PIDF Ramalamadingdong Decaf Turbo-Encabulator implementation in the same file!

Chef is relevant: Many great teams have words like “cheesy”, “barbecue”, and “corn” in their name. All great teams have eaten food at some point. You can now use your software to funnel your team toward greatness, which clearly flows from food.

But, ummmm, How?

ChefBot is a framework to interpret and run chef recipes at robot runtime, along with extra tasty tidbits for robot-specific IO operations.

You must write your software in .chef files. Put them into the src\main\deploy\tonightsMenu folder.

If one chef has some internal issue and freezes or crashes, the others will probably keep working around the non-functional chef. Chefs don’t quit, and yours certainly won’t if they can help it!

Chefs are very fast. They crank out one completed dish every 20ms.

Be careful you don’t have too many cooks in the kitchen, or you’ll slow down your kitchen’s performance.

Special thanks to Joost Rijneveld for his java-based Chef interpreter that was the base of this project.

So dig in, whip up some yummy sauce code, and satisfy your cravings for syntactic sugar!

“Frequently” Asked Questions

Q: Did you know Chef is also the name of an actual automation platform that some real and legitimate companies use?

Yes, but that’s not important right now.

Q: Why did you do this?

Because Chris got bored.

And, turns out, this was not nearly as educational of an experience as he had hoped.

Q: Is this serious?

Only as serious as you want it to be.

Offer: If you put this on your robot on the field and use it, and show us it, we’ll give you a high-five. If it’s in the next couple months, we’ll both wear gloves and stand 6 feet apart.

Just don’t complain about bugs in your code. You’re responsible for extracting your own flies doing the backstroke in your soup.


Love this.


If you write your code to mirror a recipe that’s available publicly online, does that count as releasing your code for R15?


If you want to talk about imagery in programming, then I would assume you’d want to implement your code in something like Piet. That would definitely be worth style points to me.

Disclaimer: style points issued by me are highly unlikely to be redeemable for actual game points or awards.

1 Like


You could, but that would just be silly :stuck_out_tongue:.

1 Like

I have a variety of cooking videos on my YouTube channel. Please import them into your robot and film what it does. For posterity.


Robots shoudn’t stop, but yours did.


This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.