• 0 Posts
  • 18 Comments
Joined 3 years ago
cake
Cake day: June 7th, 2023

help-circle
  • I should probably try what the O.P. did as I also have an ASUS router with Merlin. However, in my case, I have a Synology NAS and I set up VPN on that and use that server as my VPN. I have a certificate-based sign-in through a single port on the router.

    I use a Public VPN service when I’m out and about and then connect to my VPN when I need to do stuff on my network, Like syncing my Joplin notes.




  • Always on although my Phone VPN recently has failed to start up automatically or has shut down randomly lately and I got to get that fixed.

    My reasons are just privacy. I’m not using it to get around regional restrictions. Additionally, it helps when I want to use a public Wi-Fi, especially if it doesn’t have any passports on it.

    I will not connect to public wifi without VPN.






  • How do we thrive?

    Accept that change happens. Be equal parts curious and critical about the new stuff.

    That is not the solution. One cannot thrive if one cannot be seen or has been discarded as a relic no matter how up to date that person is. They will never be granted the opportunity to thrive as they have before as an employee. Their only hope to thrive is if they (magically) gain all the skills and networks necessary to be an entrepreneur that can do it all themselves. Nearly a unicorn.

    Meantime while trying, they burn through what savings they have on the hope and dream of “being relevant again” and have about a 5% chance of success.

    Maybe the author is misunderstanding the gist of the original article. Regardless, he raises an obviously accurate assessment of those who hold the hiring power. When I was recently out of college learning my craft, it was a common sarcastic refrain of either, “What could be so hard about it, it’s all 1’s and 0’s” or “What’s taking so long - you’re just typing on a keyboard”.

    This has been a problem since long before I graduated from college (when classifieds called for 10 years experience on an IBM system that was released two years ago) (see, things don’t change so much - names and places, sure, but not much else). People who are in leadership positions, who think they’re better and smarter than most everybody else, frequently belittle those who do the grunt work, both physical and mental. It’s gotta be a corollary to dunning-kruger theory (or maybe an example of it).


  • Oh, they “come home to roost” almost immediately - you just don’t see it because whole teams are doing everything they can to hide it or ignore it - nightly manual data update statements, etc… Here’s just one real example.

    In my last (read: final) job as a senior software engineer, I discovered dozens of serious problems with the system I was assigned to “maintain”. They ignored all of them - wouldn’t let me fix anything. Meanwhile I was responsible to solve production problems on the daily (duplicate data, insert failures, performance slow-downs, etc).

    It wasn’t long before the fact those problems weren’t going away that they became problems I “caused”. Meanwhile, all the fixes I wanted to make were ignored. I had one problem I dissected and and gave my boss a brief write-up of the scenario. He told me I needed to do deeper analysis. When I came back a few hours later with a considerably more detailed explanation, he didn’t read it and complained of a “wall of text”, which he literally told me to write. Then he created a random-number hack to “fix” the problem.

    They did not grasp the concept of data normalization and primary keys as they had one particular table that represented two levels of detail (for example, account -> order). They put both in one table and had a code based special update to the “account” number so they would not get a PK violation rather than just fix the data structure.

    They had as single database connection open all the time to handle all inserts in a singleton service, then launched as second one on the same database to process messages faster - and couldn’t understand why it didn’t double performance.

    The main routine had a cyclomatic complexity of 360! I shit you not! And everybody agreed it was “95% working” even as we continued manually fixing (the same) problems daily.

    Week after week, the customer (internal) would raise more data issues as “new” problems. I’d routinely ask two to three questions about the data set and explain that’s the same problem that’s been going on for six months, and if we could just get my PR reviewed, we can test it and deploy it.

    All these problems were in a single service.

    I was let go not long after the 1 month probation they soon initiated and told I was not performing at the level of a senior developer.

    This is how delusional these people are. They refuse to acknowledge their flaws even after hiring someone specifically to solve them. They blithely call their monstrosities “successful” while committing many staff to late nights and weekends “managing” it.








  • Use AI, learn the methods, tools, uses. Then keep working through the process yourself like you do now with AI as a partner who sometimes flakes out.

    Remind yourself of the tenents of critical thinking regularly. Never just accept what AI tells you. seek proof behind the answers. Think through those answers to ensure you understand the logic behind them.

    Fight complacency.