3,695 karma · joined April 11, 2009
That said, we are all producers at my studio and we also respect each other's space. Everyone designs in some capacity and we're all very comfortable in our skin. We don't really "snoop" on each others work if we know it's not time for feedback or we're not co-designing. The only time I'd pop into someones file or artboard I know they are actively working in is if I need to quickly copy/paste something I know they have (little things like this are amazing). Speaking of co-design, this is my favorite part of Figma. A few days per week we dedicate time to co-design with another person, kind of like pair-programming. Generally we both already have a base level of work complete and we talk through it, then riff on each others ideas and work to come up with something new or solve problems in different ways. Working this way at least a few days per week has really paid off for us and it's quite fun. I also feel like I learn new design tricks or skills I wouldn't have if I wasn't working this way.
I feel like between using this feature in a pre-planned way and also having some unspoken rules/constraints around how we review each others work is all you need to do to make this less of an issue. Honestly I look at it the same as literally standing over someones shoulder. I would never do that unless invited, and even then I'd prefer to sit next to them and it be more collaborative. There is also the trick, which some people do at our studio, of simply working in a private file until you're ready to paste everything into the collaborate projects. It's as simple as a copy/paste and you have complete privacy if that's what you want. We purposely do this with most of our clients so they are not tempted to leave feedback before we're ready.
I recently decided to give Webflow a try after a good friend, who does happen to be a front-end dev (and quite good), told me how cool he thought it was.
He wasn't wrong. Yes, you have to pay to really do anything with your creation, but I think it might be worth it (if you're a designer who doesn't want to learn to code). I was extremely impressed with how quickly I could export my assets and various measurements from Sketch and lay everything out in Webflow, especially when it was time to build the various breakpoints and add some animations.
What would have normally taken me a few days (over the course of a few sessions), instead took me 2-3 hours, tops.
More importantly I used flexbox for much of the page, which is something I hadn't touched before. I've of course read about it and have a basic understand of how it works, but I'd have spent A LOT of time getting that aspect of it right had I been coding from scratch.
The best part was, at least from what I could tell and based on their claims, all of this would have exported to clean code worthy of a production site. Pretty cool.
So, as the author mentions, Webflow is very interesting. It's just not exactly practical because of the way it's tied to their CMS and hosting platform. If you're only really building marketing sites for clients who need basic hosting anyway, it might be perfect for you, but outside of that I can't imagine where I'd use it. Certainly not on a product team, but it's still worth playing around with on the free plan.
I have had Flash disabled via a browser extension for what feels like years now.
I'm not saying this excuses the removal of the headphone jack, but from a business perspective it does add up.
Specialty coffee was great for the margins, but the market-share was not even close to the numbers being reported in this article.
If the drivers are maximizing for time you're not going to sleep very well because they are driving like a maniac. Sudden halts, near misses, and sharp corners make for a particularly terrifying experience when you're attempting to sleep.
The fact that this endeavor is focusing on drivers that go slow is 100% a positive for me and I would now consider trying it.
This is an issue that really just exists with overnight buses, as trains don't make sudden stops and they are not competing with other trains for a lane.
Still crazy that anyone would opt-in to do this, but a misleading headline all the same.
Is this meant to be a cool tech demo, or a real product? I noticed the author mentioned adding new features and a premium version in another comment. This leads me to believe it's intended to be a real product.
With that in mind, I have a few questions:
1. If this is inspired by Notational Velocity, a very popular and real product, why is this also named Notational? I understand if you're doing a cool tech demo that it's not a big deal, but if you plan to charge money for this you probably shouldn't copy their name.
2. Was "Notational Velocity but real-time" your hypothesis of what would make this something people want to use/buy? If so, what about all the other very standard features that note-taking and thought storage apps have? Do you plan to hit baseline with those?
3. How do you compete with the larger companies who offer these apps for free to their users? Google Keep, Apple Notes, etc.
4. Is the real-time feature the only way you plan to make this different/better than the others?
I'm not trying to be a downer here, but I feel like I see "X app but real-time" posted to HN on a weekly basis now, like it being real-time is going to be the differentiator that makes it wildly popular. Those products then go on to ignore half the reasons why the others have users. Even if they reach feature parity, their one differentiator is "well, it's real-time". I'm not sure that's enough.
If this is just meant to be a cool demo of Vue.js (with an awesome homepage), well done, ignore my comments =)
It kind of comes with the territory.
I don't think this will ever happen, but it's an interesting hypothetical.
It's night and day versus growing up in Austin, where I drove everywhere, rarely used stairs, and walking consisted of taking out the garbage to the curb.
1. Ability to "lock" a row. We often build lists in Asana that are not meant to be tasks. It's great for project planning or status boards. The problem is everything in Asana is very easily checked off or moved, which sometimes can happen by accident. This provides a feeling of fleetingness that I think makes some people (especially super detail oriented project managers) nervous.
2. Native Apps. I really need a great official OSX native app. The iOS app, while it has gotten better, has always felt like an afterthought to the company.
3. Notifications. This is the main reason I want a solid OSX app. I need notifications to work really well. If something is important and needs my attention, I need to instantly know about it (and knowing about it via a push notification on my phone isn't good enough). Slack has cut down on email usage for us, like many, significantly. I don't check email as much now, so I can't rely on email notifications for our primary project management tool.
Overall Asana is great. I always end up going back to it after using other tools. I do agree however there are a few small things that would help to make it feel a bit more "grown up".
Looking forward to trying this out!
Edit: You guys might want to be a bit more clear that you're requiring a credit card to signup for beta access, even if you're not charging for 30 days.
I'm very happy with the change. I do miss the beauty of the pacific northwest, but otherwise it's been great.
Case in point: I live in a walking city (NYC), avoid the junk described above, yet I eat/drink out often and at 31 years old I'm in above average shape without any serious exercise (other than walking up lots of stairs, and around the city, daily). Of course I could do more, but the point is cutting out some simple items from your diet can go a very long way.
Now I want to read Neuromancer again. Great book.
I'm actually curious if anyone knows how well Uber Pool is working? I've never used it for a few reasons, but a big one is that I don't want to risk another rider pickup causing me delay in getting to my destination.
Even something as simple as having an avatar next to your name makes all the difference.
The real question should be what does Slack do that Hipchat did not? The designs are obviously much different, but other than that, was it just amazing marketing and word of mouth? Even the Slack founders seemed a bit baffled by this when asked months back.
After working for the past 6 months in an office with 4 shared conference rooms and around 20 people, I can say with 100% confidence this pricing would have been approved pretty much instantly.
The conference room shuffle was a headache every single day and caused constant distraction and productivity loss. I know plenty of other people at other companies who have reported the same issues with their conference rooms. Hell, even in the Facebook HQ when I've gone in for meetings has had this problem (though their system is already pretty decent from what I can tell).
If you've felt this pain (regardless of how first world it may seem), I think you'd agree.
Personally I'd rather just never have meetings, but that's not always an option =)