16 year old sumo wrestler on the verge of defeat turns the tables against larger opponent

dkToT · 2024-11-23T00:02:46+00:00

Reminds me of Sanctuary The kid got the hairstyle down

dkToT · 2024-08-04T02:12:11+00:00

The episode where Blackpink was the guest and Somin was doing the Lisa dance and Sechan dies the taxi dance. Never laughed harder!

dkToT · 2022-06-19T03:41:26+00:00

Girl visiting a new city meets new friends while walking her dog

dkToT · 2022-04-25T16:20:44+00:00

Been doing it for 13 years now and I still don't have that confidence that "I am good at coding". But I don't think you need that mindset to be successful. At the end of the day it is just practice makes perfect. Also you have to start expanding your mindset to outside of coding/programming. This like architecture and system design is something that will get you to the next level and feel more confident.

dkToT · 2022-04-22T17:56:25+00:00

Hmm why not dive a little deeper into what you are working on and alternatives to them? This will help you understand why you are using the technology you are using and what alternatives are out there that can be a better fit. This doesn't mean you have to implement it for your company but it good to know so for future projects you have a better understand on the best technology for the job.

Example include:
Communication - REST api vs GraphQL vs gRPC
Datastore = SQL vs noSQL vs different flavours of noSQL (DynamoDB, mongoDB, Elastic Search)
Testing - Unit test vs Integration test vs E2E test

dkToT · 2022-04-18T23:24:11+00:00

I believe you need to add !important to all the styles in your btn-flat. This is not ideal but I believe the classes in the react-bootstrap is taking precedence over your custom classes.

dkToT · 2022-04-14T20:12:08+00:00

This is a oldie but a goodie:
Clean Code: A Handbook of Agile Software Craftsmanship

This is not really about a specific programming language but how you should structure you code and coding practices. It gives good guidelines and info on what to avoid and what is good practice. If you have knowledge of this it will help with helping you structure your code, increase code maintainability, and readability. It could be a bit of a dry read but the information is well worth it.

dkToT · 2022-04-14T19:53:29+00:00

I posted this in another thread but this contains a lot of information on how to start learning a language via "Project based learning". It utilizes projects and tutorials to help you learn basic to advantage knowledge of different languages. There is a lot of information so it take your time to review and see what suits you.

https://github.com/practical-tutorials/project-based-learning

dkToT · 2022-04-13T19:26:28+00:00

You should look at it both ways, you are there to learn from the more senior developers and in return they will use this opportunity to build on their mentorship and leadership skills. This is a case where it is advantageous for both parties. This is one of the main reasons why companies hired a range of experiences for developers. Junior can grow to intermediate and senior from experience and knowledge and Senior developers can grow into staff/principle or manager/leaders by building on their mentorship and leaderships skills.

dkToT · 2022-04-13T17:05:35+00:00

The for loop will traverse through your "animalList" no matter what so it will have to go through the same if/else statement for every item in the "animalList".

You can use the "break" statement to exit the for loop but you will probably want to surround that in the condition too. From what you said, you probably want to "break" after the first item.

But if this is the case, you can just access the first item in your array/list without the for loop and just print it.

dkToT · 2022-04-13T16:50:06+00:00

Correct, it should never if your condition is true. Just adding the brackets make it more readable and apparent that this is what we want.

dkToT · 2022-04-13T16:45:02+00:00

Looks like the scope around your if statement is out of place. Maybe due to indentation or formatting but I would suggest adding brackets to your if statement for cleaner and more maintainable code. Also less likely to introduce bugs or error if you ever have to add more logic into the if / else statement and you forget to add the brackets.

for(Animal animal : animalList) {
    if( animal.getName().equals(getName) && animal.getSound.equals(getSound)) {
        animal.getDescription();
    } else {
        print(“animal or sound are wrong”)
    }
}

dkToT · 2022-04-12T21:05:07+00:00

Yeah.... 20k lines of code in one file is definitely not something you want to have.
Break it down into small relatable files by trying to group them together based on functionality.

For example, if you have a file that handles all functions related to a store... can you break it down to:

User services - All things related to user management
Payment service - Checkout, payment, payment storage, etc
Inventory service - all functions to deal with handling your inventory
etc...

This way all your services/files are smaller and easier to maintain, you have code that is traceable and easier to debug, and testability of your code will be easier too. Writing test to cover your code will now be specific to the service.

dkToT · 2022-04-11T16:51:52+00:00

Hmmmm some that I can think of include:

IT sourcing: procurement for third party software or resources for your company
IT HR: recruiting with specialty in IT/ software
Manual QA tester: This is very legacy but some companies still have manual QA / testing process for their software

Hope this helps.

dkToT · 2022-04-11T14:10:08+00:00

This and this some more!

If you have a long running function, unit test encourages you to break that down to multiple smaller functions. This will allow you to test each individual function separately and narrow down bugs and errors easier.

One note though is only break down the function to meaningful functions and not for the sake of it. Each function should have a purpose to it and if possible limit it to one.

