4 ms·

> No. Professionals in engineering or the trades have to know the regulations that govern their industry and abide by them. Eh, not substantially or consistent

> No. Professionals in engineering or the trades have to know the regulations that govern their industry and abide by them. Eh, not substantially or consistently more than in software. It's possible to cherry-pick examples where engineers in other fields are more aware of relevant regulations, but overall, it's roughly comparable. I'm generally very critical of the move-fast-and-break-things mentality, but engineers in other fields are generally not more knowledgeable about industry regulations than software engineers are.

wglb 9y ago
American engineer building a bridge or tunnel in EU is certainly going to know EU regulations. An EE designing circuits for EU needs to know about lead-free solder requirements. On the other side, Mies van der Rohe needed to work with a US-certified architect to build the Seagrams. Having been in the software industry for a while, it is often discouraging to see how both explicitly and often inadvertently move-fast-and-break-things has resulted in some pretty bad software industry wide. Just look at the sense of most of the comments here--there seems to be a consensus of how to get around this, or how it doesn't apply to me.
- slededit 9y ago
  EEs everywhere know about ROHS simply because it makes no sense to have seperate designs for Europe and everywhere else. Also lead free solder really isn't that bad...
- cortesoft 9y ago
  Right, but the point is that you KNOW the country your bridge or tunnel is going to be used in, because you build it there. If I build a web app and deploy it on a server in California, it can immediately be used by people in almost any country in the world. Is it my responsibility to follow the censorship rules from China on my webapp in California? Is it my responsibility to know all the regulations on web apps from Sri Lanka? Building software with care and professionalism is unrelated to understanding all the rules in place all around the world.
  - isostatic 9y ago
    If you don't do any business in the EU I'm not sure how the new law would apply.
    - p1necone 9y ago
      So we should have a whitelist of countries we decide we are "doing business" in and block all other traffic globally?
      - icebraining 9y ago
        You don't need to block traffic, just don't specifically target those countries[1]. And don't track people connecting from them. [1] https://gdpr-info.eu/recitals/no-23/ https://gdpr-info.eu/recitals/no-23/
        aeorgnoieang 9y ago
        That "recital" is still pretty vague; the relevant text: > Whereas the mere accessibility of the controller’s, processor’s or an intermediary’s website in the Union, of an email address or of other contact details, or the use of a language generally used in the third country where the controller is established, is insufficient to ascertain such intention, factors such as the use of a language or a currency generally used in one or more Member States with the possibility of ordering goods and services in that other language, or the mentioning of customers or users who are in the Union, may make it apparent that the controller envisages offering goods or services to data subjects in the Union. Note that "the use of a language or a currency generally used in one or more Member States ... may make it apparent that the controller envisages offering goods or services to data subjects in the Union". So simply using a language in use in a EU member country may be sufficient that you "envisage" offering your goods or services. That seems significantly different than your claim that one need merely not "specifically target those countries".
        icebraining 9y ago

wglb 9y ago

American engineer building a bridge or tunnel in EU is certainly going to know EU regulations. An EE designing circuits for EU needs to know about lead-free solder requirements. On the other side, Mies van der Rohe needed to work with a US-certified architect to build the Seagrams. Having been in the software industry for a while, it is often discouraging to see how both explicitly and often inadvertently move-fast-and-break-things has resulted in some pretty bad software industry wide. Just look at the sense of most of the comments here--there seems to be a consensus of how to get around this, or how it doesn't apply to me.

slededit 9y ago
EEs everywhere know about ROHS simply because it makes no sense to have seperate designs for Europe and everywhere else. Also lead free solder really isn't that bad...
cortesoft 9y ago
Right, but the point is that you KNOW the country your bridge or tunnel is going to be used in, because you build it there. If I build a web app and deploy it on a server in California, it can immediately be used by people in almost any country in the world. Is it my responsibility to follow the censorship rules from China on my webapp in California? Is it my responsibility to know all the regulations on web apps from Sri Lanka? Building software with care and professionalism is unrelated to understanding all the rules in place all around the world.
- isostatic 9y ago
  If you don't do any business in the EU I'm not sure how the new law would apply.
  - p1necone 9y ago
    So we should have a whitelist of countries we decide we are "doing business" in and block all other traffic globally?
    - icebraining 9y ago
      You don't need to block traffic, just don't specifically target those countries[1]. And don't track people connecting from them. [1] https://gdpr-info.eu/recitals/no-23/ https://gdpr-info.eu/recitals/no-23/
      - aeorgnoieang 9y ago
        That "recital" is still pretty vague; the relevant text: > Whereas the mere accessibility of the controller’s, processor’s or an intermediary’s website in the Union, of an email address or of other contact details, or the use of a language generally used in the third country where the controller is established, is insufficient to ascertain such intention, factors such as the use of a language or a currency generally used in one or more Member States with the possibility of ordering goods and services in that other language, or the mentioning of customers or users who are in the Union, may make it apparent that the controller envisages offering goods or services to data subjects in the Union. Note that "the use of a language or a currency generally used in one or more Member States ... may make it apparent that the controller envisages offering goods or services to data subjects in the Union". So simply using a language in use in a EU member country may be sufficient that you "envisage" offering your goods or services. That seems significantly different than your claim that one need merely not "specifically target those countries".
        icebraining 9y ago