Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Boris Cherny: TI-83 Plus Basic Programming Tutorial (2004)

ticalc.org

Post reply on HN
Print view View original

41–50 of 93 posts

Re: Boris Cherny: TI-83 Plus Basic Programming Tutorial (2004)

#42

Post by t0mek »

I like the "challenges" part at the end, especially the varying difficulty levels:

* A quadratic formula program, which outputs the number of roots and the x-intercepts upon the user inputting the values of A, B, and C.

* A fighting game, with health, a store, different enemies, weapons, armor, etc, with graphics and animation.

Re: Boris Cherny: TI-83 Plus Basic Programming Tutorial (2004)

#45

Post by brookst »

jvillasante wrote: post #30

For those souls loosing their skills to the easiest to adopt technology ever created... agentic development works for him because he KNOWS what he is doing in the first place!

Pretty much every tool is far more powerful for those who understand the job it does.

Re: Boris Cherny: TI-83 Plus Basic Programming Tutorial (2004)

#46

Post by vikingerik »

z_open wrote: post #3

It's funny how many software developers got into it due to being bored in class with a TI-83 and randomly trying to create programs.

Hey, some of us are old enough to have done it on a TI-82 instead!

I already knew Basic from a DOS PC, but did write a Breakout clone while bored in classes on my TI-82.

Re: Boris Cherny: TI-83 Plus Basic Programming Tutorial (2004)

#49

Post by cube00 »

matt_kantor wrote: post #23
z_open wrote: post #3

It's funny how many software developers got into it due to being bored in class with a TI-83 and randomly trying to create programs.

That was me. Algebra clicked for me so I found the pace of the class to be slow. Ended up creating a few programs to solve tedious things like the quadratic formula incrementally while displaying the intermediate steps so I could write them down on tests. Authoring programs using the buttons on the calculator was not fun.

> so I could write them down on tests.

We had show our calculator had been memory wiped before any tests.

Although in retrospect we only had to show the wipe screen which we probably could have coded up as its own program.

Post reply on HN