Profile cover photo
Profile photo
Alex Bynum
214 followers
214 followers
About
Posts

Why open source and similar concepts in technology isn't new:  simply put it is just community service.

Things like free to everyone and/or open source has always been around.  We just call it differently.  Community service, giving to the community, community investment;  these are all older versions of open source.  

Pretty sweet, if you ask me.  Maybe they will make programmers who are convicted of minor crimes to contribute to open source projects as their community service.  
Add a comment...

Post has attachment
Add a comment...

Post has attachment
Add a comment...

Quick thought experiment.

What if DNA based life was engineered to grow and learn and adapt to be the helpers of some other type of life, and we, Humans, rose up and killed off our engineers?  

Like, what if we went all sky net on the people that made us?  

I swear I am not 12 years old anymore, but things like this still amuse me as an outlet for intellectual exercise.
Add a comment...

As a computer programmer I like how things work logically.  The machine does exactly what you tell it to do.

As a programmer who specializes in user interfaces I have found that the best practice is to assume the user will, any time they are able, give you inputs that break your code, so plan accordingly.

This is fundamentally different from taking machine inputs and handling errors that way.  You can allow only "good" input and be pretty much ok.  The white list approach, as it is called.

With UI work, especially when the user gets to define "good" not only do you have to worry about nefarious inputs, but also plain random "stuff".   This often times means kissing your regex goodbye.  It won't work.  

So, combining user inputs with system generated things, such as labels or id's presents you, the developer, with interesting logical challenges that I did not have to even consider when dealing with machine to machine communications.

My rule of thumb is cascading errors.  Where a user can input something that breaks your code, even with pretty resilient error handling that can catch it, if they are allowed to continue with their work the error will cascade through your system and cause havoc.

Challenge accepted.
Add a comment...

Post has attachment
Add a comment...

Post has attachment
Add a comment...

Post has attachment
Add a comment...

Post has attachment
Add a comment...

Post has attachment
Add a comment...
Wait while more posts are being loaded