Says a person whos never developed a complicated application in tools commonly available before mvvm was a pattern.

I use C#, C++ and GO pretty heavily Rust seems interesting but is a bit boutique for my tastes, JS is one of those languages you just have to put up with when working on any kind of web application but i avoid it for writing api's and doing backend work because i know multiple languages and there are better tools than JS on that side of the house.

The fucking put amp in everything and since I post from a phone I didn't see it and I can't edit it.

Every level and facet of society corroded by Marxist communists only way out is a total civil war. No one has the stomach for it though so we will all get the boot stomping on our faces for eternity.

Absolutely but it's clear they are influnlencing decisions with funding and sleeper agents they are embedding into these open source projects. Redhat is doing the same thing and it seems like every distro is trying to turn a server OS into a desktop OS for normies.

This is definitely about redhat and Microsoft subverting Linux with potterings maniac code ramblings. Pottering is just a convenient moron to spearhead the effort with.

I hope to God we get some other options besides shitsem.d

Yeah all the people who tell you to just shell out in python and start another process dont really understand concurrency. Not only that then you have to start trying to track and manage process ID's which is the most fragile shit ever. It's always better to just use a real language instead.

When you spend hours to fix a bug caused by someone deleting a tab and a space that then isn't caught by brace matching by the compiler because the language is interpreted you wont think the off-side rule is so great. Java is terrible but it's only so high up in the list because its the only language Indians can understand how to program in. I use golang, .net core, and c++ for serious shit and i use javascript or python to piece together little automation scripts when what im doing can be done in less than 50 lines.

Python is a horrible language. The community forked it and any language that is so loosely defined that text formatting effects execution at run time is a bastion of degeneracy. It also is garbage at concurrency.

I swear to god microsoft release numbers are a fucking trainwreck. To make it worse release numbers are shared across OS versions so there is all sorts of confusion about what release and version of product people are talking about whatever bug was fixed in. THis is pajeet level bullshit devised by pajeet engineers since thats the only people those companies hire now.

I do the same thing for a lot of work but most of the time the scripts are system level glue tying together lots of already written functionality. I don't necessarily think of that stuff as an app though. To me an application is more monolithic than that and narrower in scope.

You can call python or c++ from c# using com interop bindings if you have some external library you want to consume from your c# app. I'd recommend learning c# over c++ because it's going to be more widely used except in niche use cases.

Yes. I love python but there's just certain levels of complexity where it's better to use another tool. All of the massive projects using it end up rewriting in something else once they hit a certain complexity.

Avoid functional scripting languages for complex applications.

Theres lots of different types of programming. C++ will probably be more applicable in engineering type jobs where your dealing with writing software for hardware devices and maybe as a game dev although most of that is probably done in c# now in most shops or whatever the current mobile app platforms use. Id start learning python if your going into scientific programming or javascript if you want to do front end web dev type stuff.

I like how her abstraction layer and object classes also makes no fucking sense. At the very least the WillDate method for each class should have their counter part classes being passed in as an argument. If she really wanted to get into it she would have made an IHuman interface class and an abstract human class with an method WillDate and an abstract protected method MeetsCritera that then boy and girl class would implement and they would have a base class of Human.

Yep dependency hell I've seen it in python and ruby too. I think the key to mitigating that is microservices that are only doing a very niche thing with maybe 1000 lines of code. When its hard to upgrade you throw it in the trash and rewrite it with something new that's easier to deal with and up to date and only maintain the api signature. Then you split up all the monoliths into a maybe a few hundred of those. The key to making it viable is you need containers and an orchestration system to manage deploying, monitoring, recovering from faults.

Gotta learn how to stay on top of your csproject file and learn how to use build targets. .nets package management is excellent was one of the first modern languages with an actual one built into the language itself. Every other one (JS)npm,(Python)pip,(Ruby)ruby gems neglect framework targets and you have to use some other tool on top of the rudimentary package manager usually developed by a third party (nvm,anaconda,rvm, etc...) package management is an afterthought and still suffer all of the problems you talk about.

Where Microsoft is behind right now is that they haven't migrated to a linux kernel and re-implemented the windows apis on top of a core that supports lxc. The container solution on windows is the most bastardized thing i've ever seen.

Yeah thinking about what your going to write, researching etc is probably 30% of the time. Usually ill have done about 3 weeks to a month of reading research before a large project unless I'm already familiar with the technology.

It varies. Between 40 and 80 I guess. The last 3 weeks i put in over 80 per week but ill throw in some weeks in between projects where i only do a 40 hour week. Some weeks every second I'm not sleeping I'm writing it really pisses off the wife.

If you dont understand the basics all your code will be a pile of shit to work on regardless of what language you write it in. Programmers that cant build a maintainable piece of software are a dime a dozen mostly people who only learned "functional" programming. You can spot them quickly because there code is an amorphous blob of repeated code lacking any structure. They couldn't define a domain boundary and form an interface for abstraction to save their life. Once the goal of their code becomes more than trivial the ability for anyone to come through and refactor or add features is entirely determined by how quickly they can convince management to throw it in the garbage re collect requirements and break it up into a properly structured and layered set of libraries each with their own set of responsibilities and composed behavior.

Start with an oo language java or c#. You'll learn the basics of abstraction, composition and strict inheritance there along with how to define interfaces one of the most important concepts in programming. Then you can move on to the unstructured dynamic languages.

Neat feature. Most of the recent docker patterns ive been using involve having the app at startup pull most of the config from either vaults or service discovery. It becomes unwieldy for cicd or cluster management tools to feed a container dozens of env variables at startup. Abstracting config away into a keystore service generally means you can get away with only passing 2 or 3 into the container and the rest the app fetches on its own. This will be handy for storing the initial secret used to access the keystore.

Just keep your head down until you find something and leave on your terms. Be on the lookout for bad practice and management teams that over run their engineering teams with stupid requests.

One question I ask is, What is the strategy for dealing with technical debt and what was the last project that was completed that was entirely centered around addressing technical debt? Another good one is, How often does developer thrash occur? It's impossible to feel like you are making progress somewhere if you are being moved on and off projects and bug hot fixes every other day.

Doing so also ham strings dev teams into never being able to do non trivial refactors to address technical debt in applications. If you are constantly waiting for the next omg freakout explosion or pie in the sky new feature request you would have to hack together and can never be proactive it's impossible to be happy doing this job.

Yeah I've gotten burnt out in this profession before but i never set it down. When i get burnt out i usually find a different employer as it's almost 100% of the time burnout caused by un necessary employer drama and bad decision making thats the root cause.

Rejoice!!

Nice. Ive got a couple of micro services in prod on Core 1.1. Fix is pretty simple.

Im starting a tech debt refinancing company. I can refinance all of your tech debt for pennies on the dollar.