₦airaland Forum

brilliant!....i'm interested, please add me 08167061500

Experienced programmers do 29 things that every beginner programmer should know.

1. Use Google very aggressively. You need to know how to phrase search queries, review other developers’ code, and apply it to the problem that you’re trying to solve.

2. Maintain an obnoxious amount of stick-to-itiveness. Veteran programmers embrace the experience of being a beginner with new technologies and teach themselves on the fly.

3. Acknowledge that micro-decisions matter. For example, things like naming variables, calling functions, naming CSS properties, using a hash vs using an array, and other seemingly small things can have a big impact.

4. Acknowledge that most major decisions don’t matter that much. Experienced developers roll with the punches and avoid the flamewars that other developers often find themselves in. They’re quite zen-like.

5. Always use the right tool for the job. There are so many different open source libraries, tools, and frameworks out there. Experienced programmers know what to use for each problem that they encounter.

6. Understand that code is cheap. You need to be ok with scrapping hundreds of lines of code to do things in a different way.

7. Evaluate technologies based on all their merits. For example, I’ve been bullish on Elixir. It has wonderful syntax, an amazing community, and a bright future. But it’s so new that if you want to actually build complex features, you’ll have a harder time finding open source technology to make your life easy. You need to take all of these factors into account.

8. Say “I don’t know.” There’s no quicker way to waste your time as a developer than to refuse to acknowledge what you don’t know.

9. Always analyze the clues found in error messages. Traditional education has taught us that failure is bad. Error messages are often associated with failure. However, good programmers know that these messages are actually clues that lead you down the path to the right solution.

10. Know the difference between a premature optimization and a show-stopping optimization that NEEDS to happen. They know the right time to write code that’s a bit more confusing, but will be faster.

11. Take responsibility for your mistakes. Mistakes will happen. Especially when working on a team. It’s a waste of time to pass off the blame because typically there are multiple parties at fault.

12. Become a power-user of your development tools. If you spend a good percentage of your time coding in a specific environment, you should know exactly how to control it.

13. Know how to use Vim (at least a little bit). You need to be capable of at least muddling your way forward using this text editor.

14. Never accept freelance work in an unfamiliar technology. A big part of freelancing is estimating how long things will take. Don’t put yourself in an awkward spot by projecting time for something you don’t already know.

15. Don’t count the number of hours. Unstoppable programmers spend their time doing deep work (as opposed to shallow work), and they understand that the number of hours spent working don’t actually matter.

16. Absorb massive criticism with ease. You need to develop the ability to react rationally and logically when your code gets torn apart.

17. Pair program with people with more experience. There’s no faster way to learn to code.

18. Always code review your own work first. Before you issue a pull request on Github, you should review the code and pick it apart as if it was written by someone else.

19. Recognize that the hard part of freelancing isn’t writing the code. It’s everything else. Sales, marketing, customer support, quality assurance, and product management will all take up a lot of time.

20. Identify and resolve bigger issues. The best programmers think beyond the immediate issue at hand and know how to deal with problems in a way that leads to more long-term solutions.

21. Dive into large open source projects to bring your features to life. Impossible is nothing if you know how to monkey patch a solution.

22. Skip a lot of meetings. Your company pays you to write code. Not to talk about writing code. When meetings get out of hand, it’s ok to start skipping them. People will appreciate your time more if you start doing this.

23. Know when it’s time to give back. There comes a time when you need to start giving back to junior developers, just like your mentors did with you.

24. Be capable of writing bad code. Sometimes, it’s ok to become a Duct Tape Programmer. Over time, you need to figure out when it’s acceptable to take a shortcut and when it is absolutely needed. This is one of the most difficult skills to learn.

25. Let other people know that you’re working late without being a jerk. If you’re the last one in the office, just send an email to someone with a quick update. People generally notice the timestamp.

26. Act as a leader, not a boss. Bosses are people who have people work for them. Leaders are people who other people follow. Be a leader.

27. Go play foosball. In the long run, building relationships with other developers (and people in other roles) will be more valuable than shipping a feature in a tighter window.

28. Learn under pressure. You need to know how to navigate a situation in which a system has gone down and you’re responsible for getting it back up. Even if you don’t know exactly how to solve the problem.

29. “Move fast and break things.” Don’t let perfect be the enemy of good. Mistakes are often the best learning opportunities. So don’t treat your mistakes as failures. Instead, treat them as learnable moments and know that fighting through them is critical to your growth as a programmer.

Programming, like many things in life, is often more about the work you put in that your actual know-how. So, if you’re a beginner programmer, just get coding, and try to start implementing these practices into your routine to better your craft.

source: https://www.quora.com/What-are-some-traits-practices-of-experienced-good-programmers-that-every-beginner-programmer-should-know

Checkout Andela some i also know so pple dat did it at NIIT...u might also wanna checkout freecodecamp.com join their fb forum and go for some cofee and code...get 2 mingle wit other programmers. Good luck

