Location: New York
Remote: OKAY (but still looking for competitive pay)
Willing to relocate: No
Technologies: Modern C++ (Open to Rust), high-performance systems, distributed systems, Python, Shell script
Email: dzd0qttdh@mozmail.com
-- Senior engineer (Entry level +2) with 5 YOE. Extensive experience in performance engineering and optimization. Hands-on experience on HFT. Please only contact me if your are/represent an employer. No headhunter please
Location: New York
Remote: OKAY (but still looking for competitive pay)
Willing to relocate: No
Technologies: Modern C++ (Open to Rust), high-performance systems, distributed systems, Python, Shell script
Email: dzd0qttdh@mozmail.com
--
Senior engineer (Entry level +2) with 5 YOE. Extensive experience in performance engineering and optimization. Hands-on experience on HFT. Please only contact me if your are/represent an employer. No headhunter please
Location: New York
Remote: OKAY (but still looking for competitive pay)
Willing to relocate: No
Technologies: Modern C++ (Open to Rust), high-performance systems, distributed systems, Python, Shell script
Email: dzd0qttdh@mozmail.com
--
Senior engineer (Entry level +2) with 5 YOE. Extensive experience in performance engineering and optimization. Hands-on experience on HFT.
Please only contact me if your are/represent an employer. No headhunter please
Location: New York
Remote: OKAY (but still looking for competitive pay)
Willing to relocate: No
Technologies: Modern C++ (Open to Rust), high-performance systems, distributed systems, Python, Shell script
Email: dzd0qttdh@mozmail.com
--
Senior engineer (Entry level +2) with 5 YOE. Extensive experience in performance engineering and optimization. Hands-on experience on HFT.
Please only contact me if your are/represent an employer. No headhunter please
Location: New York
Remote: Yes (but still looking for competitive pay)
Willing to relocate: No
Technologies: Modern C++ (Open to Rust), high-performance systems, distributed systems, Python, Shell script
Email: dzd0qttdh@mozmail.com
--
Senior engineer (Entry level +2) with 5 YOE. Extensive experience in performance engineering and optimization.
Please only contact me if your are/represent an employer. No headhunter please.
Interesting article. I investigated a few mentioned cases and here're my thoughts:
1. Pretty much all libgcc builtins (especially those manipulating integers/i128/bits) are known to be not super optimized and probably not well maintained to latest architecture. All places I worked use libdivide and other hand-rolled implementations rather than __addvti3
2. Many 32-bit inefficient compilations work correctly on amd64 platforms. Perhaps it's the lack of maintenance on 32-bit platforms?
3. When using two intrinsic in the same function, it's almost always slower than a hand-crafted snippet implementing the same semantic. Compilers aren't smart enough in this case.
It enables users to process string at compile time. You can implement a constexpr getRFC3339DateString(int year, int month, int day) -> string and then construct a constexpr string list.
The important part is that all the intermediate strings used during the computation are constexpr, to guarantee that the work happens during compilation.
Also, constexpr symbols can be demoted to regular const as needed by the compiler if necessary, such as when getting a pointer to one. constexpr doesn't mean "compile-time only", it means "compile-time compatible"
Right - you can use the std::string at compile time but since it allocates dynamically you need to copy to a fixed size char[]/std::array to use at runtime.
Congrats on the release. May I ask if the company is still hiring C++ engineer? I work full time in system programming, and the job post says 'post something you built with bun along with resume' which really confused me as I don't typically build things ON Bun.
Glad to see this. I don't want GNU to be rebranded into a mediocre open source project from radical free software symbols, and only someone who bites his fingers after scratching toes like Tux has the least possibility to appease corporations with those sugar-coated pills named "open source".
