What should engineers call me tumblr




















However I do have to say, it really needs improvement. Having one central post-column looks comical on an iPad and really ruins the look and feel of Tumblr. Supporting new technologies like multi-column layouts would put Tumblr ahead of the competition.

They just show a scaled-up version of their mobile interface. This leads to a lot of annoyances about the iPad app. Apple so far has talked a lot about the new iPad multitasking features. With more discoverability comes more users looking to use it in their favorite apps.

When I tried to use Tumblr in a multitasking manner, it just fails to work. There is no way to have multiple windows of the app, and when it is in split-screen the UI fails to adapt well. On Apple devices, Everything Just Works. New and returning users will look to use multitasking and then learn that it is not supported, leaving them a little disappointed.

I think supporting features like these are essential for Tumblr to thrive in the growing social media space. A lot of my time is spent using and creating Shortcuts.

I really wish that Tumblr had a lot more support for Shortcuts. Currently, Tumblr has one action, and you need to login into that action inside the Shortcuts app.

Even if you are logged into the Tumblr app on your device. I think that improved support for Shortcuts will be necessary for the future for any app on an Apple Platform. Apple has been putting a lot of time and development into Shortcuts, and I really believe that Tumblr should integrate as well as it can into the Shortcut ecosystem.

These features will bring more people to the platform. It also makes Tumblr a good model candidate for an iOS social media app. You've probably already skipped those introductory screens that explain how the application works, a. I know! I was also on that boat once!

Although there are several super cool new technologies and features, it's also necessary that we know how to apply them in a correct way, ensuring a more fluid and pleasing experience within the application. The same applies to releasing a new feature, for example, how can people learn what your app is able to do? On the third day of the WWDC21 event, the " Discoverable design " session was able to deliver to us several insights on how to create a more interactive app and memorable experiences starting with the onboarding and coming all the way to the app itself.

Keep reading. The Worldwide Developers Conference kicked off this week, and we are following along to see the latest iOS improvements and dreaming up how to build a better Tumblr.

Over the years, the landscape of how people make posts on different platforms across the internet has changed dramatically. But here on Tumblr, we still want to stay true to our blogging roots, while giving access to a wide creative canvas, and the Neue Post Format reflects that work.

With literally billions tens of billions! It took many phases, and releasing the new editor on the web will be one of the final pieces in place.

A post is seemingly a very simple data model: it has an author, it has content, and it was posted at a certain time. In a standard normalized database table, these columns would look like:. For photo posts, this is a set of one or more images. As Tumblr grew, its capabilities grew. We added the ability to add a caption to photo, video, and audio posts. We needed somewhere to store that new post content.

Because Tumblr was growing so rapidly at the time, this needed to happen fast, so we took the easiest path available: add a new column! Needless to say, eventually this made it very difficult to have consistent and easy to understand patterns for how we figure out things like… how many images are in a post? Reblogs further complicate the storage design, as a reblog copies and reformats post content from its parent post to the new post.

The code to figure out how to render a post became extremely complicated and hard to change as we wanted to add more to it. With all this in mind, in , two needs converged: the need to have a more easily understandable and portable data format shared from the database all the way up to the apps, and the need for more types of post content, decoupled from post type.

We no longer need post types at all when storing a post. A post can have any and all of the content types within it, instead of being siloed separately with a myriad of confusing options depending on the post type. Now a post can be a video and photo post at the same time! When the new editor on the web is fully released, we can finally say that this format is the fuel powering the engine of content on Tumblr. Kanvas is an open-source iOS library for adding effects, drawings, text, stickers, and making GIFs from existing media or the camera.

The project is licensed under the Mozilla Public License v2. The web frontend updates we mentioned in our post about refactoring the Tumblr Activity backend have shipped! Follow this blog to learn firsthand when this happens. We might harden it with PKCE someday, though.

Happy hacking! Fixing Tag URL issues across Tumblr L and superchlorine are working on fixing a lot of issues about how we parse tags in URLs, so that we are more consistent across the web and the apps. Tumblr Ignite: pay to promote posts! Bringing two-factor authentication settings to the mobile apps We really want as many people as possible to protect their accounts by leveraging Two Factor Authentication, which you can currently enable by going to your account settings on the web.