@omoolabeads u're welcome

def recursive_factorial (n):
  if n == 0:
    return 1
  else:
    return n *recursive_factorial(n-1)
def iterative_factorial (n):
  product = 1
  for i in range(1,n + 1):
    product = product * i
  return product

op that should solve your problem

The open saturday is supposed 2 be 2moro but no resonse from them so far.....
guess i didnt fall in d range too

enigmatique:
Glad to hear that!

bro this is wassup
finally!!!!!!!!!

Cc WafiJoe, onyebig1, miketayo, 5staG.

update.....
i re-wrote the whole prime_number code
and now its finally working

enigmatique:
Here are the problems/quirks I see in your script:
1. You don't need that "continue" statement on line 6. The for loop will continue normally.
2. int is a built-in function of Python! Just like len(), range(), str(), it can't be used as a varible name. The Proctor interpreter also shows this coz it gave len() and range() the same color as int. So use another variable name e.g some_int, num, number etc.
3. The range stipulated on line 11 is accurate, but you need to rethink line 12-15. The way it is, it's only testing the input with one number, the first number of the range you gave, which is 2. This is due to the return statements on lines 13 and 15, which end any further execution/iteration. Therefore, those lines are testing for ODD numbers, not prime ones.
SOLUTION: Use your loop to check if any of the numbers in the stipulated range is a factor of the input. Immediately you find a factor, return False. But if the loop completes without finding a factor, then put a "return True" statement OUTSIDE the loop (TIP: that should be on line 17 ).

bro, like i said, i made these changes out of frustration
see what my code is looking like now....

could u edit d part d has error and correct it pls....i've got no time left

its 2:37am and am still battling algo lab since yday without sleeping a wink
ive been re-writing over n over still cant find d error and its not even allowing me import from math module
so i can use some functions in d module

like ...(math.sqrt(n)-1) ok, guess dat was weird tho'

geez!....dis algo lab yaf suffer me

sm1 pls help

this is what happens when i click submit

enigmatique:
Uh, no, didn't get that mail. Last one I got was about a Data Scientist Masterclass. But do let us know how it goes if you get picked sha.

WafiJoe:
Lol. Congrats. See you soon.

it has finally happened!
pls help me guys!!!!!!!!!!!!!!!!
been battling this code for over an hour....
pls i dnt knw whats wrong with my algorithm lab its pasing all the tests but its refusing to submit!!!

pls Note: everywhre u see int in the prime_number function, i've been using n before, i only changed it out of frustration

enigmatique:
Uh, no, didn't get that mail. Last one I got was about a Data Scientist Masterclass. But do let us know how it goes if you get picked sha.

what was that abt?....some sorta iv too?

@enigmatique congrats!!!!>>>>>
i'll also try as much 2 finish up 2day or latest 2moro....
i hope u also got the open saturday invitation by andela?
i got a mail some days back that contains an invite 2 andela's yaba office next week saturday
i really hope i fall among d first 60 pple as they said in d mail....
and hope u guiz also filled d form....
if so, perhaps we might meet there who knows?

well meanwhile.....


home study ti take over!!

enigmatique:
Also had the same problem in the OOP Lab and solved it, just like you. But this problem is totally different from that one. In this case, the interpreter is not working at all for some reason, let alone give an error message!

So, have you done the Algorithm Lab?

am doing the Algorithm Lab 2day....and i jst hope it doesnt give me any problem...
@enigmatique what stage are u in d test?

with what i've seen 2day, if any code frm d lab isnt running....it might jst be one tiny error and d annoying part is that d error msg u'd get might not really be helpful
sometimes ur code is fully ok and running but its still throwing error right?....
read d questions again and use exactly what they asked u 2 use
lemme share my experience 2day
i did d oop lab 2day and it kept throwing one useless error msg and i was jst stuck
so i had 2 write d same code in my python shell and everything was ok and jst 2 be sure i used some online code compiler
including codecademy and it ran like gear 5
but it kept throwing error until i saw d real cause
i used print("invalid transaction" )
instead of return("invalid transaction" )
and it ran after making that change

WafiJoe:
Hope you are still going to be able to say the test is easy after those labs

the only thing am sure abt is that i'll pass the test bro

the homestudy test is not too hard buh its trickish.....jst finished d second quiz(knowing ive not done too well so far) so i i'm preparing harder for this oop lab....and d rest...

The inlaws should dash him d curtain 2 sew the remaining ones na ....he still needs cap and agbada

Thought I saw those shoes in chaolin soccer

Dat nigga is not even in the friend zone....he'z in d brother zone

Hey op....We have the gud guys, the nice guys and the bad guys....trust me, u dnt wanna be a nice guy and u dnt wanna be a bad guy either....Every girl wants a gud guy! Unless d girl has some really low self esteem wch is a #No No 4 me

Shoro niyen?

Hmm...been following all d way, buh d insultive words weren't cool!...vhema u're one heck of a spoilt child sha