![James Farrell](/sites/default/files/pictures/img_0.jpg)
I am a long time UNIX system administrator and open source advocate. In recent years my primary focus as been on Linux & FreeBSD systems administration, networking, telecom, and SAN/storage management. I love building infrastructure, tying systems together, creating processes, and bringing people together in support of their technical efforts.
When I can, I try to contribute back to the open source projects either with patches, or by helping others in technical support forums.
Authored Comments
The sticky bit is used on directories where you need other people to create and delete their own files, but not the files of others. This is typically used on shared systems where a common data folder is desired. The best example is to look at /tmp which is owned by root and sticky bit set so that any system user can create & remove their own files, but not the files of other system users.
Nice summary, thanks.
One thing I'd lover to hear about is what kinds of software development project (types of products) are better geared toward scrum or kanban. I think I see a lot of literature which implies that scrum is well suited for projects like web applications where we have the luxury of incrementally improving the product and controlling how it is tested/approved. But scrum doesn't seem well suited to other kinds of software delivery ... interested to hear people's opinion on that.
I tend to prefer kanban, but I generally see management not liking that as it is less rigid in its incremental delivery cycle ... as in, managers seem to like scrum sprints because at the end of 2 weeks you know what you have or don't have ... and that sort of time-boxing is not appropriate for every kind of software product and release cycle.