It’s not innovative anymore, but it sure was when it released. But they kept it near its peak instead of making it utter horse crap.
It’s not innovative anymore, but it sure was when it released. But they kept it near its peak instead of making it utter horse crap.
I can’t disagree with this… After basing the size off of the vertical pixel count, we’re now going to switch to the horizontal count to describe the resolution.
No… The house of representatives has grown multiple times with the last permanent growth in 1913. It did temporarily grow by 2 when Alaska and Hawaii were made states, but went back to 435 after those states got their appropriations of representatives.
You aren’t wrong… But everything with extended use needs to be maintainable. Making a change in 5 places sucks.
Plus, that’s what open-closed principle is all about. Instead of adding additional functionality to current working code, you extend and modify.
My 4 host machines run debian (proxmox). I have a lot of different guest flavors running though, debian, fedora, rocky, one old guest still running Ubuntu and even a mint sandbox machine.
I probably have a bit more complicated self host than others because I am using it both for my useful internal services (jellyfin, git, pihole, etc.) I also run a whole lot of services for learning, such as kubernetes and dns. Plus a whole lot of other mostly useless stuff that I only use to test different architectures or automations that come in handy as an SRE.
The thing to think about is reusability. Are you copying and pasting code into multiple places? That’s a great candidate to become a class. If you have long lived projects (i.e. something you will use multiple times over a lot of years) maintainability is important. Huge functions and monolithic applications are very hard to maintain over time.
Break your functionality out into small chunks (methods and classes). Keep it simple. It may take a while to get used to this, but your time for adding additional functionality will be greatly improved in the long run.
A lot of great programmers were terrible at one time. Don’t let your current lack of knowledge of principles stop you from learning. One of the biggest breakthroughs I had as a programmer is changing how I looked at architecting applications. Following SOLID principles will assist a lot in that. Don’t try to understand and use these principles all at once, take your time. Programming isn’t what you make your living with, it’s a tool to help you be more efficient in your current role.
Realize that becoming a more effective programmer is different for everyone. Like you, I was self taught. I was a systems and network engineer that decided to move into software development. I’ve since moved into a role that takes advantage of all the skills I’ve learned through the years in SRE. like you, a lot of what I write now is about automation and analysis.
The NFL is a non profit, the teams are not. It still doesn’t make it right, though.
Leave me out of this 😁
Holy crap, I’m hearing possibly 2 more suspects
Three… They nabbed a third.
I’ve migrated to prowlarr from jackett. It’s far faster in searches.
Land mines are still mines.
who dropped the ball
That’s new years
It pains me to read that you went through this. I really hope you can find something that keeps you happy so you can make it through the losses.
Don’t mess with Kunta Kinte!!!
There are a few brands of preservative free drops that aren’t single use now. The applicator on these is different so the preservative is not needed. Granted. I use single use refresh most of the time at home, but I carry a bottle of preservative free when I go out.
as shocking as it is
That sounds like a good reason to not use the connector
But you’ll have cool dragon shouts powers.
Poseidon?