Hacker News new | past | comments | ask | show | jobs | submit | blacktriangle's comments login

I love how you both acknowledge that health care workers quitting over forced vaccination is an issue while immediately dismissing their actual experience of having worked through both pre and post vaccine covid world and first hand seeing the impact of mass vacination.

If enough health care workers are willing to walk away from their jobs rather than take a vaccine, maybe you should take their observations seriously?


> If enough health care workers are willing to walk away from their jobs rather than take a vaccine, maybe you should take their observations seriously?

If you value their opinions in that way, you should get the vaccine.

https://www.ama-assn.org/press-center/press-releases/ama-sur...

"The American Medical Association (AMA) today released a new survey (PDF) among practicing physicians that shows more than 96 percent of surveyed U.S. physicians have been fully vaccinated for COVID-19, with no significant difference in vaccination rates across regions. Of the physicians who are not yet vaccinated, an additional 45 percent do plan to get vaccinated."


Because the timing IS information. Why was a piece of information stated up front, or last, or in the fine print, or released to the public on friday at 5pm, etc.

We're not evaluating an arbitrary collection of facts, we're evaluating a flow (ie time varient) of information from a source of unknown trusthworthyness and as such we are looking for more information than just taking everything stated at face value.


It doesn't take a rocket science to figure out a cokehead who was kicked out of the navy who speaks 0 Russian or Ukranian, and has 0 experience in the energy industry but whose dad is a prominant politician getting millions is corruption.

I think the bigger issue is how so many people refuse to see this.

And for you people who want to write this off as partisan, Romney was in on it too by a similar line of reasoning.


Also programmers. Walmart is a massive Clojure shop, puts out some very good open source libs, and very much views their IT department as a competitive advantage and not a cost center.


I would argue that any function that branches on argument type is straight up doing dynamic typing wrong. Well branching may not be the right word. Something resembling pattern maching is fine, but like you say having a function that takes a string for lookup OR the object is just a disaster, particularly when you start stacking function calls. Dynamic types should closer resemble things that all share an interface, not totally different representations of that data based on the shape of your code.

Javascript is by far the worst offender here with its ignoring extra arguments. Javascript functions that totally change effective type signatures based on number of args are the devil's work.

I'd argue that if the types that a function accepts are not easily defineable than you're doing dynamic typing wrong.


That's some Rails stupidity there, not a dynamic language problem. Autoloading symbols by name is straight up dumb.

As for greppable though...then you may as well be using a static language. The point of a dynamic language is to be dynamic, ie you can do those things at runtime.


The point of a dynamic language is to be dynamic, ie you can do those things at runtime.

With Rails you have the option of pry-rails, and you can get a list of descendants of important parent classes like ActiveRecord with this: https://apidock.com/rails/Class/descendants

With the combination of vim, rspec, pry, fzf, and ripgrep, it's possible to become quite comfortable refactoring pure Ruby and Ruby+Rails code. But it does take some time to learn how to navigate the Rails runtime code generation magic. The more magic the code, the more you might have to use a debugger to break on method definition, but Ruby's dynamicism lets you do that.

On the topic of frameworks with a lot of magic, having used both Rails and Spring Boot (with Java and Kotlin), I'll take Rails any day. It was way easier to introspect Rails codegen magic with Pry, than Spring's codegen magic with IntelliJ. With Spring Boot, even with Kotlin, we had the burden of semi-manual typing, but lost a lot of the benefits because a lot of DB interaction and API payload handling was still only runtime checked.


I'm not a golang fan, but one thing I've noticed about go is that it is possibly the most approachable yet real programming language for beginners I've ever seen. I think this is part of why go is doing so well in the devops space. Sys admins who are not really well versed in programming but know enough to write some scripts here and there are able to bring their domain specific knowledge of admin tasks and write code to contribute.


A bit paradoxically, being a generalist is a particular strength, and as the article points out one of the things you can do to do better at work is work in areas that best utilize your strengths. Ergo, if you're the kind of person who is good at quickly superficially learning a wide variety of topics, solo entrepenureship is possibly the best place for you.


This makes perfect sense. Beyond just writing software and architecting systems, I find the most challenging parts (and rewarding) learning how to build a sales funnel, communicating expectations and deadlines with customers, etc the most rewarding. And as you mentioned, solo entrepreneurship might possibly be the best place to exercise these wide array of skills.


Honestly you touch one one of the reasons I love Heroku so much. I've never seen a service that manages to do so much of the heavy lifting for me, but at the same time be 0 lock-in. I've helped move 2 apps off Heroku once they hit a point where they needed a bit more operational flexibility and there was zero work to disentangle them from Heroku operationally. Try that with AWS, GCE, or anything else.


Get a CD player. It's what I did when I got fed up with Spotify.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: