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.
109 karma · joined September 18, 2018
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.
It's a big green flag from my perspective.
(I'm not doing anything)
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...
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!
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.
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.
On mobile we work with pretty high-level abstractions, so if you did this yourself, most of the new stuff to you would be the frameworks like UIKit or Core Data (at least on iOS).
Edit: Ray Wenderlich and objc.io are my go-to learning resources for iOS stuff
Having just had a taste of dystopian future injected straight into my veins, my irritability was at a peak, so I tried to quickly pass through behind someone else. Fuck it, I have my transfer I paid for anyway right?
A lady in the city's transit uniform instantly appears from behind the fare box and asks me what the hell I'm doing. I avoided trouble, but, well, I don't even know what to say really. It is just so absolutely bewildering and upsetting to have no human in uniform to go show my transfer to, but faster than I can snap my fingers does one appear to be the muscle.
Capitalist power structures will forever invent stupid shit for humans to do. The rich and powerful seem to prefer it this way, because whatever the hell it is for them that replace the simple joys of friends and family, is something that can only be appreciated when others can't have it. Diamonds.
I disagree. I don't believe there is a single good reason for why our world has both trillions of dollars of wealth but also people without access to clean drinking water. It's just not right.
You're right, it will build up a grudge that gets launched uphill. That's what I did, after letting my manager litter my codebase for months until he made the big mistake of telling me to shut my mouth, giving me a reason to go to HR.
That was almost a month ago. Currently struggling with the realities of unemployment and depression. Not sure where things will go from here. I haven't discovered any kind of support system for software developers who left their jobs because of their personal morals.
return config.github ?? config.twitter ?? default