progmetaldev
Joined 5 years ago
Joined 5 years ago
I finally got the physician to switch to a proper client/server architecture using .NET WinForms and ASP.NET RPC calls. All issues went away, and I was even able to allow staff members to edit the interface to set what mattered to them most at the top of the application, by building the lab testing form in XML so they could move the X/Y coordinates to where they wanted them. It wasn't even a feature I had thought of, just a physician looking through the technology and figuring out how it worked (luckily the business and security logic were on the server, so a bad actor could only have destroyed their own local copy of the app).
I am constantly having to dodge these e-bikes in the streets, mostly driven by children/teenagers, who do not follow traffic laws (I'm in upstate NY). They don't even follow standard bicycle traffic laws. Driving in the city, I regularly have e-bikes coming at me against traffic in my lane. I would be absolutely devastated if I hit someone with my truck, and I honestly usually drive lower than the speed limit in these areas. It's even worse in the suburbs, because these people don't have the same survival instincts when riding these e-bikes as those in higher traffic areas. It's constantly on my mind that if I hit one of these children, not only will my conscious be filled with guilt, but I will probably be charged with manslaughter charges.
Upstate NY is starting to create laws and restrictions around e-bikes, but that is not stopping parents from being uninvolved. In the cities, there are rentable e-bikes being used everywhere, and it only requires the ability to pay to use it. I'm all for making transportation easier for those of lower income, or that prefer to use something that doesn't spew emissions like a gas-powered vehicle, but beyond being able to pay for the e-bike there is little being done to regulate or enforce how they are used.
Happy they are independent and allowing access to their API. Seems like it may be time to work on a personal project to track the data in a way that matters to me, rather than just what you normally get built in.
I haven't used Zed, but can you choose the PHP version, or point to a PHP executable for warnings/errors? I know in VS Code, you point to the PHP executable for the version you are using, to catch errors. I haven't created a new PHP project in quite some time, but I did work on many older PHP projects, and never had this issue with VS Code. I suspect even if you don't go about it this way, there has to be configuration to specify what is and isn't an error vs. warning.
As an early teen when Broken came out, and I happened to be connected to some people into the 90's emerging industrial scene (not to take away from earlier scenes), NIN has always been a huge inspiration and got me into the grittier side of metal music.
I enjoy the general feeling of the book, like claustrophobia inside something that grows infinitely. That's the best way I can describe it, but I haven't gotten more than a quarter of the way through. I do need to go back and fully read it.
I often have a lot of time between projects, and am able to really think about things, and write the code that I'm happy with. Even when I do that, I do some more research, or work on another project, and immediately I'm picking apart sections of my code that I really took the time to "get right." Sometimes it can be worse if you are given vast amounts of time to build your solution, where some form of deadline may have pushed you to make decisions you were able to put off. At least that's my perspective on it, I feel like if you love writing software, you are going to keep improving nearly constantly, and look back at what you've done and be able to pick it apart.
To keep myself from getting too distressed over looking at past code now, I tend to look at the overall architecture and success of the project (in regards to the performing what it was supposed to, not necessarily monetarily). If I see a piece of code that I feel could have been written far better, I look at how it fits into the rest. I tend to work on very small teams, so I'm often making architecture decisions that touch large areas of the code, so this may just be from my perspective of not working on a large team. I still do think if you care about your craft, you will be harsh on yourself, more than you deserve.
Although I probably don't make nearly as much as that COBOL developer over 20 years later, I would be willing to bet that I am happier and haven't locked myself into a specific technology the way that developer probably has. Money is great, but if you actually care about what you do, I expect that being stuck on the same codebase for years isn't too satisfying (at least on code you didn't have a hand in creating from the very start). Too many people translate money into happiness, and I guess there is a balance there, but usually it's not possible to maintain happiness based off money when you do the same thing day in and day out.