Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
Try => fail
Try => fail
Try => fail
Try => fail
Try => little success
Try => fail
Try => fail
Try => I think I've got it
Try => almost there
Try => fail
Try => fail
Try => oh, is that the problem?
Try => fail
.
.
.
=> SUCCESS12 -
Non dev friend: Do you know “hatamal”?
Me: wtf is hatamal?
Non dev friend: hatamal. Spelled as HTML.
Me: T.T12 -
Learning a new technology:
1. Denial
2. Anger
3. Bargaining
4. Depression
5. Acceptance
6. Ohh, cool feature~2 -
1. See new shiny tech
2. Read install/setup instructions
3. Make Hello World/Todo app by copying codeblocks from documentation
4. Update LinkedIn profile
5. Insist on rewriting entire company ecosystem
Oh wait, thats my horseshit-eating coworker3 -
Trying out on my own, then googling the problems, finally watching a 2h documentary on zebra communication on youtube.2
-
Immediately start doing a project way beyond your level, and within 2 weeks you'll learn things that would take college 2 years to teach you.5
-
1) Looking up official Page of the new language/framework
2) Watch tutorial on Youtube
3) Realise it's teached very complicated
4) Buy a course on any course site
5) Realise it's even more complicated
6) Buy book
7) Learn it perfectly
#booksForLive :D6 -
static void TryOut<T>(T newStuff)
{
try
{
self.Learn(newStuff);
}
catch (NotUnderstandingException)
{
// At some point, it will work, just call it again
TryOut(newStuff);
}
}4 -
So day 2 of my python automations.
I have spent 6 hours and a lot of stack overflow “research” to saved myself 45 minutes a day with file downloads (web & ftp and outlook emails), excel spreadsheets and data manipulation macros, all stored in a nice tidy zip file at the end.
Now to find a way to send to a web server for digestion 😎
And all of this in a poor 90 lines 😧
God damn why didn’t I look into this earlier?2 -
My favorite method?
Step 1: Meet Morpheus
Step 2: Swallow red pill
Step 3: Wake up from the Matrix
Step 4: Upload needed Knowledge directly to my brain
Step 5: Go back to Matrix4 -
The best way to learn something is to teach someone...
If you learn a framework or a language or a tool u make sure u teach it to someone it helps u understand it better and someone else is also smarter6 -
The only technique I know.
Get hired straight out of uni. Project architect disappears right at beginning and I am left as a graduate employee to build a travel booking web app. Learning new front end and backend frameworks by coding them constantly for the next 8 months.
We might actually get this project done!5 -
1. Visit the official site.
2. Browse for official tools.
3. Check the official documentation.
4. Check the Internet for other non-audiovisual sources.
5. Try making a simple application.
6. Run out of application ideas.
7. Move on to the next shiny dev technology.
8. Go to step #1. -
I dive in head first.
Some existing program annoys me, so I get this itch to write a selfhosted Spotify in Go, or a conky with 3D graphics in Rust.
I check the homepage of the language, download the tools, check which IDE is great for it.
Then I just start writing code, following the error corrections thrown by the IDE, doing web searches for all errors. Then when I run into a wall, I might check the reference docs or a udemy course.
Often I don't finish the project, because time is limited and I still have 4 million other things to do and learn, but at least I've learned a new language/tech.
Con: For tech which uses unique paradigms like Rust's memory management or Go's Goroutines, it can be frustrating to bash away at a problem using old assumptions.
Pro: By having a real demand for a product with requirements instead of a hello world or todo app, it's much easier to stay motivated, and you learn beyond what courses would teach you.5 -
thenewboston.com back in the days.
Nowadays it's trying to make a game with it and the learn it by doing.6 -
Opening up the docs, a book or a bunch of random pages online.
build something stupidly horrible to familiarise myself with different aspects and rinse and repeat until it’s something I think is worthy of being released into the wild. -
1) read every pages of the tech's website
2) follow documentation
3) read online tutorials
4) try to use it in currently working some projects1 -
My favorite method to study a new tech or framework is to make a little research and try to write an article.4
-
Tried learning python like over 10 times from the basics. No success!
Being a Java developer for about 5 years, I think I can't live without semicolons 😂3 -
step 1) open and browse producthunt for new dev tools to use and try out
.
step 2) opens dev tool/app's website *ooh nice landing page*
.
step 3) tries to find api and documentation, scrolls to bottom of the webpage
.
step 4) "we are still in private beta, sign up to be notified about the final release!"
.
step 5) lol *sighs* bookmarks tab before closing it
.
step 6) repeat step 1
.
.
-
I used to check what local market wants, but after joining devRant I noticed local market sometimes feels in stone age, so since February 2017, devRant is best place to learn either asking, or checking what others are doing it a helps in getting ideas on what kind of project and language needs to be done for the sake of learning
-
1. Watch tutorial
2. Build project
3. “I’VE LEARNED NOTHING!!”
4. Call down pox upon instructor and seven generations
5. Rewatch tutorial
6. Get it
7. “Sorry about the boils” -
Best way to learn dev tech is to choose the thickest book on the field and start reading it. Don't lose your time on blogs comparing what is the best framework If you do not know any of them... Select one and full blast!!!
-
Me trying to find out what some word means
1. Google
2. Find a good result
3. Notice some other interesting word
4. Repeat -
I am a little bit old fadhioned when it comes to new dev tech stuff. I am at first, not an early adopter ( others should proof it first) and second I like to read books. If there is someone who has understood the matter and has written a book, then I go for it 😁 and third, when I have to use an early technology then the simplest thing is to read the doc to get a grasp what this is all about. Youtube as others describes is lame, because if you are forced to watch 40min when you are just interested in one small thing, you will loose a lot of time finding the relevant piece of content..
Positive on reading is, that you have to think for yourself!1 -
Finding out how not to do it.
An example, learning how to parse HTML, and finding a stackoverflow post with the answer "use regex" triggers tech junkies so much that they actually comment a mostly accepted way of doing something.3 -
1) read about it
2) search * sucks and read it
3) create something decently beginner frendly
4) if it was hard find something better
5) if pretty easy make something useful1 -
Best way to learn something new?
You keep repeating it wrongly until you are blue in the face, the whole world has gone red and the sweet release of death sounds favorable to your current dilemma.
Then, if you are lucky, you get it right out of the many many failed attempts.
But, what you have learned is far greater than getting it right once. You've learned many ways not to do it again. -
When I try to learn for example new language, I’m trying to replicate my existing project in this specific language
-
Easy. I've learn Bash, Python and Java just by constantly getting assigned to projects that require those languages. Also tiny bit of Perl, but I don't want to talk about this.
I was hired as a C++ developer BTW and never had contact with those languages. -
Recently, I have planned out my weekends to learn new stuffs.
And guess what, since I needed a project to start with, I have taken devrant related projects.
Example: Writing a python library as devrant api wrapper.
I have few other stuffs to learn too which I will begin once I finish this. That too most probably will also have some relationship with DevRant.. -
1) search a project on github
2) read its documentation and decide if it's worth it
3) read contribution guide lines
4) contribute
5) start at 1) -
1) Search for "what is *language-I'm-interested-in* useful for?" on ddg;
2) Google the same thing 'cause you never know;
3) If it looks cool/useful and adds something to the tech I already know, I find a tutorial and follow it.
4) Trial and error on a new project that I will end up doing in another language because by that time I will find the new project so cool that I have to finish it in a language I use proficiently.
Every damn time. -
The school I went to, and this was really the only benefit of the school, gave all it students lifetime memberships to digital tutors, which was bought out by pluralsight, which then bought code School. So I basically got free membership to three different sites, all of which have a good amount of technical training with videos, guides, and work along lessons on them.
For what school cost to me, it will have paid for itself as long as I live for another Thousand Years.1 -
I find it hard to pickup a new tech unless i need to build something with it. I guess i learn better by doing than just reading.1
-
Whatever the task needs.
New paradigm? Probably a book first approach.
Library/API: their own suggested tutorials and references cause that shit moves quick.
If I have to read a cave painting to understand an ancient card punch language I’ll happily do it.
I’ve found, when I don’t know something yet I get the “brick wall” feeling, that this is all going to be too difficult... I’ve learned to love that feeling.
If all else fails: RTFM. -
Reading 1 tutorial/ part of the documentation
Trying it on my own
Realize that your code doesn't work
Googling the problem
Fixing it
Repeat -
Oh that looks pretty let me try.
Ow God why !!
....
Ah....that makes sense
Obsess over it for months
Make failed side projects with it.
Ad to cv -
1.) Read the docs on the website
2.) Curse the Devs for bad docs
3.) Go to YouTube and pray that I find a food tutorial WITH AUDIO!
(jk,sometimes some docs r very neat and clean) -
I'm new in the programming world; when I need to learn something new I generally look at documentation and articles to get an understanding of the basics.
Then, if it's still interesting to me, I just try it out.
Sometimes I might ask a fellow more experienced programmer or a teacher to explain it to me.1 -
I love learning by doing.
Building MVPs and prototypes is the best way. Even better if you have a chance to show and share them in front of an audience (peer pressure can be good!).
Share the lessons you've learned and what you've done wrong, it will help many more people than just yourself.
I've been working for an eLearning company for the last 4 years (CloudAcademy.com) and I'm in love with the idea of learning something new every day. And not just coding. Code is "only" a tool to solve problems, and learning something about those problems and fields will make you a better developer. -
Best way to learn 'X' (and X11 too, if you see what I mean :))
1) shitpost on DevRant about how much 'X' is better than Java
2) read the official docs1 -
I'm a practical learner. Usually i get myself a simple example from codeproject and play around with it.
I constantly switch between tutorials, documentation and doing it. Doing it makes me find questions and i can remember things better if i care about them, which happens if they are the answer to a question.
Within those experiments i build working example code and document it in a way that fits my needs. When i haven't done the stuff for some time, this self-made examples, help me continue where i was.1 -
I start reading about it, from their website, forums, blogs, etc.
Next thing I usually do is to take a look at stuff made of that tech and mess around to see what it looks like.
Then I pick a book about the subject, set up the basics and start from the very beginning, even if the prologue starts with "programming is..."
At some point I start to connect concepts previously seen in the first step with the chapter I'm in, or even identify elements discovered in the second step.
Works for me. -
Most of the stuff I know comes from debugging other people's code. When working on someone else's project, I try to understand what their code is doing and think how I could make it better and if it's possible to extend the functionality to make it do other things as well.
-
I prefer starting from theory and then proceed with practicing. For example, to learn haskell and deeply understand it, I started by taking a course in category theory and I already have a degree in computer science and then start writing actual code. The same with JS. I started with theory for JIT compilers and studied how V8 works, how it utilizes event loops and how they are implemented in the kernel. Then I started experimenting with code and demos. It's a success path for me, that has worked every time with every new technology.2
-
First go through any getting started guides or introductory tutorials. Then depending on comfort level and available time, either start exploring further on your own or search for more advanced tutorials.
Try to make use of what you learned, either at work or in hobby projects or small proof of concept programs, as the case may be. -
Watching YouTube and reading the documentation.
Preferably with a practical goal (e.g. a software that does something). -
1) try make it do web requests
2) try make it work as server
if i can do these things with new technology then i can do almost all today software market need. even some css frameworks passes these tests. -
Need to use new module or pattern:
1. Read the online documentation
2. Have no fu*kin clue what I just read
3. Try for 2 hours and fail.
4. Go home and sleep
5. Wake up at 3am from a fever dream with the solution to the problem
6. Go to work and implement it in 10 min
I guess I learn when I sleep -
The meme I saw here before... changing stuff and seeing what happens... with a side of documentation.
-
Start with simple projects then keep improving it until you reach the depth level that you want.
I used to learn a new language/technology every month, I did that all this year until now, I learned 3 new languages, 2 new databases, 1 new paradigm, so many frameworks and methodologies and design patterns applying in real world projects ! -
My favorite method to learn something new is just to buy a book or download a paper about it or something lock myself up in my desk and not go home until I accomplished something. Those have been some fun nights so far!
-
1. Figure out what project needs it
2. Read a primer book (skim), mostly syntax and note the gotchas
3. Start coding
4. Read in detail as reference or Google... While coding -
YouTube first what's it's about or get information about the tech. Next, look for free tutorials on YouTube.
When working on the tech, use Google to look to bug-fix or code that some might have already written. -
Using websites that makes me learn by practicing such as codecademy. Never been a huge fan of theory class
-
What I should be doing: Playing around with it and working my way up, usually by reading the docs and putting together a "tutorial" in my head.
What I actually do: Get overhyped think of theost complicated thing possible and figure things out bit-by-bit
Meh, I do both nowadays. Slowly buys surely.1 -
- Reading the docs and trying out examples (basically copy paste their example and try it in your computer)
- YouTube videos if I don't understand something from the docs. And to see how people explore various ideas I wouldn't have thought about
- From what I have learned, trying it by myself or applying it to somewhere useful
- Tinkering when free, else move on -
Reverse engineer an example off of github, use to make something else, stack exchange when it doesn't work, repeat.
-
1. Enroll in course/project/tutorial
2. Watch, apply, ask questions, find answers and repeat until nothing left to learn
3. Reformat the machine I was learning from
4. Forgot what was learnt and repeat from step 1 until it becomes 2nd nature
5. ???
6. PROFIT (by doing jobs)!!! -
1. Docs
2. Tutorials
3. Realize tutorials skipped a few details
4. Back to step 1
And in most cases, joining a slack/telegram group for the tech -
Breaking things directionally. See it, break it, try to put it back, fail, repeat. When it works, you probably get it.
-
Wait at least an year.
Bcuz after an year, there are enormous amounts of tutorials in youtube that are easier to understand than the official documentation.
(Read the Docs (!fan)) -
Watch an "Introduction" video about it, or read the docs/blogs on why and where to use this particular tech. If you find it useful, then get your head down and work. Watch every YouTube video, read company docs, read random blogs, read FAQs. Honestly, any source you can get your hands on.
And never forget to write more code than you read.
Consistency and hard work is the only key.
I still remember when I was first getting introduced to front end, I didn't sleep for 3 straight days and was studying all that I could. -
Find a simple project that I think would fit the technology and Google how to so every single baby step I think my application will need to do.
-
read and get a basic understanding ->
create using simpleton syntax until confident ->
read a bit more ->
refactor with a more advanced approach
-> repeat until GODMODE
-> sad panda if the next version is completely different (Angular 2.0)
-> flex your muscles
-> buy some swag
-> happy panda
-> retire. -
The best way to learn is to clone it, install it and get stuck in. Read the documentation, see the example code, then get an idea for a project and start building with it.
-
When learning a new language I look up public repos on github, specifically those who are just collections of algos in different languages, and take a look + try to implement it in a different way. The good ones also have maintainers that actually take a look at your code when you open a PR and give you some hints if they are proficient in that language.
-
The lovely moment when you find the library which does everything that you’ve been looking for, install the flippin’ NuGet and get busy....
Next day you compile and run... just to make sure that the old stuff are still working, only to find out that yesterday’s NuGet flipped up everything else’s dependencies.... *fml and let me die !! -
Read basic documentation.
Pick a fun project to do it with.
Start doing it - with lots of help from larry page and the overflow site. -
Read the documents for syntax and general practices, then find a tutorial(youtube) and dive right into the mud.
-
Depends on when it comes out, often it involves rebuilding my portfolio. Other times it's building a project idea, had a light week at work once and built a small app in Aurelia, then rebuilt it in Vue to test out both and compare them.
When I was looking into PWAs I rebuilt my react native app into react. Lol
Top Tags
Weekly Rant
View