181–190 of 280 posts
Earlier quoted context omitted.
I would be much happier with smallish offices shared by small groups. Small private offices like Fog Creek would be my ideal: https://i0.wp.com/www.joelonsoftware.com/wp-content/uploads/...
Those wires though :O
Earlier quoted context omitted.
It matters in this case because the discussion took a turn towards comparing the compensation of staff to the provisioning of the office environment. In that context, companies' consideration of expenditures will take into account capital versus operational categories.
Why does it matter? It's all the same money no matter which budget it comes out of.
Organizations aren't rational; they're a product of their structure and incentives.
Earlier quoted context omitted.
C++ relies heavily on RAII. Exceptions are safer than broken instances from failed constructors.
Google C++ doesn't allow using exceptions and therefore requires broken instances from failed constructors.
Earlier quoted context omitted.
It saves a fortune, but the companies are spending a fortune on their employees' salary and benefits too I think we're talking the difference between $300/month on open desk space vs $1000/month on an office. It's a lot of money and it adds up, but these people are costing the company a total of $10k-$40k a month My theory is that open space is extremely helpful to certain types of people, and those traits coincident…
>My theory is that open space is extremely helpful to certain types of people, and those traits coincidentally overlap with the people calling the shots at a lot of companies. Sociable upper managerial-types probably value being able to collaborate more easily in open space more than being able to concentrate in private offices. Yes, and in addition, sociable developers value being able to collaborate more easily in…
And laptops have been the norm. It's a little different when you were accustomed to go back to your dorm room where you had your desktop setup to get anything done.
It’s amazing how this is the first time I have heard his name. Great people basically disappear under the Google name.
It's interesting how fleeting software fame is. Perhaps that's just a special case of how fleeting fame is. Folks who came of age in the early 2000s certainly remember him - he founded LiveJournal; wrote memcached, MogileFS, Gearman, and a bunch of other prominent software packages; authored the first version of the OpenID spec (which eventually became OAuth, which you see all over the web); and was one of the early…
It’s amazing how this is the first time I have heard his name. Great people basically disappear under the Google name.
It's interesting how fleeting software fame is. Perhaps that's just a special case of how fleeting fame is. Folks who came of age in the early 2000s certainly remember him - he founded LiveJournal; wrote memcached, MogileFS, Gearman, and a bunch of other prominent software packages; authored the first version of the OpenID spec (which eventually became OAuth, which you see all over the web); and was one of the early…
It’s amazing how this is the first time I have heard his name. Great people basically disappear under the Google name.
It's interesting how fleeting software fame is. Perhaps that's just a special case of how fleeting fame is. Folks who came of age in the early 2000s certainly remember him - he founded LiveJournal; wrote memcached, MogileFS, Gearman, and a bunch of other prominent software packages; authored the first version of the OpenID spec (which eventually became OAuth, which you see all over the web); and was one of the early…
Earlier quoted context omitted.
Google C++ doesn't allow using exceptions and therefore requires broken instances from failed constructors.
Google C++ tends towards the convention of constructors that do only cursory initialization to a sane but non-functional state, things that almost-always succeed (and assert on failure), with the "real" initialization pushed to an Init() or Start() function.
The preferred pattern now is to use factory functions that can return either a fully-initialized object or an error.
Earlier quoted context omitted.
> When can this fad end It's not a fad, businesses aren't doing this just because it's trendy and cool and they think people will like it, they're doing it because it saves them a fortune and they care more about their bottom line than their employees well being.
That fortune's pretty small, really. About $5,100 per employee, per year. It would take a lot of employees for that to even be a noticeable line item for a company with profits in the billions. It saves an average of 40 square feet (65 for open office, 100 for an individual office), plus a couple of thousand in construction costs. So, at around $100 per square foot per year (figures vary wildly, but I saw a couple of…
Earlier quoted context omitted.
More than that, the guide limits C++ usage to a safer subset of features.
C++ relies heavily on RAII. Exceptions are safer than broken instances from failed constructors.
Not every error is exceptional so not every error should use exceptions. This is especially important in lower level code where someone's exception is someone else's expected code path.