Joined 18 years ago
We're a development team of about 20 working on applications for small and big companies such as the Deutsche Bahn. We develop using Django and React, striving for a clean API between backend and frontend. On the backend, we've been using Django exclusively since starting out in 2007. Needless to say, we know our way around Django...
Currently we're looking for a backend developer at an intermediate level. See the jobs description here: https://www.jonasundderwolf.de/jobs/) or send me an email directly at "jvp" on our domain.
One note, however: our language around the office is German so you would need basic fluency or a willingness to learn.
Absolutely - I've learned this the hard way and it's giving me new appreciation for phone calls.
It's amazing how many people do _not_ remember that an email chain of several hundred pages _will_ contain something incriminating or embassaring if forwarded to someone outside the original circle of recipients.
[0]: https://www.chelseagreen.com/product/oil-power-and-war/
I just read a calculation how automatic milking machines will turn a tidy profit on milk into a loss with energy costs per kwh just 10 cents higher. Milking by hand will be _more_ profitable with that small a difference.
So it's controversial because doing something about climate change involves massive changes to our way of life. Not simply switching your SUV for a Tesla, we're talking up to and including economic collapse and deindustrialization.
Cars are a net negative for societies (see e.g. https://tu-dresden.de/bu/verkehr/ivs/voeko/ressourcen/dateie...). Just imagine having most (80%+) of goods transported by cargo bike: lots of (local!) employment, lots of new technology needed, etc.
However, now I'm at a loss on how to teach the junior programmers at my company how to recognize which patterns scream "turn me into a state machine!" Several booleans triggering certain code paths in several methods is a pretty sure sign. Are there more?
