"yeah, we could probably fix that deeper but it's going to take 6 weeks of meetings and 3 departments to approve this. Is that really what you want to spend your time on?"
This is where a developer goes from junior to serior.
I would definitely agree, now that I have started to save my bookmarks into a dedicated section on [my personal site][1]. I want my blog to become my central place for all my knowledge dump, that is indexed the way I want, and can be explored through simple Linux tools (grep, find, etc.). I might also try linking it to a local LLM to query more naturally.
Also, I personally miss good old [del.icio.us][2]. It was way ahead of time.
Recently read a [similar article][1] and I couldn't agree more.
Essentially, you need to stringent the code review and testing processes. You cannot have AI doing code generation and code review and/or testing together. Either you have code generated by AI, and have Humans review and test the code, or have humans write the code and AI supporting with code review and/or testing the code. Never both.
I find the second approach better - AI supporting with testing and code review processes. Code generation is still Developer's domain and I don't see AI writing Production level code anytime soon. Developers can use AI to generate snippets of code which is then adjusted to make it production ready. That is probably best of both worlds at the moment.
If you are given a house with a bad foundation, and need to build on it, literally your only option for improvement is to see if anything can be salvaged, and then you start over.. ideally not making the same mistakes the next time.
I happen to stumble upon [this Engineering Salary Formula][1], and I am not sure if it is good or bad. What do you think about this?
Here is gist what I could make:
1. If you took 4 performance reviews, and gets promoted in last review, you compensation formulates to be - New Base + Last 3 Raises (Meets Expectation) + 1 New Raise (Exceeds Expectation)
2. If you are doing just fine and get meets expectation, you only effectively get 3.6% increment yearly (using the $180,000 example)
3. I still cannot see how people get compensated for their long tenure.
Within over 14+ years of my professional experience, I have seen systems and processes of all sizes and complexity. And I never felt out of place in any of those situations. My experience, attitude and ability to solve problems always helped me to build solutions which align with business goals and achieve success and results. A majority of my experience comes in the E-commerce domain, I have been exposed to various other domains and business processes. My ability to get on-boarded on to newer domains and businesses, and become a valuable asset, is one of my key aspects of a successful professional journey.
On the technical side, I have worked with all sorts of technologies, programming languages (Java, Python, Kotlin, Javascript and more), clouds (AWS, Google, Azure), Datastores(Postgres, MySQL, Redis, Hadoop, Hive, Databricks, MongoDB), Web(Node.js, React), CI/CD, Data Science, Machine Learning, GenerativeAI, Bash scripting, and more. The variety of technological exposure allows me to build scalable software architectures that not only add value to business processes, but are also loved by people who work with these architectures.
Lastly, I am always curious and eager to learn and find ways to contribute. I never feel shy of any work or support that is needed off me. I ensure I am able to support myself to the best of my knowledge and abilities.
Not only that, but syncserver can be locally installed so you have an additional layer of autonomy if you want that. (The data itself is already end-to-end encrypted, so it is not really necessary to be exact.)
This is where a developer goes from junior to serior.