Lysergid

joined 1 year ago
[–] Lysergid@lemmy.ml 7 points 2 days ago

What is crazy is that Mac version is more stable than windows in my experience. Still shit, though

[–] Lysergid@lemmy.ml 0 points 2 days ago

I think you forgot to pollyfill your console.log and now you have some error in some script in some callback

[–] Lysergid@lemmy.ml 1 points 2 days ago (1 children)

It’s not corporate world, it’s web. Spring de facto is the only modern way to build web services and integrations in Java and Spring comes with DI because it’s the way to build efficient extendable framework.

[–] Lysergid@lemmy.ml 5 points 2 days ago (1 children)

Here we go, even drugs are low quality now

[–] Lysergid@lemmy.ml 28 points 3 days ago* (last edited 3 days ago) (2 children)

95% exaggeration. Here is reality:

  • yeah you need main class coz it’s OO-language. Though, not required anymore, which should’ve been done once Java got scrip language capabilities (jshell) back in JDK 9. But as of today not required anymore
  • imports exist in most if not all languages. Gotta be insane writing them manually in 2010 let alone 2024
  • installing Java runtime (JRE) is as simple as installing any app. Though for installing JDK you need 5 mins for setting PATH. Think about JDK as like TSC or Webpack and JRE as a Browser. I’d argue installing and configuring JDK is simpler than TSC or Webpack
  • Unless you doing some non-trivial multi-threading your stack trace will tell you exactly where is your NPE. You gotta be as blind as my teammates to spend more than 1 minutes to find where it is coz it literally tells you file and line numer where Exception occurred
  • I mean, yeah if you use IDE from 2000 it will look like it. IntelliJ looks modern, though I don’t like the fact latest versions look like VSCode
  • I hardly reach 3G of deps from all 10 projects I have on my workstation.
  • IDK what anon means by ecosystem here, Java ecosystem is quite standard across the board. JDK(std lib), Maven/Gradle(deps, build, publishing), Spring Framework (all sorts of blueprints and solutions to standard app level problems), Hibernate/JPA (ORM), JUnit+Mockito (testing). These are tools and libs used in 90% of projects I worked on. Of course there will be more depending on project needs. Layers? It’s not like language imposes any layers whatsoever. It’s just common practice to have 3-4 layers and some glue in-between.
  • don’t do GUI in Java it sucks and will suck until Java gets string interpolation. Hopefully soon
  • concurrency is actually the only thing which is really bloated in Java. Which will change with next LTS version if I remember correctly. And it’s not that hard if you actually read the f manual and not just “try and hope”. Again it will become much more efficient and easier to follow soon. As of now - yeah, not trivial. But people mostly prematurely optimize, so karma
  • Java is kinda have 20 ways to do same thing but actually no. Java built with idea of providing simple building blocks. Then it provides more specific API built on top of those building blocks. It allows to have API which solves typical problems and provides capability to solve custom problems with those building blocks. People often confuse this as many ways to do one thing but it’s like saying “I can have byte array why I need string data type”. Those are different levels of abstraction

Edit: typos

[–] Lysergid@lemmy.ml 16 points 3 days ago (1 children)

I guess naming it NullReferenceException will revolutionize industry

[–] Lysergid@lemmy.ml 14 points 1 week ago (1 children)

I’d leave my job if Musk would become CEO at my job.

[–] Lysergid@lemmy.ml 3 points 1 week ago

If administration does not change agency’s policy in the the way it contradicts your moral I’d say it’s ok

[–] Lysergid@lemmy.ml -1 points 1 week ago* (last edited 1 week ago) (1 children)

Everyone screaming about democracy just died. In fact it was always dead. Electoral college system basically disregards voter who does not vote for winning party. It’s a system where you have only two choices, thus less competition, thus lower quality of candidates. Then everyone is like “is this best US can do?”. Let alone gerrymandering. People should be rioting, not because Trump won, but because system is not democratic.

[–] Lysergid@lemmy.ml 4 points 2 weeks ago* (last edited 2 weeks ago)

No, that means you falling into author’s bait where they misuse term “delete”. Refactoring is not equal to deleting. One can be result of another. But the truth is that extendable code needs to be modular to be extendable. And modular code is easy to refactor. Author couldn’t not name it “Write code that is easy to refactor, not easy to extend” coz it’s even more dumb

[–] Lysergid@lemmy.ml -2 points 2 weeks ago

No, title only

[–] Lysergid@lemmy.ml 5 points 2 weeks ago

See no problem as long as person genuinely likes branding, not because “flex”. For example i have Adidas Original hoodie and I like it has huge logo coz it’s iconic design of hoodie from golden era of hip-hip and break dance. I would never wear same from other brand or even “three stripes” logo from the same brand.

10
submitted 4 months ago* (last edited 4 months ago) by Lysergid@lemmy.ml to c/programming@beehaw.org
 

Hello my fellow, lemons? I have this problem in my current project I’m out of clue how to approach it. Maybe someone had similar experience and can give an advice.

Our requirements captured in JIRA. Throughout years we accumulated thousands of user stories. Say suppose following naive requirements team knows about:

  • Day 1: create home page
  • Day 20: create profile page
  • Day 50: add green footer to all pages
  • Day 100: create admin page Day 150: change footer color to blue

Now I’m doing refactoring (yes, I know, this is the actual problem) on day 400 and noticed that footer on profile page having green footer. Because requirements are just set of individual statements not consolidated with all history of system no one on the team knows why is that, is it bug or requirement did change on day 300 but we cant find it now.

When I worked in Waterfall we had BRD and FRD stating current actual desired state of system which was “reduced” from individual requirements which were coming in throughout project life. When in doubt devs can check FRD and not only know how system expected to behave but also which are other parts of the system that will be affected. How is it in Agile? To my understanding FRD is not a thing in Agile. Do I need to scan through hundreds of tickets and hope I didn’t miss anything every time i’m doing any non-trivial change to system?

 
view more: next ›