Mark Price

Low-latency systems, high-performance Java, Linux tuning.

[Mark Price @epickrram]

Getting down to 2.5 microseconds scheduling jitter: https://t.co/N0iZCzii26

[Mark Price @epickrram]

@grumpyjames On hols I'm afraid. Enjoy your trip!

[Mark Price @epickrram]

@nitsanw @GeeCON @JUGru Best talk title I've seen in a while, good work!

[Mark Price @epickrram]

@forked_franz @nitsanw @mjpt777 @PeterLawrey Congrats!

[Gary Bernhardt @garybernhardt]

unfortunately, as you probably already know, floating point

[Mark Price @epickrram]

Pretty dense read, but some gems in here
https://t.co/Y7DTRw94Rt

[Mark Price @epickrram]

https://t.co/juh2GZ0oqV

[Mark Price @epickrram]

We've had our heads down building our core product suite @4otcmarkets; now we're expanding our remote-first dev team. Performance and reliability are success metrics. Tech stack C#/Java/Rust/Cloud. Interested? [email protected] https://t.co/sAdCDBXCFL

[Mark Price @epickrram]

It's been *checks watch* a long time since I worked on any OSS. So I'm happy that @4otcmarkets has published DotMetrics, our monitoring sidecar for DotNet applications. Read more here:

https://t.co/2RUuTMjJgI

[Mark Price @epickrram]

@andymalakov The model was gpt-3.5-turbo, perhaps it has different training data.

[Mark Price @epickrram]

Most of the articles I've read on ChatGPT talk about the ability to generate code.
Today I discovered a different use-case that feels like it will materially affect my work.
1/7

[Mark Price @epickrram]

@grumpyjames All those private repos must contain higher quality code :/

[Mark Price @epickrram]

@grumpyjames Definitely has more worth as an oracle/encyclopaedia than as a coding assistant so far..

[Mark Price @epickrram]

Looks like I won't need to surf around kernel source code so much anymore...
7/7

[Mark Price @epickrram]

When I saw the first two words on the response, I thought I'd asked too much.
Turns out I just hadn't been precise enough...
6/7

[Mark Price @epickrram]

@grumpyjames What do they put in the medicine out there?

[Dave Farley @davefarley77]

1) Always start with a test.

Writing the test first shapes your design for the better. Starting with a test will set you up to code in an attempt to pass your test, rather than continuously going back to fix code that's tested too late, and failing.

Start as you mean to go on.