akdas

11 ms·

61.
Why men's health depends on feminism(avikdas.com)
4 points by akdas 6y ago|0 comments
62.
Looking for strengths is not lowering the bar(hiringfor.tech)
2 points by akdas 6y ago|0 comments
63.
by akdas 6y ago
Looking for strengths isn't the same as lowering the bar. If you have specific requirements, you will maintain those requirements. But, the goal is to push aside weaknesses that don't matter (such as nerves during an interview, or
64.
by akdas 6y ago
> Everyone loves to read and write about how developer interviewing is flawed, but no one wants to go out on a limb and make suggestions about how to improve it. I've spend this year writing about hiring[0], both to talk about the p
65.
Breaking down a one-hour interview(hiringfor.tech)
1 points by akdas 6y ago|0 comments
66.
How to improve your interview skills by doing your job(hiringfor.tech)
1 points by akdas 6y ago|0 comments
67.
How to Hire Junior Engineers(hiringfor.tech)
2 points by akdas 6y ago|0 comments
68.
Hiring junior engineers – when to hire them(hiringfor.tech)
2 points by akdas 6y ago|0 comments
69.
by akdas 6y ago
Not saying that fitting people into a small space isn't hard. However, children of immigrants are especially keen to assimilate into the receiving culture, so much so that they often go beyond what natives do. For immigrants and their
70.
by akdas 6y ago
I really like that style. It's related to the Inverted Pyramid style in journalism, meaning others have thought a lot about how to get important information up to the front of a piece of writing. https://en.wikipedia.org&#x2
71.
by akdas 6y ago
This post was inspired a recent HN discussion around GitHub and hiring[0]. I compiled some other relevant perspectives and also added my own about where GitHub _can_ fit into the interviewing process. [0] https://news.ycombinator
72.
The Private Programmer(hiringfor.tech)
2 points by akdas 6y ago|1 comments
73.
by akdas 6y ago
I've been writing about this topic for the last 7 months. The absolute biggest change you can make within the confines you presented is to switch from "looking for weaknesses" to "looking for strengths". I wrote abo
74.
by akdas 6y ago
Every interview is different. You're asking people to read your mind: https://hiringfor.tech/2020/03/02/are-you-asking-candidates-...
75.
Rendering Curves in 3D(avikdas.com)
2 points by akdas 6y ago|0 comments
76.
The prisoner's dilemma of training your employees(hiringfor.tech)
5 points by akdas 6y ago|0 comments
77.
by akdas 6y ago
> the compiler will guide you towards the completeness of all the functions in your codebase that match over your type. So this burden is not on the programmer. That only works if all the functions you care about are in one codebase. If
78.
by akdas 6y ago
> The "problem" in each case is that you have to modify code in a bunch of different places instead of one place. And by extension, different places include ones you don't own, and therefore can't change. For example
79.
by akdas 6y ago
I haven't fully read through the paper, but it looks like an important part of the technique is that the light acts like a point light at each point in time. For example, the projector will emit certain patterns of light, like in Figur
80.
Open book tests – accessing the internet during technical interviews(hiringfor.tech)
2 points by akdas 6y ago|0 comments
81.
How fair is the take-home assignment?(hiringfor.tech)
1 points by akdas 6y ago|0 comments
82.
Reducing interview stress with independent work(hiringfor.tech)
1 points by akdas 6y ago|0 comments
83.
The programming language doesn't matter(linkedin.com)
1 points by akdas 6y ago|0 comments
84.
Barebones 3D Rendering with WebGL(avikdas.com)
1 points by akdas 6y ago|0 comments
85.
Tech interviews fail those with hidden disabilities(hiringfor.tech)
1 points by akdas 6y ago|0 comments
86.
Executing code virtually during an interview(hiringfor.tech)
1 points by akdas 6y ago|0 comments
87.
by akdas 6y ago
I actually think the other resources, including WebGL fundamentals, are really great. But whenever I tried reading them, they just didn't click for me. I don't mind organizing the code. I just want the barebones in the beginning.
88.
by akdas 6y ago
100% agreed that I'll be writing abstractions as the program grows. But without understanding the underlying APIs, I don't know which abstractions to write. As another commenter asked: what does "DSA-like helpers" mean i
89.
by akdas 6y ago
Thanks for the heads up. I actually did look at that reference, and in particular, the WebGL State Diagram is fantastic. Unfortunately, it still uses some helper libraries that, for me, obscure the core APIs. That said, WebGL Fundamentals i
90.
by akdas 6y ago
I bet! I'm fortunate enough to understand the concept of shaders, and how GPUs work generally, so at least that's one concept I don't have to learn. The APIs, however, are another beast altogether.

More ›