coffee

8 ms·

31.
by coffee 6y ago
The bigger problem that I've run into is that most employers don't know how to recognize talent.
32.
by coffee 6y ago
> Here's to hoping we both come away from this slightly better than we entered That's very funny to me :-) > my original reply to you was probably a bit snarkier than called for > At the time, I thought it warranted >
33.
by coffee 6y ago
This is reaching far beyond the context of the article, and the comments replying to it with this example.
34.
by coffee 6y ago
This reply makes far less sense now that mistrial9 edited/updated their original statement without attributing that fact :-\ It's been toned down for sure.
35.
by coffee 6y ago
That is not an accurate representation.
36.
by coffee 6y ago
Some of the best people I've had the honor of hiring, and some of the best jobs I've had the privilege to be offered, never once involved opening a code editor, sharing a screen, reviewing any code, completing a take home project,
37.
by coffee 6y ago
> Your line of argumentation seems to argue the opposite Hmmmmm... I'd say that "my point of view" differs from yours, and does not fall in line with common group think. Cognitive biases are typically pushed back on, even
38.
by coffee 6y ago
> I think many companies through the hiring process completely lose sight of what they are actually looking for I think you're right about that. But I've also seen (from both sides of the table) that many companies also have no
39.
by coffee 6y ago
Wow. This response (and how you responded to it) really illustrates, to me, the problem with hiring in the first place when placing those hiring choices in the hands of engineers that don't have hiring skills. > What's the pain
40.
by coffee 6y ago
You pulled out one small statement and ran with it. The problem is it's out of context with the rest of what I said. Also, there is far more history than what you just outlined which falls into "folklore" and "cult of pe
41.
by coffee 6y ago
> If you are expecting a candidate to have a certain skill-set, having a simple timed coding test as the first round is the easiest way to filter out a lot of unqualified candidates. Stripe does this quite well for example. The problem i
42.
by coffee 6y ago
> They were given two (!) weeks to complete a simple task. I saw no excuse for not delivering. So you're saying that in your worldview, it is 100% acceptable for a pre-interview candidate to spend a full 2 weeks (or even a significa
43.
by coffee 6y ago
> the company is not entirely to blame here... I clearly hear what you're saying, and I understand your stance on it. But I can't agree with it. The burden is on the folks hiring in my opinion. This is not a "real life&quo
44.
by coffee 6y ago
> I think the problem is that in our industry you have many companies where you have 24yo, managers, or even folks under 26 with Director of Engineering titles, and they don't have either the experience or knowledge to sift through
45.
by coffee 6y ago
> This entire post is why I quit the interview circuit as a person with ample prior relevant work experience. It is really bad. Removing yourself from it is probably a very healthy choice. There's so much folklore, cult of personali
46.
by coffee 6y ago
No, I didn't misread the end. I understand it (along with the rest of the post) very clearly.
47.
by coffee 6y ago
> you have a very tangible chance of spending 12 hours doing it and hearing nothing back at all ...which is so very frustrating. It's painful to read things like this: > That was all we asked; we intentionally left it open-ended.
48.
by coffee 6y ago
My takeaway was the author learned how to better interview, by not giving code tests, but instead to begin engaging in a discussion with someone.
49.
by coffee 6y ago
This is so painful to read... > That was all we asked; we intentionally left it open-ended. > I let them know there was no time limit or minimum for how many hours they had to work on it > But then over the next three paragraphs,
50.
by coffee 7y ago
> Because business is mostly about sales and marketing and not so much about the product. That's not been my direct experience. Actually, very much the opposite for myself and many others I know who are software engineers building t
51.
by coffee 7y ago
> Fun about what exactly? If you mean farming to Upwork, not building is not fun for engineers. Nope. Never said anything about "not building." Only you have stated that. This circles back to my original question/statement
52.
by coffee 7y ago
As an engineer, what is fun about it? From your statement it would be "something fun to build." I wonder why building a business and building a piece of software are so different, and why one is fun while the other is not.
53.
by coffee 7y ago
That's a bit snarky. I've been engineering software for a long time and I've never come across a code base (associated with a successful product) that was debt free.
54.
by coffee 7y ago
For anyone without a Medium account, here is the source: https://www.reddit.com/r/funny/comments/epi5wq/amazon_accide...
55.
by coffee 7y ago
It doesn't matter. I'm not arguing the chronological order in which layers of abstraction have been created and when, just that this is fact. And if this is fact, why not this as the next layer?
56.
by coffee 7y ago
> Cynically? No, not cynically :-) > Because people were also selling "no code" ten years ago, or even further back. Not really sure it matters when it starts. Sometimes markets aren't ready and products are too early.
57.
by coffee 7y ago
> I want some no-code to make me feel for my career a bit. It sounds like your career is software engineering, if so... > My personal feeling is that any no-code tool should be useful enough that I would use it. Someone who's a s
58.
by coffee 7y ago
> I think those with a programming background take terms like "no code" far too literally. Agreed. Poor term. But what these platforms can accomplish is liberating for those who can't code yet want to get something live on
59.
by coffee 7y ago
> If there was a faster and easier way to develop software, we would be doing it. We are already using the easiest to understand tools we can find to develop the best software possible. Not really. As we evolve software development, hist
60.
Alternative Funding Calculus: A Quant Comparison of Tiny, Indie, and Earnest(medium.com)
31 points by coffee 8y ago|6 comments

More ›