gregors

The highly overused "best practices" marketing term should really be called "most-likely good practice for most but not all situations highly dependent on context".

I think the problem is people want to know "Hey what's the right way to do this?". Turns out IEEE does publish some actual standards[0][1] related to software, but being completely honest I've never actually read it. I'm assuming I'm not in the minority.

[0] https://standards.ieee.org/ieee/29148/5289/

[1] https://standards.ieee.org/ieee/1012/5609/

Could be possible they looked at the sort directory and overlooked the combination test file "sorts_test"?

If you'd like to see a really well done deep dive by the new Golang Tech Lead ( Austin Clements), check this out

GopherCon 2020: Austin Clements - Pardon the Interruption: Loop Preemption in Go 1.14

https://www.youtube.com/watch?v=1I1WmeSjRSw

I'll agree with you if you mean - entirely en masse. I specialize in fixing legacy software systems that have ground to a halt development-wise. Blanket rewrites are almost never a good thing, but partial rewrites are a wonderful tool. Like most things in this industry there unfortunately isn't a hard and fast rule. Everything is extremely context-dependent.

punning for the win!

I truly believe if you were trying to invent the WORST possible way to hire people it would look very close to what they've implemented.

It can be when you're supporting AD authentication on an intranet site. I did a bunch of these for government type web apps. Not the most fun to be sure.

Interesting. Thanks for the clarification.

Figma? I'm curious if this type of behavior is a reflection on the organization's culture in the larger sense. If so, it would explain why the 20 billion dollar acquisition to Adobe fell through.

MONTHS??? Do even elite athletes making millions and millions subject themselves to such foolishness?

You actually get a tax break after $168,600. After that you no longer get taxed for Social Security.

As an immigrant who works in tech, I think the H1-B issue in particular is a bit more nuanced. I think the feeling is that H1-B's are used inappropriately as a tool to leverage salaries lower. I don't actually know the stats on that.

That being said, you do want immigrants working right? That's kinda the entire point.

I'm curious about the security implications and corporate policies about uploading your entire codebase to an LLM where others can access it (indirectly or directly).

Other than that, I'm very interested to see how easily opensource libraries could be converted from ecosystem A to B.

Just recently setup some ebook software on my linux laptop trying not only use Apple for everything these days.

Calibre was the very first thing I tried but it seems like it was going to be a time sink. I can't quantify that precisely maybe because of the design? I didn't seem like I could just get going easily.

Foliate was the next thing I tried and seemed perfect. Easy to start, limited options, good design. It was a lot closer to what I was used to on my mac.

I'm sure Calibre probably does a bunch of things perfectly and I should revisit it, but that's the experience coming from a novice.

I'm a big fan of evidence base scheduling by Joel Spolsky [0].

Story points hold very little value in estimation, the discussion that occurs however, is extremely useful.

[0] https://www.joelonsoftware.com/2007/10/26/evidence-based-sch...

It's a good point but I'm willing to bet there are thousands of devs who are smart and talented enough to land those positions who will absolutely jump at the chance to run their own business instead. There are many devs that can't get a job due to layoffs and schools are still turning out graduates each semester.

The skills they're not good at is exactly where AI (assuming it can of course) will be used. Why only use it for a 10% improvement on a skill you have vs a 100% improvement on a skill you don't have? Or why not both?

Hard economic times (layoffs) typically result in people starting their own projects/businesses. The last major downturn resulted in a mass influx of new startups and ideas. Of course most of them failed, but that's typical I suppose.

Here's the thing that I'm wondering about most.

Anything that current LLM's can do code-wise is overshadowed for me with what they can do product, design, marketing-wise. If LLM's actually break the productivity ceiling why would any developer bother working for anyone other than themself? Having a job and working for someone else just disproportionately improves their wealth while limiting yours.

If this turns out to be the case I'd expect to see unprecedented micro-software shops spring up overnight. Why bother burning yourself out working for a FAANG or F1000 when you could make more and be in control of your own destiny and happiness? The rise of entrepreneurship should follow actual increases of LLM productivity across the board.

Graphql is by far the most painful DX and least productive thing I've seen cargo-culted. Like most things there's a time and place for Graphql but I think it's vastly overused.

