Something funny i saw

Lol, where did you see it ??

I think I've seen the image on Medium.

And after the interview you wouldn't see anything like that again when you actually working there

Deicide:
And after the interview you wouldn't see anything like that again when you actually working there

Personally my own take is as an Engineer you should still know it, especially when you move to bigger careers as you climb it is very important unless you shift to the Business side.

qtguru:


Personally my own take is as an Engineer you should still know it, especially when you move to bigger careers as you climb it is very important unless you shift to the Business side.

I think it's more important to learn and understand design patterns.

Deicide:
I think it's more important to learn and understand design patterns.

With some companies it's not up for discussions and it makes one a better developer. but depends on the job sha.

I used to say that data structures and algorithms isn't important but na lie o. See as a junior to mid level Dev it's very very important to learn data structures and algorithms regardless of what you do. Let's even leave job aside, you need solid knowledge of data structures and algorithms to do your day to day job. Building solid infinite scrolls In react require you to know graph traversal very well and I am talking of small scale projects o not large projects that are serving millions of users.

Now even in platform Dev I used to tell qtguru that you don't need DSA thats a big lie. You need DSA to write efficient code in platforms even more than general development as this platforms are very restrictive with how data is pulled and manipulated. Take Salesforce for instance. Just two for loops will throw errors all over the whole code base and this is for a small org with like 20 contacts. Imagine working on a large org that has like 1 million contacts writing double and triple four loops. You won't last a week on the job.

I started learning DSA and taking it seriously and I implore every junior and mid level Dev to do so too. Not just for a bigger job or money but for your growth.

tensazangetsu20:
I used to say that data structures and algorithms isn't important but na lie o. See as a junior to mid level Dev it's very very important to learn data structures and algorithms regardless of what you do. Let's even leave job aside, you need solid knowledge of data structures and algorithms to do your day to day job. Building solid infinite scrolls In react require you to know graph traversal very well and I am talking of small scale projects o not large projects that are serving millions of users.

Now even in platform Dev I used to tell qtguru that you don't need DSA thats a big lie. You need DSA to write efficient code in platforms even more than general development as this platforms are very restrictive with how data is pulled and manipulated. Take Salesforce for instance. Just two for loops will throw errors all over the whole code base and this is for a small org with like 20 contacts. Imagine working on a large org that has like 1 million contacts writing double and triple four loops. You won't last a week on the job.

I started learning DSA and taking it seriously and I implore every junior and mid level Dev to do so too. Not just for a bigger job or money but for your growth.

Exactly you get.

Learning algorithm will require you have some knowledge in discrete mathematics topics like logic, number theory, induction and recursion, cryptography, set, matrices, probability, graph, all bunch of topics that sum up to discrete mathematics. Learning them can be daunting. You will need them for design and analysis of algorithm, actually.

parkervero:
Learning algorithm will require you have some knowledge in discrete mathematics topics like logic, number theory, induction and recursion, cryptography, set, matrices, probability, graph, all bunch of topics that sum up to discrete mathematics. Learning them can be daunting. You will need them for design and analysis of algorithm, actually.

Probably topics under discrete mathematics are hardcore programming topics on their own. Some programming languages don't even have loops so everything looping needs to be done with recursion.

parkervero:
Learning algorithm will require you have some knowledge in discrete mathematics topics like logic, number theory, induction and recursion, cryptography, set, matrices, probability, graph, all bunch of topics that sum up to discrete mathematics. Learning them can be daunting. You will need them for design and analysis of algorithm, actually.

Yeah I feel 6 months is okay however if you want to learn for interviews you can learn some, most companies repeat the same question or use code-recruitment.

Syncy:


Hi qtguru.
Do you mind if I try the Yoruba translation gig?

Already sent someone, but I will let you know if anything changes.

Syncy:


OK.



Please, how do I bypass purchasing a product key to activate Microsoft Office?
The apps are refusing to work without the activation.

go to DirectOnPC but mine is paid because it is 3k monthly for Family plan

qtguru:
Something funny i saw

I seems to understand you deeper than you think,I know your challenges and I would have been of help but I pray your woman understands you perfectly and help feel your void.Oya show us your six packs na abi you just dy go gym without six packs?in response to your diary updates. You overwork yourself too much.

wahalla no dey finish for this programming.... there's just a ton of things to learn. I code day and night but each time I say make I chuke eye for here na different things to learn just yakpa

tensazangetsu20:

Probably topics under discrete mathematics are hardcore programming topics on their own. Some programming languages don't even have loops so everything looping needs to be done with recursion.

I don't really like the idea of doing everything with recursion unless the requirement is baked into the language. Languages like Haskell make functional programming a requirement. And there's even a trade-off because function calls are expensive and recursion is not exactly easily readable. I like the approach of JavaScript, different approach for different problems. Sometimes array.map(iterative) makes sense, other times you need array.forEach(iterative) and other times you need array.reduce(recursive). when all you have is a hammer, everything looks like a nail.
Buy the idea of pure functions is cool because it makes automated testing way easier since you try to avoid side effects in your functions but at some point you'll need to write to db and that's a side effect you can't avoid.

Can anyone do a quick tutorial on induction and recursion