Something I call Event Stream Assistant. I found myself commonly having to code small utilities for message brokering management/assistance (over and over again)- for the simple things like:
Flat File Processing,
Flat n' Sort,
Single State,
Single State Merge,
CnC (CLI for managing (SAS) ESP projects).
Logic Engine (basic logical engine / schema interpreter)
Pika (AMQP), MQTT wrappers, and Websocket Async services...
Some of these items are in production environments. I plan on releasing it open source (fully) once I get around to it. It's really useful.
Abysmal exception handling,
Character encoding issues,
Incongruity code style,
Delusional developers. (I'm in that last category for sure)... but hmmm... probably should check myself at that statement.
I responded without reading anyone else's comments-- I'm so happy that my Past [name], Future [name], dialogue is something other people do! You're "other me" is the same as my "Past Jon"
haha-- Remember to thank your "other me" and you should make sure to drop little notes addressed to your future self-- beacuse it is REALLY rewarding to find a note you left addressing your future self like "Hey, Future Self-- If you're looking for the actual module that does the communication-- it's: [location]"
And if a year later you are doing EXACTLY that-- trying to track down that thing-- and you start with something you know -- and find that note- It's hard to not exclaim- "Thanks Past Self, you just saved me some searching- hats off to you sir"
Sometimes-- but most of the time when I look at code I wrote and was proud of but 6months or a year later-- I'm like, what was I thinking- I would of done it differently now. I call it programmers remorse. Since we're always learning and patterns change over time based on technology I think that most programmers live in a constant state of embarassment over things they previously had done.
However-- sometimes (with increasing rate into my 15 year carreer) I need to modify something and had not touche the code in a long time-- only to find to my supprise I already had that feature or ability coded into it... I then have to say "Thanks Past Jon- This is Future Jon (to you) and noice forward thinking"
While in isolation due to gobal things... it's a good time to make sure Past you and Future you get along-- Present you (third state) is both past and future but leave some notes for Future [yourname] and make sure if you find notes from Past [yourname] you remember to appreciate their work.
I know how you feel- It's always rewarding when you worked on something but never finished it- you knew it was a good idea when doing it-- then years later someone else does something very similar. No anger from it, not like they stole your idea- it just validates that your original idea was so good that it was just a matter of time until someone else did it. Makes me feel all warm and fuzzy.
I really enjoyed Angular 1.x, was not happy with the 2.0 version (other then they fixed some critical performance issues with scaling websites). It was perfect for making simple single page applications for internal use at an an eCommerce company. POS, Order Processing, RMA processing, Research, competition and price controls, inventory & warehouse management, etc. I use ReactJS for large applications these days.
Upfront, I'm not a Apple person. I generally buy Business Class windows machines (after making sure I can install Linux on them). While their speakers generally arnt the best, I do enjoy the extended battery life and SSD. I mostly use them for coding laptops. I also like the "flippy" ones, but that's only because I have the tendency to carry them around by their laptop lid and this way it does not snap the neck.
Ah- I was not aware they had an LTS with different versioning. (And I did attend DjangoCon many years ago)- I clicked on this article initially because I was curious with what USSD was in the first place-
Why Django 1.1? Super old school right? I'm actually suprised that Django supported Python3 fully back then... then again I've been super slow to switch to Python3 but I think my earliest Django app (an eCommerce website) was at least 1.3 possibly...
I'm just wondering if other then just habit and 1.1 being what you're familiar with you chose to pick such an old version.
Python backend is easy to learn. JS for front end is critical. For JavaScript, make your life easier- start at ES6.
For Python for backend start super simple for small projects. Bottle.py or CherryPy.
Templating is a thing of the past, use Angular or ReactJS for front end development and use async calls for all data loads.
That's what I'd suggest. Python is easy to learn, start with simple things like bottle.py to to make a simple restful service. JavaScript can be a mess if done wrong, but ES6 is a game changer. I like both Angular and React, I find Angular 1.x super easy to use and learn but never use it in produciton.
If you're starting out, that's a quick dev cycle and easy to learn.
A clock on PST (I live in EST).
3d Printed various objects.
3d Printer (I overtook the desk next to me).
Lots of clutter. Papers, Misc. Junk.
Misc D&D items (Team building).
Peak Proformer Award 2017 (Q1).
Scatterd notebooks and pens.
Of course Computer, 2 monitors, 3rd USB smaller monitor.
Nurf Gun.
Cirtic Acid.
Water bottle.
Chromebook as aux computer.