For backend services in particular literally anything else is probably a better choice - rest, grpc, soap, a socket. I honestly don't know why more people don't give twirp a shot.

https://github.com/twitchtv/twirp

The problem with your kitchen sink example is that you'd think that they've unclogged 7k kitchen sinks so that they can you give you a great estimate.

If we've built the same software before ....we wouldn't have to build anything we'd just use the previously built software.

Software isn't built like a kitchen but by exploring an infinite list of design choices and then choosing one way and implementing it ..hopefully without impacting existing architecture. And it seldom stays static - the name of the game is constant change and then add group dynamics to that.

A better example is to call a plumber and ask how much would it be to add a "rainbow spout to the horse-drawn wheelie-do" oh and there will be several other teams of plumbers there as well. I bet you get a few questions.

Completely agree. This seems to me like common sense reasoning to me so I'm curious how the best companies in the world just seem to phone it in with leetcode.

As someone who interviews and hires engineers I'm not even remotely convinced live code exercises lead to better hiring than any other signal such as a CS degree. I remember when the the coding horror fizz buzz article came out and honestly things have just gotten worse since then.

I always like to link the talk where the speaker mentions google hiring committee refused to hire themselves [0]. I suggest that this outcome isn't rare.

[0] https://youtu.be/r8RxkpUvxK0?t=531

I'm extremely interested in progress on this front. I'm a person who would definitely purchase an X Elite to run linux ....but only if I could get it installed with minimal effort.

If this were actually true, the real under performers would be the executive team which should be replaced immediately.

hmmm, yes you are correct. I thought they used to offer more for free but maybe my memory is off. Apologies.

You are also right about that the Phoenix book needs an update, they changed A LOT with the way they structure code in the last release. Which, you don't have to use btw, you can still use the older methods. The major differences are here https://elixircasts.io/upgrading-to-phoenix-1.7 which I can honestly understand the pain a new developer feels when the books are out of date.

I'd still consider going through an older book, you'll learn 90-95% of the same thing.

At a lot of places the entire "sprint" culture is designed to extract maximum output from the dev team with nothing but short term goals. They know it's non-sustainable and really don't care.

The toxic culture of dev productivity is the de-facto workplace culture. They're happy to replace their burned out workers every 2 years. They don't really understand the impact of training new hires up, just continue to hit those KPI or OKRs.

Having on-boarded quite a few jr developers with no previous experience with Elixir (and have purchased the prag studio course for most of them) I've heard that many of them also really enjoyed

https://joyofelixir.com/

and

https://elixirschool.com/en/lessons/basics/basics/

And while I haven't watched it - there's a free code camp tutorial - https://www.youtube.com/watch?v=IiIgm_yaoOA

From looking around there seems to be a host of free videos on YT as well as many books on elixir/phoenix. Also, I believe prag studio gives away 1/2 of that initial course for free, probably enough to get you started.

I think the term is Mirrortocracy

https://carlos.bueno.org/2014/06/mirrortocracy.html

It really depends on what you're trying to do specifically. Maybe take a look at Elixir/Phoenix it has ok performance while still allowing fast dev productivity. A nice feature is that if you run into a section that needs higher performance you can quite easily write a small section of it in Rust or Zig.

* https://elixir-lang.org/blog/2021/07/29/bootstraping-a-multi...

* https://github.com/njwest/Awesome-Elixir-Gaming

* https://www.erlang-factory.com/upload/presentations/395/Erla...

* Erlang Factory SF 2015 - Jamie Winsor -Building And Releasing A Massively Multiplayer Online Game https://www.youtube.com/watch?v=_i6n-eWiVn4&t=1131s

* Petri Kero | Building a Scalable, Distributed Backend for Mobile Games - https://www.youtube.com/watch?v=nCSO8yeR0c4

All that being said, Go and Rust are hands down faster and there's no denying that.

Whoa, they did get rid of it. Not surprising in the least, but they definitely did it with a minimum of fanfare. When Heroku got rid of their free plans at least they were upfront and released a blog post about it. Maybe they did and I just didn't notice.

K8s was absolutely built using exciting tech....Golang was hot off the presses. The brand new hotness. Google's internal Borg was C++, so the boring choice was C++ which wasn't chosen. Also they were google employees, which also adds a bit of bias in selection I would imagine.