avg_dev

I once said - and still maintain - that all devs need a life-long lesson in empathy. For our users and our library consumers and so on.

It will be impossible to fix every conceivable issue and sometimes we will have to deprecate or break backward compatibility or features or whatever. But if maybe some more effort to understand and respect our users was made as a matter of course, then when we are users we will be more inclined to give the benefit of the doubt to the developer who created the thing.

Also the post made me laugh.

I had a number of burned CDs flake out on me over the years.

And that has a link to a paper: https://www.lse.ac.uk/News/News-Assets/PDFs/2021/Sentience-i...

Edit: but, you may be right; I cannot find any other source for this NZ news.

however,

  irb(main):001:0> value = false or true
  => true
  irb(main):002:0> value
  => false
  irb(main):003:0> value = false || true
  => true
  irb(main):004:0> value
  => true
  irb(main):005:0> 

Just editing to add this reference: https://rubystyle.guide/#and-or-flow

i remember some years ago reflecting back on some software project that had gone well. in my head, it was a beautiful finished object that i'd created using the tools and frameworks available to me. it was perfect and flawless.

then i went back and read the code and saw so many TODOs and things that i would have accomplished had i only had more time. and i never did get a chance to finish those TODOs, but the project launched successfully and generated a lot of revenue.

However, that was quite some time ago. Does anyone have any more recent opinions? How is it to work on a large modern Ruby or Rails codebase? Also, I saw some type annotations examples a few years back and thought they looked pretty ugly - is that how I would feel after some months using them, too?

This is from September of last year but it definitely changed my mind about this stuff.

> In fact, however, the Wikimedia Foundation is richer than ever. Its assets and reserves (including an Endowment with the Tides Foundation now holding well over $100 million) have increased fivefold since 2015, and stood at an estimated $400 million at the end of March 2022.

FTA:

> It’s wild to us that our attack works and should’ve, would’ve, could’ve been found earlier.

I'm not actually familiar with the issues that VSCode has but I seem to recall some key component was not OSS, but I forget the details there and maybe it has changed. I know it has telemetry and such, but AFAICT that can be disabled by some settings. (I personally use vscode for my own work and disable telemetry and don't use any code assistant platforms, and I would like to know if there is a problem with what I'm doing)

1. Since you say it is an open market with alternatives, I don’t see why you seem to take issue with the blog post author taking one of the alternatives.

2. I thought the author did have some issues with the product. Like lack of persistence of uploaded files, price going up, and the support for the author’s current main language, Lisp, being not as good as for Python.

I would assume that if you measure enough things and code enough you may start to get a feel for what is going to be expensive and what is not. And then - as before - you can continue to measure and iterate.

(Also, I think you said "first people" when you meant "first point")

Insert No Coins: https://www.youtube.com/watch?v=N5CNlMGcARA

I did file a support ticket once and the support person clearly didn’t understand or read my request and instead sent back some pre-formulated response to another query. That was kind of annoying. But other than that I’m quite happy to pay the few bucks a year for the service.