metalgearsolid

I have a similar story, but it was my first programming job, and it wasn't a cake-walk to get it, so for myself I simply couldn't imagine doing much better. And to be honest, after quitting, I haven't. I'm at least healthy and happy again.

But you're right, honestly the only thing I really learned about that experience was I should have just quit sooner. That's really all there is to it.

I would definitely hire them. I don't see it as a lack of commitment, rather he/she just understands the value of their time. 24 hours of labour is NOT 60% of a full work week, especially for a knowledge worker.

It's a big green flag from my perspective.

I stocked up on this new limited edition Eggo cereal, as it is the spiritual successor to the long forgotten Waffle Crisp, the #1 cereal from my childhood. Honey Comb simply does not compare, don't even bother mentioning it. If things start getting scary, I'll stock up on some milk.

(I'm not doing anything)

Being anti-Veblen is not the reason I dislike Behringer. It's not so black and white when it comes to cloning or replicating original designs of the past. It can be done tastefully. Behringer does not do their clones with integrity.

Isn't that the point though? That sweeping things under the rug in order to save face is what allows these issues to spiral out of control.

To answer your question: objc.io

Facebook is really big so lets treat it as such, and look at things piece by piece. Start with treating Facebook's NEWS FEED as a newspaper perhaps, then move on to other problems like hate groups using facebook to organize, marketplace fraud, etc.

Been there. Anecdotally, a good indicator of a feature factory is the turnover in marketing, a particularly gruelling department to be in when you are not finding any consistency with the message you've been tasked with communicating. That kind of situation is okay and perhaps even fun if you can count your colleagues with your fingers, but at companies larger than that, the general lack of understanding of what your software does is a kind of debt, perhaps even classifiable as technical debt.

I tried to raise red flags to my bosses when our colleagues in customer support we're making feature requests for features we already had. The company as a whole lacked the courage or enthusiasm to tackle those design flaws, and instead would request additional features. I tried really hard to fight for removing features too...

It's nice working on any well known product really. I spent 3 years with a tiny startup doing enterprise software, and I can hardly even explain it to other employers, because hell, not even my own boss knew what he was trying to sell. We just had some kind of survey builder platform with a mess of features that was starting to stick with people.

Finding my 2nd job is just as hard as getting the first one, as the product I helped develop is just not that interesting. It would be so much easier to just say I worked at Google, Airbnb, Apple, whatever. I'd be upset, but I don't want to work for a FAANG regardless.

Good luck!

I think brining usenet back is problem solving in reverse. Usenet will not bring back the joys of early internet, but attempting to revive an old technology through the collaboration of other curious and passionate people certainly will.

I honestly never noticed I was scheduling my time in half-days or even full days, but it's so true for myself. I would've thought it was some sort of anxiety thing, but having plans several hours away in my schedule is extremely debilitating to my creative flow. Just one scheduled item, even something enjoyable like going out to a nice restaurant, can practically paralyze me from working on stuff. Fortunately chores, errands, and house work generally do not fit this bill.

Or rather it prevents me from venturing into the unknown, like when working on a novel program or writing music from scratch. I really had no problem accomplishing day-job things despite knowing I had scheduled meetings later on in the day.

I'm pretty apprehensive about this "callAsFunction()" feature. Requiring users to name things in a specific way was the kind of awful UX our customers struggled with when using our hobbled-together marketing software.

IMO, some better alternatives, in order of personal preference:

* Give away the functionality to all types that implement only a single function.

* Require an explicit protocol conformance. I get that the language does not want features to be hidden away, but requiring a user to implement a function with a specific name and signature is literally the job of a protocol. It doesn't seem like much of a hurdle for non-beginners, who have likely been familiarized with core protocols like Sequence or Collection, to acquire a knowledge of a CallAsFunction protocol.

* Introduce a new keyword, or tag (like @implicit).

* Allow the user to unlock the functionality through a more obscure phrasing. Even something as ugly as "func ` `()" could be preferable.

The answer to both questions is yes. A bootcamp helped me because it put me into a collaborative environment where I had some kind of obligations to show up and complete projects. Ultimately, you really only need side projects. I'm actually struggling in my job search right now, despite getting my foot in the door and doing great work for about 3 years, as having one company on my resume is not making up for my lack of newer side projects.