Geisterschleier

@vaxryy I think it is a good idea most of the time. People use bash because it involves less typing but if you really want a robust script, the limitations of the language soon get in your way. Python is an excellent alternative.

on a real note, is it even a bad idea to just replace most bash scripts with python?

@thdxr Demanding payment is probably too much, however I still think take-home assignments are very inefficent for both sides and completely unnecessary since there are better ways to screen an applicant.

it's so embarrassing when software engineers act like someone is getting unpaid labor out of them "this company interviewed me and made me work on their codebase as a test and didn't hire me!!!" have you ever worked a real job lol there is zero chance some random person contributing code on day 1 is a net positive someone had to find an isolated low priority task for you, answer a bunch of your questions, and then review everything thoroughly you COST them time and money and weren't even worth it

@fxr256 Thanks for having me :)

@Geisterschleier has kindly contributed another blog post. This time, he explains why apathy is such a problem in the software industry and what to do about it. Please take a look: thinkingsideways.net/people/apathy.…

I am honestly shocked by this blog post go.dev/blog/error-syn…. A language that is incapable of addressing the most reported pain point of its users is essentially frozen and limited to security fixes. This will turn Go into a legacy language in no time.

@ChShersh That people in the replies to the quoted tweet actually celebrate Go not doing anything - despite the fact that they could just ignore the hypothetical advanced error handling - shows what is wrong with the Go community. They are more hostile to progress than even the C devs.

Go is a horrible language. But if you pay me $400K/year, I'll write Go for you and promote it in my account.

@badcop_ Not at all, the syntax is completely different and both languages want fundamentally different things.

golang is like they made a compiled python i will not elaborate

@dhh I am not a rails developer but if I were, I would apply to you guys simply because of the great hiring process. It is very refreshing to see a company being this transparant about their process. I wish more companys would follow your example

37signals is hiring a Junior programmer. We're accepting applications until Wednesday, April 23rd at 12:00 PM CST. The salary is $145,849. apply.workable.com/37signals/j/A9…

@fxr256 Very true, I think "Clean Code" will soon be so divisive that developers should be wary of using the term. I have also seen developers describe themselves as "Clean Code Developer" which confused me a lot at the time.

It's quite amusing that the term "clean code" can now mean "code I like" as well as "overengineered code I hate" depending on who uses it.

I encountered two more cases of devs creating new code rules and claming it was #CleanCode. One was using streams rather than if statements (in Java), the other was not using break in a while loop. Neither are featured in the actual "Clean Code" book. What is going on here?

@0xIlyy Don't you have meetings or other interactions with your colleagues? I talk to my colleagues every day even when working from home. And apart from that you could check up on old friends (via call) or pick up a new hobby.

How do you talk to people when you work from home? I’m becoming seriously awkward from no social interactions i need help

@dhh I agree 100%. I have seen so much effort wasted on huge integration tests which are so difficult to get right. Unit tests are great but end-to-end tests are rarely worth the effort. Unfortunately, it is very hard to convince people to stop once they have started working on them.

Some times you just gotta admit defeat. System tests -- the end-to-end variety that drive a headless browser -- just aren't worth the effort. We'll bring back a minimal set for smoke testing, but rarely been happier to see 5,000+ lines of code erased!

@HSVSphere I certainly did not expect a Zig vs Go fight. Talk about different weight classes

ANDREW KELLEY (ZIG CREATOR) on Go: > Go is great if you are an amateur with no taste, like 99% of google employees

Lambdas have a similar problem. One liners are fine but if your lambda needs curly braces, I think a method reference is the better choice. Python wisely limited its lambdas to a single expression which also would have been the better choice for Java

I think Streams are one of the most abused Java features. They are great for certain use-cases but for complex logic regular loops are superior in every way. Unfortunately, some Java developers seem to use Streams for everything without thinking since they are the "new thing"

@code Blue botton (or black button in IntelliJ) for commit, terminal for branching / pushing. I like the pre-commit features like reformatting in IDEs but after experiencing a few bad Git integrations (hi Eclipse), I prefer doing the complex stuff myself.

blue button or terminal?

@KrTirtho @HSVSphere Docker was literally a Python programm first, mate. And Python's machine learning libraries are incredible successful

@HSVSphere All the docker, vite, arch linux's yay package manager etc are terrible right? I don't remember something as successful as docker written in python, rust, zig

Congratulations to the Go programming language on receiving the "WORST PROGRAMMING LANGUAGE OF THE YEAR AWARD" consistently for more than a decade!

@TravisMWhitaker Wispem's tweet sounds like bait considering that Docker was orginally written in Python and Borg (which still powers Google) is also not written in Go. It is true that Kubernetes does a lot to pop up Go (and it is good tool) but it is not as ubiquitous as he seems to think

> Almost every important piece of software from the last 10 years uses Go: - list of the most insufferable slopware ever.

@davefarley77 Most likely overkill

Describe #microservices in 3 words or less...

@simas_ch Yes, that was the consensus in the team. In your example, I also don't see any advantage for AssertJ, it is just longer. And it gets worse for boolean asserts with: Assertions.assertThat(returnedValue).isFalse() instead of Assert.assertFalse(returnedValue)

@Geisterschleier Really? For me, it's quite the opposite. The fluent API helps to improve readability. For example: assertThat(myList).hasSize(1); instead of assert(1, myList.size()); or is it assert(myList.size(), 1);

I always use AssertJ. What about you?