top of page
Search
Writer's pictureMike Reshetar

Back to Programming

I started my career off in programming - System 370 Assembly - if that means anything to anyone. While that career was short-lived, I've done lots of scripting over the years thanks to my time programming on a VIC20/Commodore64 as a kid. Over the past 2-3 years, I've picked up Python and learned to leverages classes, dictionaries, JSON, etc. thanks to a great mentor at Cisco (Thank you Nathan!). Last week I started helping on a project leveraging Go. As with all languages, many of the constructs in Go are similar to Python (looping, decision trees, variable types), however I was surprised by a few items: - Python is very much about data - Python is class-based/object oriented - Python messes with your brain when it comes to variable typing - Go is more structured in variables - Go has multithreading built in, whereas in Python, multithreading is cumbersome IMO. - Go is not really object oriented, which surprised me.

- Go Interfaces do not start with 'Interface Ethernet x/x'.... This all reminded how programming languages are like a tool box. Not everything can be fixed with just a hammer or just a screw driver and the same applies to our jobs. Having multiple 'tools' available (Go, Python, BASH, etc.) gives flexibility in how we get a job done. Now to figure out what 'interfaces' mean in Go....

9 views0 comments

Recent Posts

See All

Comments


bottom of page