The legal basis is there to protect wildlife from man-made disruption and provides a kind of ecological basis to limit the kind of boundless growth that politicians appeal to.
Unfortunately, for those laws to be effective, they have to be strong enough to beat the various legal shenanigans / loopholes which can be used by developers to effortlessly leapfrog them.
Finally, if the laws are strong enough, they might be effortlessly wielded to prevent even reasonable developments from occurring.
The law lands somewhere in the middle and I think there are always people at either extreme trying to take advantage.
As the position is for a lead engineer, it wouldn't be unusual for applicants to have ideas or a view on more recent developments in this technology area and/or it's application to this particular problem space...that's all I'll say
* Experience required in both data engineering and back-end engineering spaces
* Experience welcome in ML engineering and data science spaces
I've worked on this team for a year or so now and it's fair to say that there's been no shortage of things to work on - you'll be immersed in the challenge of computing and distributing personalised recommendations across the business via operational and analytical workloads.
You will also become a part of a company which adopts a lot of the nice danish working practices (family first).
The office culture is an important aspect of the business so 3 days a week is a needs-must.
* Experience required in both data engineering and software engineering
* Experience welcome in ML engineering and data science
I've worked on this team for a year or so now and it's fair to say that there's been no shortage of things to work on - you'll be immersed in the challenge of distributing personalised recommendations across the business and become a part of a company which adopts a lot of the nice danish working practices. The office culture is an important aspect of the business so 3 days a week is a needs-must. If this sounds like your bag - apply below:
Thanks for all the web dev advice and tech callouts. Some real neat examples there which I knew nothing about.
Regarding niches, I think as a data engineer, becoming fluent in an interactive front-end data-viz library might be the slam dunk that I'm probably looking for.
Having looked at D3, I am quite impressed! Do you have any experience or knowledge of this lib?
bandcamp is a bit more of a level playing field - the artists can decide whether they want to use the platform to stream or sell their music, while being given some control over the number of streams per listener before a song will be unavailable to stream (although this does lean on cookies, I think, so not difficult to get around...)
Wow - that sunroof thing is cool, I bet that was a fun area to work on.
There’s a lot to be said for data engineering when done at scale - systems design, devops, cloud engineering etc.
I’m not sure that’s going yet…
Building the individual units (reliable ETL pipelines) might be on the chopping block in the near future - I’m not convinced there’s 100 competing ways to build these.
Still - best way to get started is probably to get stuck in with running a data pipeline using a locally deployed Airflow instance. Read some data from some api and write it to a local database deployment (postgres?).
May I ask the same of web application development?
Longtime data engineer - web apps in vanilla HTML/CSS/JS with Node - and some fun with ncurses in C++. Copilot is helping me out a bit but I’m having fun!
Unfortunately, for those laws to be effective, they have to be strong enough to beat the various legal shenanigans / loopholes which can be used by developers to effortlessly leapfrog them.
Finally, if the laws are strong enough, they might be effortlessly wielded to prevent even reasonable developments from occurring.
The law lands somewhere in the middle and I think there are always people at either extreme trying to take advantage.