@captainjaneway@lemmy.world avatar

captainjaneway

@[email protected]

This profile is from a federated server and may be incomplete. View on remote instance

captainjaneway , to Technology in After 16 years, Ecobee is shutting down support for the original smart thermostat
@captainjaneway@lemmy.world avatar

Yeah the majority do it and I think it's bad.

captainjaneway , to Technology in After 16 years, Ecobee is shutting down support for the original smart thermostat
@captainjaneway@lemmy.world avatar

Thermostats are easy to change out. So this isn't a huge deal. But I don't love the idea that tech isn't built to be self-hosted or maintained in any meaningful way. If you're not shipping an open source version of your software when you close up, you're an asshole.

Yeah, self hosting isn't for most lay people if it's just a GitHub repo. But GitHub repos quickly become adopted by nerds like me who build tooling around it that eventually let lay people self host software with the click of a button.

captainjaneway , to Android in Could a uniform interface (like the command line) ever exist for smartphones? What could it look like?
@captainjaneway@lemmy.world avatar

Great examples are already in the thread, but generally speaking the answer should be "no". Smart phones are just slow at typing. In the case of a smart phone, hitting a button is far faster than typing a command. Not to mention our devices aren't really being used for file management, tooling, complex work, etc. So it doesn't even make sense to have a command line unless you're a huge unix fan or if you are doing something quite niche. And in that case, I recommend just connecting via adb.

captainjaneway , to Programmer Humor in What I want to become Vs What I do
@captainjaneway@lemmy.world avatar

Software engineering is just what any "engineering" field would be if they didn't have standards. We have some geniuses and we have some idiots.

Mechanical engineers, civil engineers, electrical engineers, etc. are often forced to adhere to some sort of standard. It means something to say "I'm a civil engineer" (in most developed nations). You are genuinely liable in some instances for your work. You have to adhere to codes and policies and formats.

Software engineering is the wild west right now. No rules. No standards. And in most industries we may never need a standard because software rarely kills.

However, software is becoming increasingly important in our daily lives. There will likely come a day wherein similar standards take precedence and the name "software engineer" is only allowed to those who adhere to those standards and have the proper certs/licenses. I believe Canada already does this.

Software engineers would be responsible for critical software, e.g: ensuring phones connecting to an emergency operator don't fail, building pacemakers, securing medical records, etc. I know some of these tasks already have "experts" behind them. But I don't think software has any licensing/governing.

Directly opposed to "engineering" would be the grunt work which I do.

  • All
  • Subscribed
  • Moderated
  • Favorites
  • kbinchat
  • All magazines