It had basic geolocation feature though so you could mostly see where you were on a map which was still very useful compared to flip phones

Cellular triangulation worked really well on the classic iPhone - if you were in a very crowded place. In more rural areas, you could be off by many kilometers. I’m not sure if they had Wi-Fi SSID location back then.

A lot of buildings down have floors under floor #1 so its always above you

Companies just want a clean break. In cases where they really need you to do a hand off, you will get a transition period. I've had that happen to me, and it's a weird feeling. I don't think its great for productivity or morale, and is more common when you are shutting an entire division down.

The difference is sort of meaningless. What matters is if you are getting severance or unemployment, and if you can get a recommendation. If they are going to fire you for invidual performance, youd think they would put you on a pip, but some companies will just wait and lay you off.

But the two can be similar in that if you are valuable you won't get fired or laid off, unless the company is in serious trouble.

Sometimes you are just on the wrong project. It is good to be generally aware of your projects value if you want to keep your job.

Cucumber, IMO, died like 8+ years ago and never really made sense. It was useful for a team to define requirements and then see the progress to implementing them, but Gherkin was a sticking point and integration tests are hard to get/keep working, esp with javascript apps that are now so popular. The fact that someone would pay a OSS maintainer up til now seems like a crazy waste of money.

yep. An awkward terrible joke to cover up whatever she was doing - social media, messaging, or looking up her employer

"Come on dude, were you on TikTok again?!"

"No! No! It was porn I swear!"

Sounds similar to how do not call lists are handled

This is super common, (and the mark of a bad programmer if you program the same in every language). What's funny is the opposite - people who get so into ruby that everything they write is cute and overthought - is actually worse.

Ruby is so powerful but simplicity is the best if other people are going to read and maintain your code. Go is great for this.

    Ruby is so powerful but simplicity is the best if 
    other people are going to read and maintain your code.

Amen. Keep it simple for a large shared Ruby application, such as a Rails app.

More advanced Ruby (writing your own operators/iterators/whatever, metaprogramming, extending the language itself, whatever) is best reserved for Ruby frameworks, not applications.

golang https://github.com/Masterminds/squirrel

Constructing sql by concat strings has a few issues, its repetitive and hard to assemble certain queries conditionally, and at least in golang its easy to write code vulnerable to sql injection and you can avoid that by using types

I never use string concat to generate SQL in Go - isn’t it normal to use placeholders? ie,

    db.QueryRow(“select $1”, n)

Looking at squirrel, I really don’t see how this

    sql, args, err := sq.Insert("users").Columns("name", "age").
    Values("moe", 13).Values("larry", sq.Expr("? + 5", 12)).
    ToSql()

Is better than this

    sql == "INSERT INTO users (name,age) VALUES (?,?),(?,? + 5)"

That said, I will happily agree that that SQL statement composition is not the same as an ORM, and I can see the benefit of Squirrel for those rare times you do need to conditionally build SQL statements.

Bitbucket wikis basically do this.

Expensive wines are expensive because they are rare, not because they are better. If you value your money its not for you. The same is not true of beer, I can't really say with liquor