Paid Programming
July 31, 2024
I’ve had a very little to none formal education associated with information technology or computer science and I’ve rarely (if ever) been into reading books either, and still managed to have troube to learn programming.
I’ve seen a problems which I have not been aware by my self-doubt which pushed me towards additional validation of what I’ve been doing and make sure solutions which I’ve come to unknown problems been acceptably flawed.
I’ve had a beef with LeetCode, it rewards pattern recognition and memorization more than real problem-solving. Once you identify the type of problem, the ‘correct’ solution is usually just a short Google search away. I’ve always tried to resist that and force myself to understand the problem on its own terms and use a solution that actually fits what it’s asking.
I’ve been a somewhat a “glue developer” could see a whole space within which objects have existed, connect them togeher in order to produce coherent system in which there’s been harmony inside.
I’ve could never settle down for a single set of responsibilities which been associated with my role which almost always shifted through design, product, engineering and management. I’ve simply been despite doing nothing at all.
I’ve always been somewhat unable to solve mathematical equations and a formal specifications of computional problems were challenging to grasp for me. I’ve been doing what I could to follow through objects and “match” a solution of which I am aware or not into a problem of which I’ve been aware or when I’ve had a feeling something been off it’s place.
I’ve always been breadcrumbing through dependencies within systems, along with separating concerns and maintaing bendable rules about software architecture which have affected future shape of a codebase before one have evolved.
I’ve anthropomorphized systems on which I’ve been working, seeing production as a living organism which have own processes which shouldn’t be disrupted and treated it gracefully if not carefully compared to a development environment which been my playground where breaking things and going fast been rewarding.
I’ve been pretty bad at reading code and been attracted into idea of writting code which I wouldn’t be supposed to read in order to have a meaning whan one could be doing - I’ve used symbolism and abstraction to navigate through codebase. I’ve never had a problem to understand what code represents depending on a context and level of abstraction which been necessary for me to know about.
I’ve never seen value in knowing ex. operating codes for CPU architecture while I’ve been building web application in interpreted language, it’s just seems like a inefficient and in some context useless information - just noise.
I’ve depended a lot on community and ecosystem of my programming language, and try to keep a healthy balance between external dependencies and inviting public code into codebase for which I’ve been responsible. I’ve been open to learn about libraries which I use by trying to reproduce them on my own in free time.
I’ve been designing modules with clear APIs (by my own taste) which have hidden unnecessary information and methods and exposing only what should be interacted with by customers of a given API. I’ve almost never extracted modules into microservices until it’s been absolutely necessary.
I’ve didn’t liked work on code which been not in my taste.
I’ve been revieving code which been written by not me and always tried to put a lot of effort into explaination why I would do things other way as I’ve been aware (as for a senior) other collaborators of repository might not hold up same understanding of a existing system as I did. It’s been somewhat important to me collaborators would hold similar assumptions to ones which been behind existing codebase unless assumptions weren’t fundamentally flawed.
I try to use as few software components as possible. Ideally, just the application itself which would be self-contained in executable binary. I solve deployments with set of basic shell scripts and containers when there’s a need to do such.
I’ve once wanted to explore what programming languages are about and decided to stay at a level of knowledge where I am aware of that code is parsed down to AST which is later on interpreted or compiled, and I am aware that I don’t know all the details which goes all the way down up to machine code and further.
I’ve built a software used by users which have served business (or myself) well.
I’ve had a feeling only people which have liked me been CTOs and eventually coworkers been not a fan of me. I’ve been avoiding a talks at all costs because I would rather write a documentation than jump on individual calls.
When I’ve had a break from software engineering I’ve thought about an potential future directions in formal verification but my own lack of grounding I sorta give up and decided to do a little of writing about life.
So being stupid kind of worked out for me, at it’s own time.
Fucking kindergarten.