Hey, it’s been a while! How have you been? Did you miss us? We sure did miss writing these updates up for you!
While we were away, we were busy keeping up with updates to our development tools and libraries, so here’s a summary of updates that went into production since we last posted:
- 🏎 Improved API performance on GET requests by moving some of the API implementation from Rails to Go. You’ll notice a significant increase in speed when hitting the projects and clients endpoints.
- 🕵️♂️ Improved user permission restrictions and added more tests.
- 🐛 Fixed a couple of bugs with managing downtimes that prevented them from being saved correctly.
- 📚 Updated libraries and tools where we detected security advisories for vulnerable versions.
You might be thinking, “that doesn’t sound like it would have kept you busy for 2 months!” And you’d be right! Err… OK, that didn’t come out quite right. Let me explain.
For the past couple of months, we’ve been working on a super secret project that we haven’t told anyone about. Until now. It’s not yet ready for release, but we are going to preview this for selected accounts before we do a full release to all Resource Guru accounts.
We will, however, offer a sneak peek into the engineer’s
holding cells offices to see what you can expect.
The Schedule page is the most heavily used page within our application, by far. It’s also the most complex view in terms of code and data that we have to process within the browser. Through the years, we’ve steadily improved performance and added features, but the existing codebase meant that we were trying to fit a Lamborghini engine on a wheelbarrow.
So we threw everything away and bought a new chassis.
What you’re seeing here is a full refresh of the same account, just using the next-generation Schedule. Pretty neat, huh?
But that’s not even the coolest part. By starting from scratch, we decided to make performance our guiding principle. Everything from loading data, complex calculations and drawing graphics has been carefully designed to offer rendering as close to 60 frames per second as possible, even for our largest accounts. This also applies to mobile devices!
So that’s enough of a tease for now. 😉 Of course, all of this comes with a disclaimer: nothing you see here is final, and will likely change before we release this into the wild. Stay tuned!