Earlier quoted context omitted.
> I get the impression that they're continuously discovering new and exciting ways that individual facets of individual pieces of software (and the processes around them) suck As a software engineer, I think this is my experience at every job I've had around systems in general.
As a person sometimes overly distracted by grammar, I would like to thank you for using the "As a [description of subject], [subject] [rest of sentence]" construction correctly. Getting this wrong, which is called a "dangling modifier" error, is common. Examples from today's front-page HN discussions: As a new (1 year) coder starting out at 39 years old, this sounds very similar to the path I envision for myself. As…
I'm not burned out, I'm pissed off
251–260 of 335 posts
Re: I'm not burned out, I'm pissed off
#252Re: I'm not burned out, I'm pissed off
#253Earlier quoted context omitted.
I guess you could have used a private nextcloud instance to transfer it.
I guess in such a locked down environment that would be grounds for termination.
Re: I'm not burned out, I'm pissed off
#254"A new car built by my company leaves somewhere traveling at 60 mph. The rear differential locks up. The car crashes and burns with everyone trapped inside. Now, should we initiate a recall? Take the number of vehicles in the field, A, multiply by the probable rate of failure, B, multiply by the average out-of-court settlement, C. A times B times C equals X. If X is less than the cost of a recall, we don't do one." N…
Re: I'm not burned out, I'm pissed off
#255I asked my SO recently how she view the Internet, what it is and how it works. She was honest and told me that, "If I click this button, this websites loads. If that works I'm fine! If it doesn't I will call you. Don't stop working with IT please, if you get it, we need you badly!" I believe that is a good reason to be accepting towards the current state of affairs. People just don't care. They have more important is…
I can't respond directly to kissorgy because of shadow ban I guess. Anyway, yes the author says we are worse today, but keep in mind that we "just" connected a few billion devices. It will take a massive effort to get that fixed properly and keep all up to date security wise. Nevermind that goverments wants to ban security in some places.
Yes exactly this. Information technology has improved at a totally crazy rate, and I think it's unrealistic to expect safety and sanity to keep pace, The internet has only been around for 30 odd years, and getting all this right takes time. To examine another technology, the automobile was invented in 1885, seat belts were invented more than 60 years later, and it was another decade or so until they were made mandatory for new cars (in the US at least).
Re: I'm not burned out, I'm pissed off
#256Earlier quoted context omitted.
No, actually I had somehow never heard of Hyper-V before today (or maybe I had but for some reason it didn't click it was software I could make VMs with). Great suggestion, I'll look into it.
Definitely give Hyper-V a shot. I've been using it at home and work since Windows 8. I had a lot of issues with VirtualBox and networking (I could never SSH into a VM from the host working, for example). In Hyper-V, all you need to do is setup a virtual switch and the host and VM can talk to each other just fine. Hyper-V just works. I've got Linux and Windows VMs and have never had a problem with either (as far as vi…
Re: I'm not burned out, I'm pissed off
#257Earlier quoted context omitted.
I don't understand what "accept" is meant to mean here. If we accept that everything sucks, the only thing left to do is leave the field, since it will always suck no matter what we do. If we try to make it better, then we're not accepting that it sucks. I think there is a better way to phrase what you mean.
You kind of need to accept that it sucks for you to want to make it better. If you thought it was already perfect there would be no reason to.
Re: I'm not burned out, I'm pissed off
#258Earlier quoted context omitted.
I don't understand what "accept" is meant to mean here. If we accept that everything sucks, the only thing left to do is leave the field, since it will always suck no matter what we do. If we try to make it better, then we're not accepting that it sucks. I think there is a better way to phrase what you mean.
You kind of need to accept that it sucks for you to want to make it better. If you thought it was already perfect there would be no reason to.
Re: I'm not burned out, I'm pissed off
#259Earlier quoted context omitted.
> I get the impression that they're continuously discovering new and exciting ways that individual facets of individual pieces of software (and the processes around them) suck As a software engineer, I think this is my experience at every job I've had around systems in general.
As a person sometimes overly distracted by grammar, I would like to thank you for using the "As a [description of subject], [subject] [rest of sentence]" construction correctly. Getting this wrong, which is called a "dangling modifier" error, is common. Examples from today's front-page HN discussions: As a new (1 year) coder starting out at 39 years old, this sounds very similar to the path I envision for myself. As…
Re: I'm not burned out, I'm pissed off
#260I'm a recovering security guy. When I listen to security people rant, I can see their points and it's a bit of fun, I like a good rant. But I get the impression that they're continuously discovering new and exciting ways that individual facets of individual pieces of software (and the processes around them) suck. All without ever accepting that the entirety of the software ecosystem sucks (and that they're rarely mov…
I hate when I see people throwing in the towel like this. As a two developer company with four separate products doing nearly $500k in ARR collectively, Kumu [1] is a living example that it doesn’t have to be this way. We rely heavily on bash, docker and cloudformation. We only use Ubuntu LTS and we lag a release behind so there are plenty of tutorials available when it comes time to upgrade. After experimenting with…
I can look at the product I develop and rattle off an impressive list of capabilities, talk about how well it is designed, say why it's the best product for the job on the market and talk about successes in the field. But I can also look at it and see a laundry list of design flaws, architectural limitations and unrealized enhancements that may never get time on the schedule.
The second side of the fence exists, and security people inherently spend a lot of time there. Spend enough time there and you see how the system that is the sum of all software is a mess. I'm not even saying it's a bad thing, just that it's the inescapable reality.
Your architecture is like swimming in a school of fish. By moving with the group you benefit from the successes of the group. Ubuntu, docker, typescript and delivering your product as webapp brings a lot of benefits in featureset, maintenance and training that come at a reduced cost. For the same reasons I also prefer to use as much popular off-the-shelf tooling as possible and stick to familiar designs wherever possible.
You're probably doing better than most. But even with all that benefit, the components of your system are fraught with defects and limitations that in a perfect world would already be solved problems. Both in the stack you use and your own software. And you make it work despite that. Great. That's not my point.