This is a list of books currently on my To Read shelf... literally. I do not suggest or anti-suggest any of them at this time as I haven't read them yet.
This is not the home of dotProject or web2project. It is the home of CaseySoftware, LLC. Any dotProject support questions should be referred to their support forums.
One of the most common configurations out there is related to allowing web2project users to have access to only specific companies. While it's not as simple as saying "users should only see things from their own company," it's not as complicated as you might think. Here's how I've done it for various groups.
If you start with the basic roles, here are the step by step directions:
Role: Project Worker
Non-Admin Modules - Allow - Access, Add, Delete, Edit, View
Companies - Deny - Access, Add, Delete, Edit, View
Reports - Allow - Access, Add, Delete, Edit, View
Explanation: This gives access for a User to do anything they want on any of the non-admin modules *except* for Company. But since all of my Projects are assigned to a company, they can't actually see anything other than the navigation menu and empty screens.
In previous years, I've reviewed & covered each conference as I went to them. In 2011, I got so busy that I gave up midway through the year and just decided to do a recap at the end.. it's only now that I realized how many I actually attended. So without further ado.. here are the conferences in order:
I've already written on PHP Benelux, so check out my PHPBenelux coverage here.
Although I attended the event below on behalf of my employer Twilio, this is not necessarily their position on this topic. I write representing my own opinion and thoughts..
Last week, I was tapped to represent Twilio at the Made In Austin recruiting event at University of Texas-Austin. While the event was well-organized, the students were sharp, and the overall experience was beneficial, I noticed something odd. When students approached me, they all had one of two approaches:
One group - thankfully the smaller one - would open with "Hello. I am XXX. I am looking for an entry level position where I can demonstrate my attention to detail and teamwork skills." It was basically the verbal form of their Objective Statement. While that's great on paper, I wanted to hear what they really think and want in a position, so I countered with:
A few weeks ago at php|tek, I was lucky enough to deliver the Closing Remarks. Well.. it was less "lucky" and more of a "wait..
If you haven't figured out by now, I attend quite a few conferences and catch a lot of presentations from numerous speakers. I've found that most presenters have a sweet spot. They're good at expressing a concept but don't get into the code. Others can build ridiculously powerful applications but couldn't describe the concept if their lives depended on it.
In the middle, there's a special kind of person. They're the ones that can explain a concept and whip up some demo code. Or alternatively, they can look at some code and identify not just what it's doing but likely reasons why.