Lysergid

joined 2 years ago
[–] [email protected] 3 points 9 hours ago (3 children)

It takes cheap labor. EU has tech. If I’m not mistaken Netherlands one of few who has capabilities to produce machines for photolithography. Question is how to make it competitive.

[–] [email protected] 5 points 3 days ago

Idk which market you are in. In mine no one cares about your project. Most of companies don’t do innovation. Most of real life projects I saw just moves data around. When I interview people all I care about is knowledge of tech stack and what I call “analytical thinking”.

[–] [email protected] 26 points 1 week ago (3 children)

Omg this is so true, I had 3 engineers which supposed to work on component. It took me almost a day to explain context, requirements and how work is split. Two of them were busy with other work. One did their part. After reviewing I realized they still lack understanding and need to rework what was done.I made an experiment and implemented whole thing myself. Since coordination part was eliminated it took me 3 times less than initially estimated.

[–] [email protected] 5 points 1 week ago

I was on vacation in Portugal and twisted my ankle badly. It was in remote area, so hospital was not the best. But experience was ok. It was in a town with around 25k people. 2 hours of waiting. x-ray and doctor visit costed me 55 euros.

In my home country I pay 20 euros per month for private health insurance. This includes basic dental insurance. I guess, most expensive procedure I had is MRI of brain, but it was also fully covered so I’m not sure what was the price. There is free healthcare but I only had to resort to it once

[–] [email protected] 1 points 1 week ago

Don’t get me wrong, I’d always choose html over js if I could. My problem with css, and web in general, that it’s too fragmented. It’s like those people who are designing css, html, js and browsers didn’t speak to each other whatsoever. So now there is entire industry of js frameworks to glue all shit together. Like, look at the WebComponents. Which supposed to be native, out of the box replacement. So much effort and they still cannot compete, in some cases they simply do not provide basic features needed to build complex UIs. Next time I can choose stack I’ll probably just go with htmx

[–] [email protected] 9 points 1 week ago (8 children)

Never heard of electric tanks or jets

[–] [email protected] 4 points 1 week ago

I feel like I saw this picture in a book when I was a child. This gives weird vibes

[–] [email protected] 1 points 1 week ago* (last edited 1 week ago) (2 children)

Don’t know about tailwind but I used styled-components and not going back to vanilla css. CSS seems to be designed to be used with HTML, which did make sense back when it was created. Modern web is 99% JS and components composition which does not work well with Vanilla CSS in terms of class name uniqueness, specificity. Also it easy to dumb shit with CSS, like, I worked in the project where we had a lot of legacy global CSS. We had like dozen CSS styles which were adding margin to , and so on. I mean no classes, just globally. I’ve been forced to add ‘all: unset’ to basically all my new components just to avoid changing global styles and breaking something else. Do not recommend.

[–] [email protected] 1 points 4 weeks ago
[–] [email protected] 12 points 1 month ago* (last edited 1 month ago)

It’s not like I’m deciding on customer’s IT policy

[–] [email protected] 17 points 1 month ago (3 children)

I’m doing cloud migration now and one of assumptions is that two regions in Americas is enough for resilience. I’m in danger

[–] [email protected] 98 points 1 month ago* (last edited 1 month ago) (11 children)

Nope, JS is “You think you are nerd”.

Also, why React is there? It’s a lib not a language

4
submitted 3 months ago* (last edited 3 months ago) by [email protected] to c/[email protected]
 

I hope this is allowed

106
Coder (lemmy.ml)
 
9
submitted 1 year ago* (last edited 1 year ago) by [email protected] to c/[email protected]
 

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 ›