Azure Artifacts has been great for private stuff. Have you tried Github packages yet? Works well enough for public packages. I don't know what your use case is, but what prevents you from using nuget.org?

Audit logs and Access control paper trails.

Security event logging has to be:

1. Broadly accessible
2. Write-protected
3. offering some proof of completeness.

These three requirements are tricky and often conflicting. Block-chain might be an inefficient way to achieve these, but the glove does fit quite neatly.

Logistical paperwork

• Purchase Orders/Invoices and packing slips
• Waybills/Bills of lading and CMR's

These kinds of documents require multiple stages of matching and approval by untrusted 3rd parties. There are dozens of ecosystems of interacting systems that support processing these documents, but most people still use paper. Paper is more reliable when you need to deliver a container full of diapers from Poland to North Sudan. It's more reliable but incredibly prone to fraud and forgery. Having all of these approvals and transactions tracked on a blockchain and letting different systems interact with the same chain, would make it possible without each ERP having a rest API to each other ERP.

Man, I have to agree. Your write up reflect my experience with Azure Functions in a mid-large sized application way more than the post. Fantastic

This is a bit of a narrow view of a very vague term. Having worked with many different sizes of organisations i can say that the responsibilities of whomever is labelled CTO are completely arbitrary. The only thing you can establish is that they are the person accountable for the technology decisions.

Sometimes that's a legacy developer, sometimes that's the first sys-admin.

Sometimes it's the VP of engineering.

Sometimes that's the person that maintains the best relationships with software vendors.

Sometimes it's the person that was hired externally to explain the tech to the CEO and let's them make informed executive decisions.

Sometimes it's just a public figure used to promote the org and maybe do DevRel.

Sometimes it's the Architect that designed the ecosystem.

Sometimes it's the ancient programmer that has kidnapped the entire codebase so that no-one else can sanely work on it.

Sometimes it's a six sigma type that setup the ticketing system, PRs and the release process.

At any size, the CTO is whatever the org needs him to be at that point.

Every engine is going to come with engine specific problems. You will also come against many general game development problems, for which the engines have come up with many different creative solutions.

I can't make it any simpler for you. You will waste a bunch of time learning stuff. The only way to avoid that is literally building your own engine that conforms to your expectations and assumptions, because noone else can do that.

There are so many invisible boring-ish problems. Ui, scaling, networking, instancing, level changing, loading screens, even scheduling etc. You need to learn to love the boring stuff, because it comes at a 10-1 ratio towards the fun-ish creative problems.

However it's best to start wasting that time today than next week.

The way I managed to get an intuition about the language is just building classic boardgames. Checkers, chess, diplomacy and go are great exercise to start working with lists and dimensions, declaring multiple predicates and have them interact with each other. Changing the state of the program and using the traces to branch out decisions. Remember to keep track of your interpreter. Different interpreters act in surprising ways. The order of operations of SWI is different than Tau.

After that, the honest truth is that Prolog isn't widely used enough to have a 'modern standard approach'. The best way is to treat it like any other embedded subsystem: light and concise scripts embedded in a grown-up language.

1. You need as many environmental reminders that you are doing work as possible:

• dedicated work place where you don't game or browse or do chores and taxes on.
• dedicated work time where you are allowed to do work.
• dedicated non-work time where you won't work and don't get to feel bad about not working on the project and avoiding negative emotions associated with the work.
• I have a dedicated work shirt only worn while at work
• figure out your attention sinks: music/podcasts/YouTube w/e and apply them strategically to signal that you are or are not working

2. Plan. Identify as many tasks as possible ahead of time and figure out what is motivational an demotivational. Motivation takes a nosedive once the low hanging fruit runs out.

• make sure to front-load the boring stuff and keep motivated by anticipating the fun stuff later. Please, Start out with the tests. TDD is a hack for ADD
• Ration your creative sessions. Once you feel you are plateauing force yourself create some novelty in the project.

3. Want and grit. At some point you'll have to grit it out. You have to make it clear to your brain that you want it. Make it personal. Want it not the way you want to have a cookie after dinner, want it the way you want to breathe. Don't even want the project, but want to prove to your brain that you are a rare capable human, able to start and finish a creative endeavour independently.

4. Make work time scarce and urgent. Having a child has done wonders for my creative output. I used to splurge 6 hour sessions kinda working on something..now I get maybe 40 minutes a day. An hour if I'm creative about it. But heck, does that hour get applied like nobody's business.

Hope this helps, best of luck!

Obligatory: Don't learn programming languages. Learn programming problems and which languages were developed to solve these problems.

Also, you say you've reached a reasonable level of fluency with javascript and python. What does that mean? Having a grip on the syntax is different than being comfortable with half a dozen libraries and building an application that solves real user problems.

If you're learning for the joy of learning that's great! But maybe then try something completely different than the C family of languages. Try Prolog or Assembly and try to make some applications!

No one can make moral or ethical judgments for you. I recognize the hesitance towards defense, surveillance, attention-commerce, and tech consultancy. However, there can be positive moral and ethical perspectives even on those examples. The reverse is also true for industries that, on the surface, seem much more ethically marketable. I personally consider any automation that removes human work from the economy to be a positive contribution to humanity. You can make the perspective that robbing labor opportunities from real humans is a moral failure. My point is that moral choices are usually based on a combination of personal values and a certain understanding of the problem space.

I can't make ethical suggestions for you, but here are some options that might appeal to you:

• Paperwork Automation for professionals (Lawyers, Notaries, Hospitals, Governments)
• Bioinformatics for medical and environmental applications
• Computer vision for medical tools (Detecting anomalies in scans)
• Agrotech (seed, grow and harvest food more efficiently for a better environment)
• Prosthesis Robotics (Help people in need of mobility)
• Accessibility Engineering (Help people with disabilities access websites, programs and games)
• Environmental modeling for sustainable planning
• Supply chain optimization (software to get goods from A to B with the least impact)
• Video Games!

A career is not only the industry or sector you service. It's also about the relationships and colleagues you deal with. The work ethic and labor standards you have to deal with. The opportunities you get to build a reputation. The physical location of the opportunities. These are all things to consider when starting out on a career.

Edit: The best way to feel good about work is to set reasonable expectations for yourself to others and meet them consistently. Understanding human problems and solving them. That's what telling computers what to do is all about.

I had been struggling with severe RSI for a few years and no one thing helped. I would try something out and the pain would return in a few weeks. What eventually completely solved my problem is variation. I have several working spots using different devices (traditional mouse, vertical mouse, thumb balls, trackballs, pen tables, touchscreens). I've made sure to just change posture and devices every few weeks. Ever since doing that, my problems have completely gone away. A mobile standing desk that you can adjust for squatting to slouching to sittin to standing and walking is great adds a ton of variation.

Inheritance is a fine abstraction. Easy to understand, but can't bring you very far. It's like a necessary evolutionary niche. It has its places, but it's most important as a gateway to get us to better abstractions.

I once thought that it might turn into a "one-eyed man is king" situation, but now I'm not even that sure.