gregorburger

BHS Technologies (https://bhs-technologies.com) | Linux Embedded Software Engineer | Innsbruck, Austria (onsite) Hi,

we develop the RoboticScope a digital surgical microscope. We combine an in-house developed HMD with a robotic arm to achieve unprecedented ergonomics for the surgeon. We are searching for someone who has good knowledge in customizing and securing Linux on x86, integrating third party dependencies into our CI and deployment on the machine and developing a safe over the air update that can be used inside clinics.

Our tech stack: - Linux (Ubuntu, NixOS) - C++, Rust and Python - CUDA, OpenGL and Vulkan

talents@bhs-technologies.com

BHS Technologies | https://www.bhs-technologies.com/ | Full-Time | ONSITE | Innsbruck, Austria

We develop the RoboticScope a robotically, digital surgical microscope. We are searching for a software developer for the RoboticScope. You would be responsible for developing new features for the device including image processing on GPUs (Vulkan, Cuda, Wayland + KMS/DRM), control of the robotic system, user interfaces (Qt + skia) and for everything that supports running the software on the device (Ubuntu, NixOS, deployment system). We work on Linux and use C++, Rust and Python.

If you are interested in high-performance, low-level native development, contact me: talents@bhs-technologies.com

- As a starter Realtime Rendering [0]

- The siggraph courses on shading [1]. The 2017 course will be on 30th of July [2]. Current techniques from AAA engines.

- Papers from JCGT [3].

- Plus the paper collection from Ke-Sen Huang linking all graphics related conferences [4]

have fun reading

[0] http://www.realtimerendering.com/book.html

[1] http://blog.selfshadow.com/publications/s2016-shading-course

[2] http://blog.selfshadow.com/publications/s2017-shading-course...

[3] http://jcgt.org/read.html?reload=1

[4] http://kesen.realtimerendering.com/

Has anybody experience with testing code that produces graphics (e.g. 3D engines, etc.)? I saw some articles stating that mocking the API is a good approach. But how can you test shaders etc. Tests based on image comparisons seem very cumbersome. We currently rely heavily on our QA which does automated integration tests based on image comparisons. But there is no immediate feedback for developers with this approach.

Rust?

it does provide some limited reflection which is in my opinion the biggest missing feature in C++. (and no, I dont want to use macros for this)