In other news, this week I've found a 16,600+ LOC #Java file in the "main" monolith which performs the bulk of business logic for the main web (interconnected to other monoliths and -from what I've been told- even way huger PL/SQL scripts with tens of thousands LOC). And this is just one file, of thousands.The file has no comments, is not documented anywhere, the variable names are far from informative, and there's at least one function with way more 1000 LOC. Now go and debug this. XD
@array at least it is written in #java so your IDE ( #intellij of course!) will have some clues of what it deals with... Unless you've only Maps of Maps of Strings named "data" :-p
@array you definitely should give a try to IntelliJ, I'm not used to promote proprietary software but I make an exception for that one. I would say the licence cost is covered in about one or 2 months by productivity gains, and it's nice to use :blobcatheart:
@array fair enough, I haven't tried Eclipse for years now... On the other hand, any new comers to our team have the choice for their IDE (and OS), at one time or another they do try IntelliJ (and Linux), and ...never come back to Eclipse (and who's using Windows for development nowadays?)
Don't get me wrong, I do think Eclipse is a very good software, and the Eclipse foundation is important for the Java ecosystem, but there is no comparison.
We're heroes that fight legacy code, need best weapons
@dada attention de ne pas remplacer une idée reçue simpliste par un autre argument statistique sortit de tout contexte et donc fragile. Je trouve que l'article suivant de la sécurité routière apporte la nuance nécessaire https://www.securite-routiere-az.fr/idees-recues/femme-au-volant-danger-au-tournant/
En gros on ne compare pas du tout la même population en termes d'usage, de proportions et de conditions d'utilisation.
@Crell 10 years ago, I felt the same, until I realised that I just lacked XP on these very powerful technologies. Sadly, most projects are devastated by developers that don't use them correctly, because they just "hate" it, so just don't learn it.
What I hate today: thousands of lines of SQL code, some dynamically built with string fragments (even to an embryon of a badly designed ORM..) that is so difficult to maintain as it mostly fails at runtime #java#hibernate#jpa
@Crell there is so much more than 1:1 mapping (that saves you tons of SQL writing and maintenance)
There is cache level 1 and 2, there is entity graphs, complex but powerful Criteria API allowing you to combine predicates specifications, automatic batching...
It really worth giving it a try, but with at least one member of the team that does master the subject as much as you seem to master SQL
The ETA just for setting up the development environment in $newJob is no less than 2 weeks, but it's no problem if it's two months. I know many of you are used to this kind of scale in dev work places, but I'm kind of terrified (that, plus the ~300 person IT workforce all in the same place, the git repo with more than 100 repos -and this is, apparently, just the tip of the iceberg-), the commits in 1000+ LOC files made in the past century... This will be fun, fortunately. And sadly. :P
@array@fedops@tulpa after 20 years of #java coding, having worked with others ( C, C++, PHP, js, Rust, python), well I think Java is most of the time the Silver Bullet for any serious, long lasting, industry grade projects, and recent versions get it closer :-)
Des internautes arrêtés par les forces de police pour avoir cherché certains mots sur Google.
Ça devient complètement dingue et dystopique.
(Et c'est donc aussi une très bonne raison pour utiliser d'autres moteurs de recherche que Google.) https://sebsauvage.net/links/?MaaBFw
@sebsauvage j'utilise kagi.com avec bonheur depuis quelques mois maintenant. DDG et autres Qwant n'ont jamais été à la hauteur surtout concernant les recherches pro. Je trouve que #Kagi est souvent plus pertinent. Et je trouve normal de payer pour un service aussi central dans la vie numérique.
@KToche@sebsauvage je ne connais pas, mais disons que par défaut une société privée qui fournit un service "gratuit" sans exposer clairement son modèle économique, il y a de bonnes chances qu'il ne soit pas en faveur de "l'utilisateur" (le produit ?), donc c'est non.
Il n'y a pas ce problème avec #Kagi