HN user

getaclue

-2 karma

not a software engineer

Posts4
Comments33
View on HN

Thanks for sharing this; I've only skimmed it but it seems to hit some of the common issues right on the nail. Definitely a useful subject matter. Now we just gotta make the management read it ;-) I like the checklists and the questions to ask sections. The appendix also seems to ask relevant questions and provide proper guidance. I'd be interested to hear from a non-technical person to see what they think of it. Cheers

Pains me to see CBC go down this path - from their recent modernization changes that made their website unusable for basic things like news, to seeing comments like this. Makes me wonder why "non-tech" companies just copy tech companies that are able to innovate and move faster without considering their own fate. But then I remember how they work and that every company is now a tech company at the apparent mercy of FAANG. I'm seeing a lot of talk about our neighbours down south but not a lot of action. This piece made it seem like CBC is losing a piece of the pie and they are salty. Makes me feel sad to see this from the top down. We have the same tech available and the similar resources but it seems that we would much rather partner or purchase than take some risk and try something different. I hope I am wrong.

Well to take a step back and evaluate the question of "who needs ds" - most answers to typical problems come down to using a hash table or an array... or some trickery of both. So... I can see this question as being useful.

I am afraid that I am missing the point of why YOU chose this approach if you can't answer this question. No offense to you. It seems like you came from the approach that if people want this job they will do this thing. Seems noble and with good intentions.

But DS is much more than that. It is the basics. The definition. The building blocks. Lots of reasons why you would want to ask about it.

I've actually been asked something similar prior to working at IBM. My caveat was that this question was asked in the interview without any preparation.

However, I can see how some people would find this challenging. It may seem like a lot of work for some people. Especially if you worked with some engineers that freak out when such a task is presented. If they don't have an outline, a set criteria, the protocols, previous samples, and the such. then you will have a bad time. Such people approach problems very systematically. As long as your task is clearly defined and has such things, then it should be easier in theory.

The people who aren't phased then won't be phased. The people that may see this as challenging shouldn't also be phased. Finally, considering monetary incentives for such additional work could smooth out some issues. You could pose such things as an investment and a risk mitigation strategy to your elders.

Anywho, these are some thoughts.

Interesting view point. Haven't thought about it like this before.

Anecdotally, I am finding more of these people in indie development. Making their own thing or working with like minded people.

I used to look to Google/Facebook for experts and people to follow. Now, I look elsewhere.

As someone who is currently looking for a job I can definitely relate to the troubling HR in software field. What I started doing is working on my own content to help recruiters decide if I am what they are looking for. I added more information about ME, what I am passionate about, what I was passionate about previously, and what I am looking for to my about page (https://getaclue.me/about).

This way, recruiters can decide if they like me or not. Another thing I started doing while reaching out to companies is saying that I am open to 3-6 months "tryouts" if you wish.

I feel like we should have more of those. I also realized that social media is very powerful for finding your way in 2018. Gone are the days of wanting to work at a Fortune N company because they are doing great work. Most of those unicorns turn into corp machines that they were trying to stay away from.

Another thing I started doing is looking for people that share my passion. Anecdotally, Forums, IRCs, Telegam and the such communities are definitely booming once again thanks to the dissolution of privacy.

One challenge - esp if you are someone who cares about software and software engineering field - you have to do A LOT more work on your own. I work full-time and I work when I get home. I don't see this changing.

EDITed to add some \n

If you are in it just for having a job and an income - then having a degree is not necessary. If you want more then it is also not necessary but helps a lot. Make a pros and cons list and decide for yourself. But make a decision. I picked engineering instead of CS and do not regret. But I was looking into application of CS. Be mindful that engineering is not particularly easy but definitely doable.

Nice job Brett. Logged in just to make a suggestion. If you haven't considered the enterprise angle - I can see this being useful in creating enterprise video content. Specifically for making e-learning content and such similar things. You don't know how much this space lacks in proper tooling. Having said that, I can see some challenges if you have considered or are considering. I can shed some light if you like. Or if not, best of luck =) Useful!