chrisdevs

Thanks. I enjoyed putting this together.

It's been satisfying watching the temperature forecast compared to my local station.

I'm not measuring wind for the reasons you stated.

The temperature forecast though has been interesting to compare and track. That's what I am most interested in.

Great question. Haven't figured that out yet personally.

Will let you know :)

I'm a research engineer on the team behind this at Datadog AI Research.

We released a family of open-weight models today, 4M to 2.5B params.

It's the first time we've been able to scale time series foundation models this large and train them long enough to see performance keep improving with size.

These were trained on internal Datadog observability data (from monitoring ourselves) and synthetic data.

More details in our blog post (https://www.datadoghq.com/blog/ai/toto-2/), technical report is coming soon.

Happy to answer questions.

Full disclosure, I work at Datadog as a research engineer and this was my team behind this.

We’re releasing an open-weights time series foundation model and 350 million datapoints as a benchmark (Apache 2.0 license). The model and dataset are up on Huggingface, the paper is on Arxiv (links in the blog post).

The model and dataset all come from our own internal telemetry. We dogfood extensively and pride ourselves on being best in the world with dog puns.

I joined the team 10 months ago, coming from a data engineering background. This was my first research project. The amount of work that went into this paper blew me away. It was scary taking on a new role mid-career like this but very rewarding, I learned a ton moving from data engineer to research engineer.

Give the model a try, grab the dataset, and let us know how we can help.

We are excited to see what you build!

I like writing, it's one of my strengths as a Staff Engineer.

I've read too many books on how to write well.

Here is a list of the best 13 quick fixes you can apply instantly to make your writing more effective at work.

TLDR Good writing is when you respect your reader.

Please let me know if you have any other techniques that have helped you!

Reflecting on this past year, I realized this was a big part of my growth.

How do you communicate effectively across your org? Especially if doing glue work.

> From a broad vision, I make a small bulleted list of what a finished MVP might look like

I like this approach.

It's hard to project far into the future, especially when you've not gotten started.

Set a rough target, move towards, and continually adjust as you learn more.

Oh boy.

I’m glad you asked.

Here’s what works for me:

- don’t plan too far into the future, the further you do the less specific you should be

I like annual visions for each area of my life, so once a year reflect on each area and think where you’d like to be a year from now. My annual time capsule I call it, is coming up next week and I can’t wait!

- do monthly reflections

I have a google calendar reminder that links to a journal template. Here I briefly reflect once a month on what’s working and what’s not in each area

This is more tactical. Habits and things to help implement the vision

- ad hoc reflection

When struggling with something or needing to evaluate, I’ll just open a doc and type. Stream of conscious style to get it all out there.

Then read it and pluck out next steps. Sometimes this means pivoting, sometimes it’s just a deeper understanding of why the path I’m on is the right one.

Sorry for the sloppy writing here. I actually would like to write this up better when I’m not on mobile.

Hope it helps

We all have "off" days from time to time.

Happy to hear, thanks!

Best of luck.

I hear you.

I'm not a doctor.

I don't know how to advise the chronically ill and medically under-served, so I can't speak to those circumstances.

What would you suggest?

:)

Let's make a distinction.

If you're sick -> take care of that first. Don't work.

If you're just having an off day, trouble focusing, not feeling in the mood, that's different. I can suggest a few things that's worked for me.

1) Focus on just doing one thing.

Pick your most important project, then pick one specific piece of that, and shut down everything else until you at least complete that.

2) Set a timer.

If you're problem is getting started on a new or challenging project, do something like the pomodoro technique where you just promise yourself you'll work on it for X minutes and then stop. This removes some of the barrier to entry and can help you get started.

3) Remove distractions.

Similar to the first point, but is Slack always on? Are you getting notifications from your phone? Checking e-mail? This is a problem with our current life, we have too much competing for our attention. A lot of what we need to do to be successful is blocking out the noise so we can focus.

Hope this helps!

Thanks!

People change over time.

I graduated college absolutely certain I would be a day trader on Wall Street for the rest of my life.

And I did that for about 7 years.

But 5 years in or so I started to realize I didn’t quite like it. I actually was more interested in writing code to solve my trading problems. But what really appealed to me there was the writing code bit.

It took about a full year of my mini identity crisis for me to realize, there were other jobs out there I could enjoy. And the career my 20 year old self had picked wasn’t my ultimate path.

It’s OK to change directions.

Continue to reflect on what you want for yourself. Don’t try to predict too far out because it will likely change. But think about the next year or three, where do you want to be?

Once you have a rough idea in mind you can think backwards about what steps are needed to get there.

Hang in there, self reflection is tough but very worthwhile.

Your previous experience absolutely has and will NOT go to waste. I can’t tell you how many times my finance experience has helped me at my software jobs or just in life.

While it may not be directly related to your new job, that experience is there, helping you in more ways than you realize.

Wow, I’ve never heard of him.

His two most popular books, The Psychology of Computer Programming and Introduction to General Systems Thinking sounds very interesting.

Thank you for the suggestion!

1) Keep reducing scope on all critical pieces needed for you to release/publish/finish v1.

2) Don’t do anything else in the meantime.

3) Ship a v1. Don’t wait for it to be perfect, learning from real users/ readers/ viewers/ etc is more valuable then working in a silo.

4) Then iterate.

Any good but distracting ideas that pop up between step 1 and 3, just write them down for later and get back to work.