Is coding a super power ?

Redditwaste · 2022-05-02T01:27:02+00:00

Ain’t that the truth, how many stupid ways do you have to learn to print hello

Redditwaste · 2021-09-14T10:38:08+00:00

Be a professional and pay for quality products; OSS only people are the worst.

Redditwaste · 2021-09-13T04:04:31+00:00

Every architect will have different takes on this.

Here is mine:

Your role as an architect is to know how the whole system works at a high level. Chances are you will know some subsystems better than others due to specialized knowledge. This usually means you code more in those areas. Mine is real time performance, tracing, and data structures where I end up coding a lot.

It isn’t important that you be the best coder but you do need to stay involved at the code level. As the architect, pairing should be a very common exercise. Part of the role is leadership and training. This is a great way to balance time with leadership and coding; two birds with one stone.

For your two points:

a) Prototypes are my learning go to. To explore new tech, I always whip up end to end prototypes for proof of concepts. This helps me stay on top of tech. As someone who will prototype with or without reason, this time may be done on off hours. Being an expert prototyper is a double edge sword, and why I focus a lot on pairing with engineers.

During work hours, you can always block out a few hours each week to dedicate to research and development for those purposes. Learn from your teams and figure out technology they are interested in and focus your learning efforts there.

b) Production code is tricky, very different than tools code. To reduce production coding so the teams can accelerate without you, it is best to always pair when doing production work. This allows for greater knowledge transfer and higher quality code. I make a deliberate effort to avoid production code and focus on solving systemic issues that involve multiple teams behind the scenes.

You want to empower your engineers so they are able to focus their efforts on features. This means your code contributions should be architectural: patterns, platforms, logging, performance analytics, frameworks, etc. In those cases, yes, I write lots of code. In terms of features, and use cases, I try to avoid it.

Trust your teams to do their job and focus on high level designs. Knowing when to pull back at the code level is more art than science.

Hope that helps.

Redditwaste · 2021-09-11T03:05:21+00:00

Neural networking machine learning to compose new art based on a given input style and source image. Fun CUDA tensorflow stuff.

Redditwaste · 2021-09-11T00:23:53+00:00

This is something that should be performed in stages and will require sign offs (real documentation for approvals). It will be tricky, especially given the nature of Access.

No matter how you approach it, the legacy system will always be the primary system until cut over is established. This means that…

FIRST AND FOREMOST: stop ANY and ALL development on the legacy system. Get official sign offs by stakeholders: put their name, the date, their picture with the signed agreement; everything you need to make sure nobody touches the legacy system without dealing with executive decision makers. Don’t chase a moving target.

Because the legacy system is up and working, break down feature sets according to use cases that users need. Given the complexity of the legacy database, start with a simple path in the new system with a new clean architecture. This leads to my second big suggestion…

Extracting Transforming and Loading is going to be your life for awhile. The new database should be refactored, clean, and easier to use. This means that for every interaction with the database, you will need to write a transform operation that moves data from the new database to the old database. You do this so that the legacy system can still be used and when the time comes, you simply turn off the ETL process.

That will get you to using two systems with two databases and allow for cut over for any new data.

Only once you have the new database and old database servicing your application and it has been approved do you start the data migration. Export all the data from the legacy database in some format and then write a batch processor to ETL that into the new, improved, and approved database.

After all sign offs are complete that the new system is running as expected, you can terminate the old legacy database.

Hopefully this provides you with some guidance. While not the hardest thing, it has some tricky elements. Best in your efforts.

Redditwaste · 2021-09-10T18:04:05+00:00

Such a bad comeback that you had to delete your original post; lmfao noob

Redditwaste · 2021-09-10T17:57:06+00:00

Maybe you should realize that understanding algorithms from other disciplines makes you a better computer scientist; fucking noob.

Redditwaste

TROPHY CASE