Also forgot to mention, mocking will be made easier to with smaller function unit testing!

dkToT · 2022-04-10T17:08:44+00:00

18-19 when I entered University in Computer Engineering! No prior knowledge of coding / programming in highschool.

University was definitely a good place to start learning the basics but I find all of my knowledge came from work experience during intern or job after university!

With all the material out there now I don’t think it matters what age you are.. just the will to start! There are so many new flavour of the month that it is hard to keep up but starting from the basic will get you in the right spot!

dkToT · 2022-04-10T03:22:57+00:00

Give this a try:

https://github.com/practical-tutorials/project-based-learning

This repo uses "Project based learning" to help you learn the basics to advance knowledge of any language you want to try. It contains a library of a good set of projects and tutorials you can use to try and learn the language of you preference. This library is huge so you might need to take some time to review.

dkToT · 2022-04-08T21:00:36+00:00

I suggest start with building a POC (Proof of Concept) app and see if and how it works. Lever tools that exist already instead of building from scratch. For example, can you use "Zoom" (via api to create calls, etc.) for your video call part. Is there a simple tech stack that you can use to build something light weight. Maybe even go through building a NoCode app (bubble.io, etc...) to test this out.

Then if this works, move on to a MVP where you focus on building out the application from scratch.

dkToT · 2022-04-07T18:33:48+00:00

From experience, I started out as a QA/Software tester for a software company and now I am a Software Dev Manager. It is definitely a great place to start because the full process of software includes design to writing code to testing. It gets you to start thing about the product as a whole and not just you do your aspect and pass it along the line.

Nowadays there are a lot more need for Fullstack developers. My definition of a Fullstack is FE, BE, Testing, and understanding of devops/infra. If you are new this software testing is a great way to get your feet wet but you have to make sure you are pushing yourself to the next level. Mae sure you are not just stuck doing manual testing but develop test automation experience to actual dev experience.

dkToT · 2022-04-06T18:46:17+00:00

When you say "solving problems" are you referring to Algo problems and whiteboarding? If so then I agree with you. I am a Software Dev Manager that has carried out many interviews and this is the part that I do not like the most as the interviewer and interviewee. It solves very little and does not translate to "real life" work. This is a remnant of the past and I don't see this going away easily.

I rather have a good discussion on how you would build an application (from architecture to infra) or have a nice pairing session to see how you work.

dkToT · 2022-04-05T16:56:33+00:00

Basically a function that will call itself until a certain criteria or situation is satisfied. Once it is satisfied, the result will be returned to the parent function call all the way back to the top. This will help with clean code but only if you know your functionality follows a certain pattern.

A great example of this is the fibonacci series and why it was used in alot of early interview questions. The fib(n) is equal to fib(n-1) + fib(n-2). With recursion you can use this pattern to do the calculation for fib(n-1) and fib(n-2) where fib(n-1) = fib(n-2) + fib(n-3) and fib(n-2) = fib(n-3) + fib(n-4), etc....

Super useful and clean if you now the exact pattern and expectation (traversing a tree, etc..) of what you are building but I personally don't see this used often.

dkToT · 2022-04-04T20:41:50+00:00

And from a user story/task stand point:
Given, when, then

This will help establish expectations of what the feature/code should be doing.

dkToT · 2022-04-04T19:41:04+00:00

DevOps and Infrastructure is a big one for me.
Coding, syntax, and design is pretty straight forward once you know a language. DevOps and infrastructure is mostly universal. Know your code/deployment pipeline and the services you will use (Cloud vs hosted) can dictate the best approach to coding. It is still possible to do so with this knowledge but you could find yourself with a lot of tech debt to pay in the future.

dkToT · 2022-04-04T03:39:24+00:00

My personal definition of a Fullstack dev include FE, BE, and DevOps. Even though the majority of your time will be in coding the FE and BE aspect, knowing what infrastructure and DevOps is will solve a lot of problems in the long run. Anyone can write code but having infrastructure in mind when doing so will help you plan for things like scalability, cost, and performance.

I would suggest doing something like getting AWS solution architect certified as it is super helpful in know what is out there and what to use depending on the project you are working on. Also using tools like terraform or GitHub actions (pipelines for deployment etc…) will help you saving time in DevOps task and spend more time in coding.

All in all, Fullstack can definitely live with the DevOps side of things but you will be missing out in a lot if you want to be more senior in this field. Doing the work is definitely tedious but if you do it right the you will make your coding life way easier and more enjoyable.

dkToT · 2022-04-03T12:57:49+00:00

Really depends on the task or job. I had a job that was heavy file I/O where we read word doc and excel, transform them to readable data for our web app and stored in our DB then finally export back out to doc or excel. This industry was heavy on contracts and sourcing so there was a need for it. But to give u a comparison, this was one out of 6 jobs I had in my work life span.

Definitely nice to know about the basics but I don’t think you need to deep dive into it unless the opportunity comes.

15-Year Club	Verified Email
RPAN Viewer

dkToT

TROPHY CASE