I've come up with the following actions for my project. These came up by reading the relevant documentation and it's my first try at creating a proper workflow for managing my project.
Are there any optimizations, or a more "standard" way of doing things. Additionally I found some popular actions...
I implemented a simple function that generated random bytes Vec<u8> with given n size. Then I wondered how can I optimize this.
Here is the first implementation:
use rand::{Rng, RngCore, SeedableRng};
use rand_chacha::ChaCha20Rng;
fn random_bytes(n: usize) -> Vec<u8> {
let mut bytes = Vec::w...
When doing Data Science projects, I often have to load data and metadata, and output results, plots, logs, etc.
Therefore I have to handle all the file paths from where to load the input and write the output.
I don't think that hardcoding the paths in the script is a good practice, therefore I wr...
Also do some electrical circuitry work for certain aspects of our applications. (I.e. if we need a cheap step-down transformer for a lightweight DC device)
My first job in software engineering was at Teradyne. They make automatic test equipment for electronics. I worked in the semi-conductor test division, writing compilers and device drivers.
I would like to know the appropriate way to structure the directories for a ML python project; in order to make the project easy to read, mantain and get the imports of packages properly working. (i.e. having the imports run smoothly both when running from command line and from an IDE, without ha...
@konijn: I cast the downvote because the question has no code in it and it is asking for general best practices. Both of those reasons make the question off-topic, in my opinion.
I implemented a simple function that generated random bytes Vec<u8> with given n size. Then I wondered how can I optimize this.
Here is the first implementation:
use rand::{Rng, RngCore, SeedableRng};
use rand_chacha::ChaCha20Rng;
fn random_bytes(n: usize) -> Vec<u8> {
let mut bytes = Vec::w...
