akdas

8 ms·

31.
by akdas 5y ago
Nope. Feminism is about valuing people as people, regardless of what gender roles tell us about how to judge them. What you're talking about is a gender role, which is explicitly what feminism is against.
32.
by akdas 5y ago
I wrote this article because the experience of these transgender men add to my own personal experiences, sometimes affirming my experiences, sometimes providing a new perspective. I have written other articles before from my own perspective
33.
by akdas 5y ago
This is exactly why I expanded on the original article! I have been advocating for all the same interventions, but to hear it from those who have experienced both worlds is a great affirmation of my one-sided experience.
34.
by akdas 5y ago
I don't think the quote in my article suggests you need to want those spaces. But I do. Cotten does. And it's hard for us to find those spaces.
35.
by akdas 5y ago
This is another reason we need to be fighting for economic reform. Divorce will never be pleasant, but ensuring economic self-sufficiency for everyone , at least finances will be out of the picture in these separations. Another way for us
36.
“It's not peaches and cream either for men”(avikdas.com)
120 points by akdas 5y ago|167 comments
37.
It's okay to not be okay(avikdas.com)
4 points by akdas 5y ago|0 comments
38.
by akdas 5y ago
For sure! Because this was for my own use, I need to put in some documentation for it to be useful for others. That, and pick a name :) It's all on my TODO list. You're right: if you don't control the server, you basically ca
39.
by akdas 5y ago
Writing it myself is what I did for my blog. The only thing I capture is the page that was visited, when it was visited, and the domain of the referrer (to see what the source is). The tracker is meant to be used for blogs where I don'
40.
by akdas 5y ago
100% agreed. The translation from source code to 3D visualization was ultimately based on choices we made, not on the inherent structure that already was put in place by the developer. The output was still valuable, but when the developer h
41.
by akdas 5y ago
I haven't worked on the project in a while, so I can't comment too much on the current status. But I'm happy to talk about what I learned, the challenges I faced, etc. if you have any questions about those. The multiplayer as
42.
by akdas 5y ago
> I think 3-D visualizations of 1-D languages (all our current programming languages are 1-D) will not be so helpful, as you will be looking at transformations, not the actual code as it exists. This is the part that I disagree with. The
43.
by akdas 5y ago
I worked on something like this a few years ago, only in VR so you could walk around the visualization and use your spatial recognition abilities in 3D. One part we struggled with was evolving the visualization with the codebase. I see in t
44.
by akdas 6y ago
Last year, I wrote about the prisoner's dilemma of training your employees[0]. As Mark points out, many companies don't invest because they don't find it valuable. What I tried to point out was that big tech companies already
45.
In hiring, one size does not fit all(hiringfor.tech)
2 points by akdas 6y ago|0 comments
46.
Formal Interview Training(hiringfor.tech)
2 points by akdas 6y ago|0 comments
47.
Interview Apprenticeship(hiringfor.tech)
1 points by akdas 6y ago|0 comments
48.
by akdas 6y ago
Thanks! That newsletter does have articles geared toward candidates as well, though a lot fewer. The topic of what to ask at the end is one I floated around, but I didn't find it to be a priority. In an ideal world, the questions at th
49.
by akdas 6y ago
> After performing over 100 interviews: interviewing is thoroughly broken. I also have no idea how to actually make it better. This has been my gut feeling for a long time, and in the last year, I finally took the time to write down my t
50.
Interviewing and Pattern Matching(hiringfor.tech)
1 points by akdas 6y ago|0 comments
51.
Technical skills every software engineer interviewer should have(hiringfor.tech)
2 points by akdas 6y ago|0 comments
52.
Prepare your story – introducing yourself in interviews(hiringfor.tech)
2 points by akdas 6y ago|0 comments
53.
by akdas 6y ago
You know what your job is: to figure out the problem. And the interviewer should be clear they are looking for you to figure out the problem to solve.
54.
by akdas 6y ago
Absolutely, that's something I pointed out in my writing: if the interviewer doesn't explain their expectations, you can and should ask. Interviews work best when both parties are engaged heavily in the success of the interview.
55.
by akdas 6y ago
Huge +1 on explicitly setting expectations. I've written on this topic[0], and there are a lot of different ways interviewers don't set expectations: - Is the interviewer looking for syntactically correct code, or general algorith
56.
Writing Good Interview Feedback(hiringfor.tech)
1 points by akdas 6y ago|0 comments
57.
Getting to know the candidate before the interview(hiringfor.tech)
1 points by akdas 6y ago|1 comments
58.
Vulnerability, Leadership and Paternity Leave(avikdas.com)
1 points by akdas 6y ago|0 comments
59.
Having Something to Show(hiringfor.tech)
1 points by akdas 6y ago|0 comments
60.
Trick Questions and Partial Answers(hiringfor.tech)
1 points by akdas 6y ago|0 comments

More ›