752 karma · joined May 8, 2011
I was also blown away by Mike Lazaridis' stories about RIM especially when reading it so many years after the iphone/android launch.
This feature has been in the works for multiple months now and I'm really glad to finally see it ship officially with Qt 5.4, so congrats to the team!
What I meant was that the possibility to access private chats should stay not retroactive and only happen once the company has explicitly stated it will need this feature enabled.
EDIT: so that if my company has no legal needs today it won't have access to private chats made today once they decide in the future that they now need the feature
I understand specific companies have specific needs and Slack has to meet some of these but there is no reason that this should impact everyone else.
So I end up having multiple phone interviews and then on-site interviews until I get one or more good offers. Just recently I got 3 really good offers in the span of two weeks and took the time to chose the one I really wanted to accept. I told each company I was interviewing at other places too and wanted some time to think.
I'm more thinking in the idea of doing some "pre-validation" in my library to avoid an API call from the client when something is already expected to fail (like missing the amount field right now) which would not fail with a new version of the API. So I would have to adapt to each version to know that this user would require the amount field while another one would not.
But I agree, I read some of the worst comments and would be nice to get a link to the discussion for each of these to get some contexts!
* based on IE7 so a lot of websites don't work/render properly. This does not seem important when the core of your users go on google/wikipedia and that's it. But my grandmother loves to order online but is limited to amazon because most of the other websites don't work properly. She would gladly pay more to be able to simplify most of the main websites UI for her and ease her order flow.
* Impossible to have more than one tab. This seems logical at first because it simplifies everything, but when she is ordering something as a gift and wants to look for an address she has to close the whole application and go in "notebook" and start over again. Same with the idea of having multiple tabs in IE.
* Email services really limited. Their idea is to avoid spam you have to whitelist every email address. But this is not negotiable, so when you order for the first time online you can't use your system's email because you'll never get the "confirm your email address". Or you use a gmail account for this which immediately make things too complicated for her.
* Most of the other features (games especially) are really limited/dumb such as having to recognize a banana. Creating games for her is something I'm planning to do but with the old browser inside the machine it makes things harder.
* Pictures management! We all send pictures to her by email but she can't organize them at all. I've been thinking of a UI for this but when I draw it/explain it I immediately see she would be completely lost. She needs a simple UI on top of explorer of something that would do "delete, crop, move, rename, add comments". And on top of that the main feature she needs is "print it for me and mail it to me". Websites already exist for this feature but she would have to understand how to upload photos and then use them which is clearly impossible.
* Keyboard! Another big issue for her is being able to raise her arms high enough for a long period of time to type an email on the screen with the tactile keyboard. At the same time, the keyboard delivered with the computer is not in alphabetical order. I've been trying to teach her but it takes her a long time to write so she mostly gives up and limit herself to a few words!
Hope this helps!
It depends. When someone is stuck on a compiling issue, pinging me on our chat/IRC is clearly easier than speaking loudly and hoping I'll hear and help. But at the same time, being able to hear other people discussions and chose when I think I'd be able to help is awesome. It also helps me learn a lot just by hearing other people technical issues.
Also open floorplan does not mean "just 8 members of your team" in the same place. Where I was before it meant 120 developers working on different project for the company but in the same place. An issue with this is that people outside of the developer teams would just pop over to my desk because I was the one that seemed available to ask for things. This can be annoying if it happens 10 times a day especially when none of the questions have anything to do with you. Explaining them that sending an email with questions would help worked most of the time and forced them to try and contact the right person instead of asking the developer closest to the door especially at lunch time.
If this is actually the case, you're in the minority. After doing this for... 19(?) years, few developers I've met or worked with are actually more productive in open environments
That may well be true. I've worked this way for 8 years now and clearly enjoy a lot more open floorplans especially when it is "developers-friendly" so no sales team next to you using the phone all day.
I'm in favor of private work spaces and open common areas where people can meet to collaborate when they want.
The issue with this is that I then lose the ability to follow what other people are working/stuck on and whether I can help, etc. Because people will most of the time stay in quiet area and use the open spaces only for informal gathering, having fun, or even meetings when no rooms are available.
I've always worked this way, focusing on something while a part of me was processing what was said around and being able to "pause" what I was doing to help around and get back to my work pretty easily. Of course it does not work all the time and some times you just need to focus for a few hours and in this case I just increase the volume of my music in my headphones and stop caring about the rest.
For me the main issue with open floorplans is when other people assume they can just come to your desk and ask you anything without thinking you could be busy and/or in the zone as you describe it when having a closed office would make them think twice before just dropping by unanounced. For me this was easily solved by explaining that it is a lot easier to drop me a line by email or chat and I'd get back to them as soon as I was available.
[1] https://news.ycombinator.com/item?id=5892957 [2] https://news.ycombinator.com/item?id=6339434