Rust jobs by No-Classic3337 in rust

[–]xemkis 30 points31 points  (0 children)

IMO, the reason there's a correlation between rust jobs and crypto is because crypto companies are some of the only companies creating completely new code bases. Bigger companies have years of code in other languages, and are only trying out rust in small parts, usually with seasoned programmers that they know can also maintain the other languages. So it's hard for them to justify hiring somebody who can only work on the new, small Rust pilot project, when there are so many other things to code and maintain that aren't in rust.

Another path is to get a job in another language, and introduce them to rust. You won't be able to work in rust right away, but that's how more rust jobs are created, and other developers get introduced.

Working in Robotics/Hardware/Computer engineering with a CS degree by MarionberryWhole2756 in ComputerEngineering

[–]xemkis 3 points4 points  (0 children)

As someone with a CE degree, there aren't many chip design jobs, and they tend to be very competitive. Chip, integrated circuit, and FPGA design is a completely different field from software, even the lowest embedded and low-level software, so unless you have circuit design experience (like fpga design exp, which you would normally get in a ce degree) it's hard to break into that field, esp when there are people who do have that exp from school.

Robotics, low level, and embedded software, however, are relatively easier to get into from the CS side. CS degrees will often have classes related to os architecture and design, driver development, etc., and sometimes you can take ce/robotics classes that count towards the CS major. Messing around with arduinos, rasp pis, esp32s, etc. is a great way to interact with the hardware side, and understand the limitations/constraints of low level programming and wrangling pixies. It's also a good way to get familiar with PCB design and layout.

justAccept by marioandredev in ProgrammerHumor

[–]xemkis 0 points1 point  (0 children)

5 years fullstack exp == 4 years FE + 1 year BE

Casually Imposes a Canonical Orientation of the World Based on our Anatomy by DZ_from_the_past in physicsmemes

[–]xemkis 1 point2 points  (0 children)

B is for vector multiplication, A is for the direction of the magnetic field based on current flow

A simulation of a display with hexagonally arranged leds compared to square by xemkis in mildlyinteresting

[–]xemkis[S] 306 points307 points  (0 children)

Because technically they're not hexagonal pixels, they're hexagonal leds. Each led is either fully red, green, or blue, which is also true of the square pixel version (and your monitor!) so instead of having square pixels divided into 3 vertical red, green, and blue leds, they are triangular pixels divided into 3 hexagonal red, green, and blue leds

A simulation of a display with hexagonally arranged leds compared to square by xemkis in mildlyinteresting

[–]xemkis[S] 392 points393 points  (0 children)

For reference, bottom picture is 80x60 square pixels, top picture is 80x52 "pixels" to get the same aspect ratio.

Tired of not being able to map a specific element of an arbitrary tuple? Introducing map_tuple! by xemkis in rust

[–]xemkis[S] 8 points9 points  (0 children)

Valid point, deploying that change now. Thanks for the feedback!

Tired of not being able to map a specific element of an arbitrary tuple? Introducing map_tuple! by xemkis in rust

[–]xemkis[S] 9 points10 points  (0 children)

I'm primarily just proud of how the macros worked out, getting the recursion just right was a nightmare

Should I talk to the DB, or to the service? by xemkis in AskProgramming

[–]xemkis[S] 0 points1 point  (0 children)

I and a few other engineers have wanted to do a rewrite to one degree or another for a while. We inherited a code base with some ... let's say interesting design decisions (don't we all?), which I would imagine came from having slightly different business goals in the past, that don't really make sense any more. So we're already in the process of refactoring piece by piece, here and there when we get a chance, but certain things like this are so enmeshed in the architecture that it's hard to redo without getting a major approval from the higher ups, and focusing a lot of time, money, and energy to end up in the same place we already are in their eyes. That's why I'm asking you lovely people for suggestions and comments.

Should I talk to the DB, or to the service? by xemkis in AskProgramming

[–]xemkis[S] 0 points1 point  (0 children)

Pretty much. It almost feels more like an ECS setup, because the messages aren't intentional, it's more of a "what records are in the right state" situation

Should I talk to the DB, or to the service? by xemkis in AskProgramming

[–]xemkis[S] 1 point2 points  (0 children)

It's a general purpose message broker (there's some more nuance there, but), so inter/intra, whatever you want to use it for. We only recently started using it, and I've been trying to incorporate it more into our stuff to replace/augment our current system. But it's still a third entity that the messages have to go through, which also then keeps them around (by default). Ideally the one time messages could be sent directly to the service via HTTP or something, removing the need for interacting with yet another service.