nitely

11 ms·

61.
by nitely 7y ago
Sure, adding meetings that affect the whole team instead of addressing someone's lack of communication is the way to go.
62.
by nitely 7y ago
Well said. Trust falls bring great value as well.
63.
by nitely 7y ago
This assumes people don't communicate when they get blocked, but wait 24hs to announce it in a meeting.
64.
by nitely 7y ago
Does your team communicate outside of the stand-up? I usually know what everyone is working on (because of ticket assignments, code reviews, some occasional side meeting, etc), as I usually work with teams of 5 (or less) people.
65.
by nitely 7y ago
First look up the definition of a lock and mutual exclusion. There are two types of basic locks: mutexes and semaphores. Both keep two threads or coroutines from executing a block of code/instructions at the same time, and both work in
66.
by nitely 7y ago
Even the original solution is a lot more complex than just checking some primitive value. A lock is still needed when doing concurrency on a single thread, which is the point I'm making anyway. > Long story short: Your problem is wi
67.
by nitely 7y ago
No, I didn't. That's how a lock works. Only one coroutine (or thread) is allowed to hold it at a time while the others must await their turn. A state machine is a lot more than a boolean variable.
68.
by nitely 7y ago
If the callback throws an error, none of the awaiting coroutines will run, and adding a catch would break the callback error propagation.
69.
by nitely 7y ago
That would unblock all coroutines waiting for the promise, instead of just the first one. It's not that trivial, that's the point.
70.
by nitely 7y ago
Since booleans can't be awaited until their state is negated/toggled, I'd say a lock that works like a lock is needed.
71.
by nitely 7y ago
> This assumption is false. Either the flows are written in code, are you have to have them in your brain every time you are reading some code which can handle 10 flows. No, it's not. Your interpretation of it is wrong, though. No c
72.
by nitely 7y ago
Well, I'm amazed they allowed you to run the code at all. In an interview you are expected to test the code by going through it and write the state of the program as you go (i.e comments about the state of some variables in each iterat
73.
by nitely 7y ago
> the places I’ve been are less formal than that and they might be concerned about slowing down turnaround times during the day I'd be more concerned about code being committed to master without code review.
74.
by nitely 7y ago
I can see how this would work for software boutiques doing fairly similar projects each time, or projects with very similar parts, but not in complex products. Much less for software that does not use any kind of framework or follows any ki
75.
by nitely 7y ago
Sure, but here it's a local mutation, it won't leak to the rest of the program. There is nothing wrong with mutating acc in reduce.
76.
by nitely 7y ago
7 hours of meetings? did people show up the next few days for work?
77.
by nitely 7y ago
You are not alone. Meetings just suck all the energy out of me.
78.
by nitely 7y ago
This. There are plenty of backward incompatible changes in every minor version bump.
79.
by nitely 7y ago
Well, maybe if someone record it and put it on social media. Otherwise, I doubt it. Actually, even then I doubt it, I've never seen it happen. From the article, it does not look like they got fired.
80.
by nitely 7y ago
They were drunk, so probably not at work. Not saying it's right or wrong. But probably less wrong.
81.
by nitely 7y ago
There are always unforeseen requirements or some requirements are very loose because there is really no way to know something will work until is tried. If there were any protocol that requires discussion about every little thing you would n
82.
by nitely 8y ago
The article is a rant about bad code, not about bad teammates. Maybe they were hired because the manager liked them for having people skills instead of actually being good at their jobs. I agree communication is an important part as well, t
83.
by nitely 8y ago
How many nights and weekends should be uselessly wasted on homework for every interview? At least whiteboard requieres practicing for real once in a life time.
84.
by nitely 8y ago
The pythonic way is to do duck typing, meaning don't check the params types at all. Assertions are ok to check things that should never happen. But if you're gonna put them everywhere then better use type hints. I'd use TypeE
85.
by nitely 8y ago
Make mypy type checking part of the CI pipeline. Done.
86.
by nitely 8y ago
> Simplifies refactoring tools. How? we would just have case insensitive refactoring tools. > Encourages a consistent style in the ecosystem from the beginning. Python, C, Java, etc are case sensitive langs, and it's possible to
87.
by nitely 8y ago
I've aced every whiteboarding interview when the problem was the same or similar to some problem I solved before, and I failed pretty much every interview when the problem was new to me (except when the problem was trivial, ala fizzbuz
88.
by nitely 8y ago
0-9 is defined as a [ascii] range, so you are correct.
89.
by nitely 8y ago
I think parent means that even if you "sign a contract assigning all IP to their employer", you can still write OSS code in your free time, since there is no way your employer will find out, and even if they do, they've no wa
90.
by nitely 8y ago
Some of the syntax is similar, but similarities end there. Nim was inspired by many languages: Modula 3, Delphi, Ada, C++, Python, Lisp, Oberon, C# and Pascal.

More ›