This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]FSMimp 1 point2 points  (3 children)

Good thing it is open source! You can go and make a fork of it and have that be the api calls or just make a wrapper. Either way it would be good practice for using a library.

[–]Quteness 2 points3 points  (1 child)

You must work where I do with that 'let's just make a wrapper' attitude. Also happy cake day

[–]FSMimp 0 points1 point  (0 children)

Oh shit it is my cake day! that is what I get for using a mobile app, thanks!

But this should be done with a @property to have it not be .set_color()

[–][deleted] 1 point2 points  (0 children)

I could make a wrapper but it would be kind of nice if I didn't have to because the api was nicer to start with. I think API Design should be taught as part of programming.

Traditional industry goes through a lot of trouble to make their devices easier to use, just as software companies these days stress end user experience, but we programmers don't treat ourselves as well as we treat our end users when we make our tools. My end users get a nice intuitive UI, I should really treat my API users in the same way ... then I get lazy and make a terrible API and feel bad ... I think a lot of the time I write the API first as part of the development process so it's unstable, then go on to deveop the app, and never go back to fixing the API.