On a scale of 1-10, how lazy are you when it comes to prototype code?

Me, well I'm a 'fuck it lets just wildcard anything that is a child of a GLib objects'

Don't be like me kids...

EDIT: Yes i know it should have been an override void

(!Rant) i play games on my pc with a controller. And I just caught myself reaching for it when finally starting on some web dev.
Talk about gamification.

It's all fun and games coding in Vala until you get an abort/segfault. Good luck with that.

So I have never done 'real' development on anything bar my current game engine Virgil, however found myself referring to C documentation for GLib and SDL2 rather than valadoc documentation.

Decided fuck it, I'm already converting everything to Vala's pointer syntax so I can have manual memory control, implementing stb_image and contemplating reworking SDL2_image into raw C so I'm not depending on extra libraries... Why do all this when I can just learn C and have more control.

Everything was going well and decided to buy the C programming language book, already knew about pointers and structs but ohhhhhhhhhhhhhhhhhhhh boi was I not ready for malloc .-.

Coding challenge: make an Android/iOS app using mainly Vala.

debian:jessie has lot many old libraries that cause memory leaks, which gets solved in future releases of these libraries. Yet, debian fails to accommodate these new releases. They do this to make jessie 'stable' they say. I am quite curious if these instabilities faced is what they call stability. Example: glib

used to hv a life, then i chose cs major