RT @skdh: I find this attitude, that computers can never become "truly" intelligent (whatever that means), utterly bizarre. The human brain…

@vlad_mihalcea If you're doing 2 right, you'll likely not use Spring nor Hibernate, so point 3 will likely be redundant.

@fjzeit Let's be honest, most code written, regardless of the age group, is mostly a cobbled together mess. Some exceptions apply. Although you should stay professional at all times, who here didn't at one point wanted to scream at the code or even co-workers. :)

@ChShersh I do think AI will _eventually_ replace developers. I mean just think rationally. What would be the roadblock in your opinion? Is there anything physical we can't replicate with electronics? Is there something in the learning process we can't replicate? What is it?

@guizmaii Make it correct, it'll work.

AI will eventually replace developers. There's just no argument against that. I personally see that as a low bar though. Humans are hilariously bad at complex problem solving. Just imagine what we could have, if "software" is essentially zero cost and immediate.

@jjenkov Objects are not bags of data. Users of objects should have no clue what's inside, let alone know what is needed for the object to "revive" itself, potentially in a different JVM.

Documentation in an internal project is basically saying: I didn't know how to solve this properly, so this is what I did, you figure it out!

@webdevcody Pro tip: 5 minutes _min_. A lot of problems "solve themselves" if you just wait a bit :)

Oh no, I tried to define a new project in our repo and it doesn't work. I'm in sbt hell again.

@guizmaii Gradle shouldn't be the benchmark. It's almost as bad as sbt. In Java projects "mvn install" works _every_ time. In Gradle and sbt, you don't even know what command you're supposed to use. If you're lucky, "compile" may work, but even that fails surprisingly often.

@Krever01 I'm sure you can make it work and make it simple. I've never worked on a greenfield scala project though. The sbt build was always already there and was usually quite complicated and very custom. I don't even know how to build the project initially.

"No code" is not automatically better. If you still have similar complexity of the process itself, but now with less control, less automation, less testing, you're potentially much worse off.

RT @MartinVysny: Saw a Java presentation: cool, fast paced, lots of stuff done, magic stitched with annotations. Total opposite of building…

@ryxcommar I did Java Enterprise for 20 years, using timestamps as booleans does not even register :)

@ChShersh Having "utils" is not the problem, if it contains proper implementations or abstractions. The problem is that they usually contain static methods, hanging functions, things somebody didn't understand in a library so re-implemented it poorly, partly business logic code, etc..

RT @MartinVysny: In programming, simple != easy For example, it's easy to add a Transactional annotation to a Spring app, but the underlyi…

@WholeMarsBlog My grandma used to ask that when I wouldn't eat the vegetables.

@MarkusWinand I remember the SQL-only times. It was not good. NoSQL says: Hey, it's ok to not use a relational model if you don't have to. In fact, you'll probably be better off if you don't. Just like "agile" said: It's ok to not plan for a year if you don't have to. And you probably don't.