Bozho, a Bulgarian software engineer and former e-governance minister, writes about GDPR, security, authentication, and software design.
HN commenters link his GDPR practical guide for developers, which one calls trivial to follow, and note his background as a minister and Stack Overflow contributor.
I found F# really good at with this -> "wrap around the idiosyncrasies of the underlying imperative".
In the video Paul Phillips elaborates on many subject much better than I could ever do.
I also found the .net ecosystem libraries better, even though there are fewer libraries available.
Some links that I found great on the subject:
https://www.reddit.com/r/scala/comments/4246qc/heres_why_scala_sucks/
https://techblog.bozho.net/i-dont-like-scala/
To be honest with you my social circle of software engineers gave up Scala long time ago and we do not even consider it to try it ever again. Most of the projects we do we simple use Java for JVM (since version 8 there are many useful features that you can use and have relatively terse code that is also easy to read) for the .net ecosystem we use C# of F# depending on how relaxed the engineering team and the stakeholders about it.
For data engineering (ETLs, glue code, etc.) Python works. Since Spark has a Python interface it is also not needed to use Scala there.
For frontend obviously Scala was probably never a serious option.
There is no use for Scala for me or for the companies I work for. The last time I tried Scala it was horrendous. SBT? Seriously? Binary incompatibility between minor versions? I could go on an on of the collection of anti-patterns I have encountered. Since I have limited time and there are a ton of other software environments that we can use and have much better experience why on Earth would I want…
The Media Agency's Guide To GDPR And EPrivacy
Ad Exchanger.com
https://adexchanger.com/agencies/media-agencys-guide-gdpr-eprivacy/
MarTech Today’s Guide to GDPR — The General Data Protection Regulation
MartechToday.com -
https://martechtoday.com/guide/gdpr-the-general-data-protection-regulation
Guide to the General Data Protection Regulation (GDPR)
Information Commissioner's Office
https://ico.org.uk/for-organisations/guide-to-the-general-data-protection-regulation-gdpr/
What is the General Data Protection Regulation?
Facebook Business
https://www.facebook.com/business/gdpr
EU data protection law may end up protecting scammers, experts warn
The Guardian
https://www.theguardian.com/technology/2018/feb/06/gdpr-data-protection-law-scammers-whois-tools-internet-european-privacy
GDPR - How it works. A little bee book
IBM
https://www-01.ibm.com/common/ssi/cgi-bin/ssialias?htmlfid=IMM14202GBEN
HPE Explains What European GDPR Privacy Regulations Mean to U.S. Firms
eWeek
http://www.eweek.com/security/hpe-explains-what-european-gdpr-privacy-regulations-mean-to-u.s.-firms
GDPR - A practical guide for developers
Bozho’s Tech Blog
https://techblog.bozho.net/gdpr-practical-guide-developers/
Preparing for the EU General Data Protection Regulation
IAPP.org
https://iapp.org/media/pdf/resource_center/TRUSTe_GDPR_Report_FINAL.pdf
GDPR - What you need to know and how to prepare
SendGrid
https://sendgrid.com/resource/general-data-protection-regulation/
Pulse Survey - US Companies…
> but I have never seen anybody complain that "I switched to logback and slf4j and my jndi substitutions stopped working."
SLF4J was created to replace Apache Commons Logging and Logback was created to replace Log4j 1.x. Both were created Ceki Gülcü, the original author of Log4j 1.x [1].
Logback came out in 2006. The first beta version of Log4j 2.x was only released 6 years later in 2012, and the JNDI lookup feature was added in 2.0-beta9[2] in 2013!
Obviously nobody complained when switching from Log4j 1.x to SLF4J+Logback that a feature from a completely different library (with the same name) that would be created 7 years into the future was not supported.
> Somewhere in this mess, someone hooked up the pattern capabilities into the formatting system.
That's not what happened. The lookup mechanism (which includes "$
{jndi:}" lookups) is completely unrelated to the message formatting subsystem.
The way formatting and pattern lookups work in log4j2 is:
1. logger.info("Hello
{}", "world") creates a FormattedMessage instance with the "Hello
{}" format string and a single parameter, "world".
2. The FormattedMessage is wrapped in a LogEvent and routed to the correct appender(s).
3. Most appenders will format the LogEvent with a Layout. In our case, it's PatternLayout we care about[3].
4. PatternLayout will pre-calculate a set of PatternConverters based on your pattern, so it doesn't have to keep parsing the pattern on every invocation. "%m" will map to…
Compliance is trivial and involves steps that are already best-practices anyway. You won't need to split any atoms.
https://techblog.bozho.net/gdpr-practical-guide-developers/
The penalty isn't meant to be something you afford. It's a penalty. (It's a feature, not a bug.) I'm having a really hard time not being sarcastic right now but compliance with the law might also end up being an economical option worth looking into. Cheaper than lawyering-up for being sued by shysters for non-compliance, and cheaper than being penalized for non-compliance.
Mind you, taking whatever-it-is off the internet is fine too. I totally understand. What I don't like is all the whiny sanctimony and martyrdom. "Yes I'm taking my thing off the internet, but first I'm going to make a big deal about what a tragedy it is for the world." Um no. The fact that your thing is a "small business" means few people care about it. (Sad to say. More people care about Facebook than about you. That's why they're the big incumbent.) And it emphatically doesn't mean for example, that you're some hallowed, heroic underdog who deserves protection, especially when you won't even afford the same to your own users and their data.
I always find funny how the IT community in the country decides who to vote for or whether to vote at all. But to address your concerns, although I don't understand how the technicalities around someone's personal blog relate to what kind of a politician they'll be (as opposed to... idk... its 10+ years of content for example):
1. Superhosting is the largest Bulgarian shared hosting provider. Although they indeed offer a relatively mediocre service, they're far from unusable and have low latency for his Bulgarian readership. Also his blog is somewhat old, so there may not have been much choice at the time.
2. He has configured TLS for both https://blog.bozho.net/ and https://techblog.bozho.net/ although no redirect has been added for the first site. As far as we know this may have even been intentional.
I wonder what "blockchain" means here. The word is all over https://logsentinel.com/ but it may be just to make "immutable audit trail" more buzzwordy.
In 2017 they posted a skeptical https://techblog.bozho.net/blockchain-its-all-greek-to-me/ which in linked to from very recent https://techblog.bozho.net/digital-transformation-and-technological-utopianism/
> Technology alone will not solve anything. And my blockchain skepticism is a hint in that direction – many blockchain enthusiasts are claiming that blockchain will solve many problems in many areas of life. It won’t. At least not just through clever cryptography and consensus algorithms.