Advance your career with Automattic rotations. Photo by James Wheeler on Pexels. Some of these things you may end up seeing on the site… Timestamps on Posts superchlorine hacked the website to show timestamps on every post, reblog trail item, and note in the notes view. Mutual Love Evgeniy hacked the Tumblr Android app to play a cute sound and animation whenever you follow someone who already follows you!

Grid and Masonry View for the Dashboard cyle hacked the dashboard on web to view it in a grid format like the Likes page on web or a masonry format like the Explore and Tagged pages on web. Post only to a Tagged Page Tanya hacked the post editor to let you post directly to a tagged page! A better inclusive and accessible design Apple has always focused on providing a great experience, from the presentations to what it proposes for the developers.

An inclusive app or game is not only usable by different people, but also welcomes people from diverse backgrounds and perspectives Discover how you can deliver inclusive apps that can foster amazing experiences for everyone who uses your software. We'll take you It afforded me time to learn a lot about our framework level and our design patterns, and I made some fundamental changes to how the Tumblr PHP app works.

More importantly, it almost doubled the amount of code I was expected to review, much of it outside of my previous work as a product engineer. Around that time, the senior engineers I was working with on messaging moved on from the project, leaving pretty much just me to finish the work a few months before we launched. Because of this, almost all of the PHP logic that exists for messaging on Tumblr is my code, and I became the go-to authority on how messaging works under the hood.

After launch, we continued to iterate on messaging features. A few of these iterations required heavy refactors of a system that was humming along, being used by millions of people.

One example of that kind of work was the Replies relaunch , which was outside my normal workload, but I lent a hand to help make sure it met the deadline we had set for ourselves. I also took the engineering lead on the infamous Lizard Election of , coordinating work among designers, web engineers, iOS engineers, and Android engineers, while also building most of the backend for it myself. It was an extremely ambitious project that we put together in a very short period time, all for one absurd April Fools joke.

I also spent a lot of my first two years participating in Breaking Incidents — at Tumblr these are usually sudden high-impact problems that need to be fixed quickly, usually by someone who is on call.

Sometimes these incidents were small, like just a user interface bug that had been accidentally deployed, and sometimes these incidents were huge, such as entire database clusters failing. All of this additional responsibility meant I started going to more meetings and talking to more people across the company, as I had carved out a space that I felt was my own.

It was really difficult and uncomfortable a lot of the time, and I made mistakes that broke things, but fixing them, persevering, and learning not to repeat them showed how much I was ready for a more senior role. I got promoted to Senior Engineer and stayed at that level for two and a half years, with a brief interlude as a Staff Engineer.

As a Senior Engineer, I felt much more empowered to take on difficult tasks, as I had a couple of major, successful projects behind me. I also started going to meetings that had nothing to do with my normal job responsibilities, as I felt that it was important to stay on top of what was happening outside of those responsibilities.

With only a couple hundred people at the company, it felt very feasible to know what was going on in most places. It was around a year into being a Senior Engineer that I was invited to become a Staff Engineer, which at the time was parallel with the Senior Engineer role, having only a slightly different set of expectations.

I fell into it naturally, as I was already doing a lot of the kind of work it expected, which highlighted to me that the best career moves are often the obvious ones.

Many of our tasks involved shepherding other engineers and providing insight into how to fix hard problems, and defining processes that affected most engineers. I hopped out of the Staff Engineer role after nine months or so, and the Staff Engineering group was dissolved shortly after I left it. I started tackling bigger problems with our legacy systems such as getting them GDPR compliant and helping shape the architecture of new features such as the Neue Post Format.

As I became a Senior Engineer and then Staff Engineer, more of my work became self-directed rather than decided for me by a supervisor. Instead of being given tickets to solve in a sprint, I got to do a combination of choosing my own work and being asked to help in certain areas by other managers and my supervisor.

I went wherever that focus was needed, which still meant more time talking about problems, but now also more time writing framework code in support of other engineers. After gaining a lot of experience in how Tumblr worked, it became easier for me to see where there were opportunities for improvement, both engineering- and product-wise.



0コメント

  • 1000 / 1000