jspaetzel

Could use a better title on this, it's misleading.

The worst part of all of this is that the CDC didn't already have this type of tool in place, years ago, before a pandemic even hit. This is the type of basic thing they should have already in place without any new spending.

It doesn't even need to sit around unused. They should be using it every year for flu shot distribution or coordinating other types of vaccines which are normally in abundant supply.

Ongoing support isn't the issue here, this is basically a greenfield project with nothing hairy to get in the way.

PHP developers have been very successfully using Composer for many years. It's actually quite nice having the package management decoupled from the language, there's fewer chances for breaking things between upgrades which helps slightly with long term support.

Congrats on getting a package manager for Go!

JavaFX might turn out to be a winner but it's still partly proprietary and is still transitioning from Oracle to the OpenJDK community. There's good reasons for it having little adoption.

This is such a solid take. I'd extend it to say that sometimes technical debt appears to be so when really you don't have a complete understanding of the problem. It may help to spend more time learning the problem domain. Maybe refactoring is part of how you learn, however it's arguably the most dangerous way since you risk breaking things without understanding.

How'd this get voted so many points? RTFM and use a more appropriate datatype.

More context is helpful here. "We take an opinionated stance that every module should be a crate, as opposed to generating Rust files 1:1 with proto files."

These issues exist for mail in voting as well. The main difference is how well the average Joe understands computers vs mail. There could be a secure opt-in system for online voting. Heck they could mail out the ballot and let you submit it online.

The difference between Apple and Google in this instance is a matter of transparency and predatory actions.

I draw a parallel between refactoring and code ownership. Once I've worked in an area of code for a while (several sprints) then I probably know enough to try refactoring. Longer time working on it == more ability to refactor.

The idea of what is correct (to you and to others) and what needs refactoring changes over time, even the product changes. Sometimes it can be beneficial to wait a while and see if you still feel the same way after a few weeks.

I've never had issues with this, what sort of maddening package management are you doing? Are you just talking about installs that's only an occasional hit anyways...?

They're discoverable in the way that documentation is discoverable.

Versions should appear when you have multiple versions, not a default behavior.

This is silly. It's just another contributing factor of total compensation and cost of living.

This is such a dangerous precedent. This type of call out will only discourage the release of source code making legitimate peer review more difficult.

Was the last android version you used released on a 3rd party device in 2012? Because that's what you're describing.

Square peg, round hole.

I also use Google keep and google reminders when I need a reminder. Mainly because of the Google calendar integration which is great.

Standard Notes. Simple, encrypted, open source, and has nice consistent apps on every platform.

https://standardnotes.org/

Most people who own domain names and run websites are mainstream non-tech normies.

Well. That's a nice publicity stunt. lets see how they get their investment back. It's nice that this project does some good. https://github.com/handshake-org/hsd/blob/56c83ca7344def512e...

So if I read this right

Creators get: 102mi coins

Sponsors get: 102mi coins

they are airdropping about 952mi coins to users on github to the tune of 4,246 per user.

So they're collecting about 20% of all coins initially dropped. That's slightly more then some. And at the value listed on https://www.namebase.io/ that adds up to some 102,000,000 * $0.44 = $44mi.

Ok, so it's not an ICO exactly, instead they raised VC funds which is expecting a return by selling coins.

I've just spent a few minutes looking through the website, docs, and a little code. And I have no idea how an end user will use these names. Everything polished about it is for trading coins not real world usage. Sounds like every other crypto coin.

First impression: Great another ICO.

Second impression: Not a wildly outlandish idea but im not sure if it's a good idea either. Decentralized and automated registrar with a concept of renewals. Nifty.

I'm not really sure how the economics here work out.. Could I scoop up a few million names early on and then hold them forever? Has that already happened? Could this enable anonymous registration? Would these things make users trust these names more or less?

Pretty good! My CS degree focused most on math, algorithm, data structures, programming, and computer architecture.

The other topics I don't really think of as computer science, more as electives a CS student might take.

Understanding the problem.

Most of the time the users haven't taken enough time to understand their own problems and have trouble articulating them in a way that's meaningful for a product manager or developer. And on the opposite side of that product managers and developers often do not develop sufficient domain experience to understand the problems users are trying to express.

This is why the absolute best software is built by people who are developing for themselves. You know when it's not solving your problem and you fix it because you know nobody else will.

Hahahaha. There's absolutely nothing in the OPs post that suggests they would be a good CTO or dev lead. That's exactly the counter to the question made by OP.

Learning terraform is probably only going to be useful if you are going into operations, joining a team small enough to not have a team dedicated for that, or if you'll occasionally be supporting others who are maintaining infra.

In addition to that... That entire ecosystem is changing rapidly and will probably be completely different in 5 years. (Terraform has only been out for 5 years)

Software engineering can be hard and it can be tedious, either or neither... I think it's what you make of it. That's one of the most entrancing things about it to me. It's one of the few jobs that's truly "choose your own adventure". There's a thousand ways to solve every problem and you get to decide the difficulty at every turn.

Great tool! Made it much easier for me to get started with puppet & vagrant

I don't write code on my smartphone but I do some planning work on it. Basically any editor will do that can sync to a pc, I use a combination of Journey & Google Keep currently.

My workflow is essentially to think through the problems im going to encounter, make lists of everything, define naming for things that have to be thought through. (All these things are easy to do on a phone) So when I go to actually write the code I can just reference my document and essentially only write the logic on a computer.