See Bosses them... For me Just manage I mean manage to write 200 lines self. I hail those bosses at thousand lines of code, e nor easy. *cover my face and runs outta thread*

DanielTheGeek:

No wonder the computer was playing like Albert Einstein.

LOL dude nor yarb the game, all the moves where hard coded.... I have been trying to implement Minimax algorithm to make it play perfectly but I think this is the hardest algorithm I've dealt with.

I remember begging this seunthomas guy to assist but he completely ignored.... I'm almost there sha

FincoApps:


LOL dude nor yarb the game, all the moves where hard coded.... I have been trying to implement Minimax algorithm to make it play perfectly but I think this is the hardest algorithm I've dealt with.

I remember begging this seunthomas guy to assist but he completely ignored.... I'm almost there sha

Una go insult person, una come dey expect help. Who go epp?

Secondly no be my responsibility to assist anybody. Na so one guy send me him school project for c code say make i help am do am.

I don do the work but i no go send am. Whats the point of being a programmer if you cant toil?

My only assistant is to guide, and not help people write their code.

19... On python.













Yea...im a_fucking beginner...

FincoApps:


LOL dude nor yarb the game, all the moves where hard coded.... I have been trying to implement Minimax algorithm to make it play perfectly but I think this is the hardest algorithm I've dealt with.

I remember begging this seunthomas guy to assist but he completely ignored.... I'm almost there sha

Took me a week to fully grasp that minimax algorithm, but minimax is slow, for speed checkout alpha-beta pruning (a variation of the minimax algorithm but reduces the search tree to return the heuristic score faster)

toheebDOTcom:
To those looking at the last line, remember that the lines of the docblock of a getter/setter method is at least times two of the method itself!

Diaries God ooo.

Anyways, for me, I sha know that it is 'something' thaaasand. 1 or 999, stories that touch. I remember that night, feeling like say I be one guru... E red for me when d tin no gree work

RobinHez:
19... On python.













Yea...im a_fucking beginner...

Everyone started somewhere

Kodejuice:

Took me a week to fully grasp that minimax algorithm, but minimax is slow, for speed checkout alpha-beta pruning (a variation of the minimax algorithm but reduces the search tree to return the heuristic score faster)

I'm also using alpha/beta pruning but the game has a 12 X 10 board so it still has A LOT of moves to calculate..... I figured my scoring algorithm needs to be optimized.... still struggling on it though

FincoApps:


I'm also using alpha/beta pruning but the game has a 12 X 10 board so it still has A LOT of moves to calculate..... I figured my scoring algorithm needs to be optimized.... still struggling on it though

function score(node){
if(computer win) return 100;
else if(player win) return -100;
else return 0;
}

since its Tictactoe this would make your game unbeatable, provided you are searching to a reasonable depth.

Kodejuice:


function score(node){
if(computer win) return 100;
else if(player win) return -100;
else return 0;
}

since its Tictactoe this would make your game unbeatable, provided you are searching to a reasonable depth.

This is just the algorithm. The fact and also issue is evaluating if(computer win). This would be a very long method to check if the current winner is the computer. That's wwhere my problem is.


I tried restricting the search to make it detect only horizontal wins and leave out vertical and diagonal and it became a lot faster. But that's not Tic Tac Toe

Kindly look at the codes dhtml15 suggested here https://www.nairaland.com/2529139/tic-tac-toe-online-game to get an idea of the code

Kodejuice:


function score(node){
if(computer win) return 100;
else if(player win) return -100;
else return 0;
}

since its Tictactoe this would make your game unbeatable, provided you are searching to a reasonable depth.

I'll like to share the code with u

FincoApps:


This is just the algorithm. The fact and also issue is evaluating if(computer win). This would be a very long method to check if the current winner is the computer. That's wwhere my problem is.


I tried restricting the search to make it detect only horizontal wins and leave out vertical and diagonal and it became a lot faster. But that's not Tic Tac Toe

Kindly look at the codes dhtml15 suggested here https://www.nairaland.com/2529139/tic-tac-toe-online-game to get an idea of the code

I'll definitely see to it tonight, I'm a little bit busy now.

FincoApps:


This is just the algorithm. The fact and also issue is evaluating if(computer win). This would be a very long method to check if the current winner is the computer. That's wwhere my problem is.


I tried restricting the search to make it detect only horizontal wins and leave out vertical and diagonal and it became a lot faster. But that's not Tic Tac Toe

Kindly look at the codes dhtml15 suggested here https://www.nairaland.com/2529139/tic-tac-toe-online-game to get an idea of the code

the link over thereis invalid, 404

Kodejuice:



the link over thereis invalid, 404

oh yea, I removed it.... I'll like to mail the source to you

FincoApps:

oh yea, I removed it.... I'll like to mail the source to you

No P, kodejuice@gmail.com

So I checked it seems the lowest I have is like 3000 LOC and highest like 5k LOC got to admit some code duplication I will trim them down, left to me I see large LOC as a bad thing unless it's a big system

D34lw4p:
See Bosses them... For me Just manage I mean manage to write 200 lines self. I hail those bosses at thousand lines of code, e nor easy. *cover my face and runs outta thread*

One day you'll be so caught up trying to crack a problem that you'll forget to count lines. Then you'll do a count and find out you've written in the '000s. You who use to write 100s,look at you now!! You've grown!

@op
your story seems fishy.
100k+ will generate between 50+ - 100+ source files.
at between 1k - 2k lines per file.
It will take you 1yr-10yrs to write 100k+ lines of code.
maybe less working at blistering pace.
So after churning all that code out, to count lines per file, you :
click on a file
scroll down
see the number
record it down somewhere
click on another file ...
by the time you're halfway thru, at the 25 file or 50th file, the tedium is getting to you.
You are beginning to think , isnt there a program i can download online to do this?
Your client too will be bored too.
If on the other hand, you choose to open all files in an ide, they'll be so many tabs, navigating will be uncomfortable and
you processor will run slow from having so many tabs open.

2) after a long tiring project, your client would not be interested in sitting down with you to do a line count
. Very unlikely

3) After seeing the tedium of manually counting codes per file, you'd have quickly hacked together a line of code program to automate the process for you ...

So i think you came up with that story to make the thread inviting..
But i may be wrong,but i think you're telling a fib (you dey blow fabu).

asalimpo:
@op
your story seems fishy.
100k+ will generate between 50+ - 100+ source files.
at between 1k - 2k lines per file.
It will take you 1yr-10yrs to write 100k+ lines of code.
maybe less working at blistering pace.
So after churning all that code out, to count lines per file, you :
click on a file
scroll down
see the number
record it down somewhere
click on another file ...
by the time you're halfway thru, at the 25 file or 50th file, the tedium is getting to you.
You are beginning to think , isnt there a program i can download online to do this?
Your client too will be bored too.
If on the other hand, you choose to open all files in an ide, they'll be so many tabs, navigating will be uncomfortable and
you processor will run slow from having so many tabs open.

2) after a long tiring project, your client would not be interested in sitting down with you to do a line count
. Very unlikely

3) After seeing the tedium of manually counting codes per file, you'd have quickly hacked together a line of code program to automate the process for you ...

So i think you came up with that story to make the thread inviting..
But i may be wrong,but i think you're telling a fib (you dey blow fabu).

asalimpo 1 seunthomas 0

Maka why?
but why is seunthomas always getting 0? for what now?

asalimpo:
@op
your story seems fishy.
100k+ will generate between 50+ - 100+ source files.
at between 1k - 2k lines per file.
It will take you 1yr-10yrs to write 100k+ lines of code.
maybe less working at blistering pace.
So after churning all that code out, to count lines per file, you :
click on a file
scroll down
see the number
record it down somewhere
click on another file ...
by the time you're halfway thru, at the 25 file or 50th file, the tedium is getting to you.
You are beginning to think , isnt there a program i can download online to do this?
Your client too will be bored too.
If on the other hand, you choose to open all files in an ide, they'll be so many tabs, navigating will be uncomfortable and
you processor will run slow from having so many tabs open.

2) after a long tiring project, your client would not be interested in sitting down with you to do a line count
. Very unlikely

3) After seeing the tedium of manually counting codes per file, you'd have quickly hacked together a line of code program to automate the process for you ...

So i think you came up with that story to make the thread inviting..
But i may be wrong,but i think you're telling a fib (you dey blow fabu).

OK ohhh.

Mr Assumption.
Its always easy to look at how small you are and imagine that everyone is like you.

My project has more than 100 files in it.

Most of the files have between 500 and 1500 lines of code in them.

It did not take me 1-10 years but a full 8 months.

It was a process of write and rewrite.

We had to remove redundant code also, i am sure with the redundant code it would be well over 150k lines.

It was in Java.

Am not jobless na, why will i start counting lines?

Am sure any reasonably good programmer should be able to devise a way to know how many lines of code.

By the way there are tools for that.

With all una git experience, una no even sabi anything.

FrankLampard:


asalimpo 1 seunthomas 0

Grader..

seunthomas:


OK ohhh.

Mr Assumption.
Its always easy to look at how small you are and imagine that everyone is like you.

My project has more than 100 files in it.

Most of the files have between 500 and 1500 lines of code in them.

It did not take me 1-10 years but a full 8 months.

It was a process of write and rewrite.

We had to remove redundant code also, i am sure with the redundant code it would be well over 150k lines.

It was in Java.

Am not jobless na, why will i start counting lines?

Am sure any reasonably good programmer should be able to devise a way to know how many lines of code.

By the way there are tools for that.

With all una git experience, una no even sabi anything.

Your claim was simply subjected to scrutiny. That's all.
I didnt compare your output to myself but to other people's output i've read about.
A pattern usually emerged for large output , in the scale of yours.
Two, run the process of the code counting in ones head - and you'll see what i was
saying.
Anyway, I dont know any mature programmer who starts out with the intention of
outputting a lot of code. Rather, he wants to solve the problem as elegantly and simple as ever and go home. in coding less is more.

Your story simply sounded fishy that's all. and i was'nt scared to tell you so.

lets go over it:
YOu opened the first file, scrolled down, read the lines. saved it on paper,
He reached for his calculator,
you did it to the second file, the third,
ha... non coders in the world i live in wouldve glazed over by then.
two:
architecting, designing and planning a 100K application would take
lots of time, because you can't just go back and change things like you would on
on a 1k app. Infact at this level, architecting is the deal breaker.
You dont just hack 100k+ apps.
Then testing the app!!! - testing is 60%-80% where the work is.
Every single one of those 100k+ lines must be tested else bugs will bubble up and
compound.
Now assuming you were the architect, the programmer and the tester and the build engineer,
by the time you're done, sitting down with your client to open each file and count codes,
while he makes a map fileName->lines of code on paper would seem , irritating..

in a nutshell,if you dont want to be critiqued , dont post.
You could be telling the truth, you could be telling a lie, it has nothing to do with feeling small.
We are all here to learn

dhtml18:
Maka why?
but why is seunthomas always getting 0? for what now?

isi gini?

asalimpo:

isi gini?

dis boy na dollard, adon-talk-am-since.

asalimpo:

Your claim was simply subjected to scrutiny. That's all.
I didnt compare your output to myself but to other people's output i've read about.
A pattern usually emerged for large output , in the scale of yours.
Two, run the process of the code counting in ones head - and you'll see what i was
saying.
Anyway, I dont know any mature programmer who starts out with the intention of
outputting a lot of code. Rather, he wants to solve the problem as elegantly and simple as ever and go home. in coding less is more.

Your story simply sounded fishy that's all. and i was'nt scared to tell you so.

lets go over it:
YOu opened the first file, scrolled down, read the lines. saved it on paper,
He reached for his calculator,
you did it to the second file, the third,
ha... non coders in the world i live in wouldve glazed over by then.
two:
architecting, designing and planning a 100K application would take
lots of time, because you can't just go back and change things like you would on
on a 1k app. Infact at this level, architecting is the deal breaker.
You dont just hack 100k+ apps.
Then testing the app!!! - testing is 60%-80% where the work is.
Every single one of those 100k+ lines must be tested else bugs will bubble up and
compound.
Now assuming you were the architect, the programmer and the tester and the build engineer,
by the time you're done, sitting down with your client to open each file and count codes,
while he makes a map fileName->lines of code on paper would seem , irritating..

in a nutshell,if you dont want to be critiqued , dont post.
You could be telling the truth, you could be telling a lie, it has nothing to do with feeling small.
We are all here to learn

If you want to learn, you must first accept the statement, then you can render your own evidence if indeed you have any.

If you actually read the whole first post and not skim through you would understand what happened and not make[b] "Assumptions"[/b].

No one started out trying to count the number of lines in the code, it was just a curious gesture to know how many lines have been generated after such a long exercise( that was the longest i worked on a project).

Maybe if you do hold a positive view about me, you may actually learn from me.

I am not out to destroy, just to correct a few very wrong notions that people post here.

seunthomas:


If you want to learn, you must first accept the statement, then you can render your own evidence if indeed you have any.

If you actually read the whole first post and not skim through you would understand what happened and not make[b] "Assumptions"[/b].

No one started out trying to count the number of lines in the code, it was just a curious gesture to know how many lines have been generated after such a long exercise( that was the longest i worked on a project).

Maybe if you do hold a positive view about me, you may actually learn from me.

I am not out to destroy, just to correct a few very wrong notions that people post here.

Bros, your story still doesnt add up. It smells fishy and i aint afraid to tell you so.
Architecting, then coding, then debugging a very large application takes a freaking long time.
if you worked so long and under intense duress for so long, the client would be in a rush to use his software
not sit down with you, and count the lines using of all methods a tedious method.
Non programmers hav very little interest in code . It's like children who dont like maths seeing maths, it scare them . So this clients interest in counting code lines ... hmmm.

let me give you som info of lines of code:
couchdb- was 20k lines of terse erlang code. It was a game changer
I was reading a blog once by a programmer who wrote an application with 100k lines of code,it took him 10yrs!!
youtube and facebook - yeah, the global phenomenoms. With all the intense grinding work of the founders
were about 10k lines of code at launch!! - think of it.
Facebook - zuckerberg resigned to concentrate full time on building facebook.
with 3 or so other coders and it hand only about 10k lines!!!
Dude.

When you add testing!!! Testing 100k lines of code alone could take you months or more.
Testing every function ...
infact by the time you're pushing out 100k lines of code, you'd hav spawned so many frameworks and libraries from the effort.

Then architecting, remember you can't just hack 100k+ . it must be architected like a professional.
The architectural phase alone would take months.
The testing will take months.
The building will take a few minutes or even up to half an hour.

Doing all these in a few months -- hmm!! It looks exaggerated.
Dude,think again. But i could be wrong.

asalimpo:


Bros, your story still doesnt add up. It smells fishy and i aint afraid to tell you so.
Architecting, then coding, then debugging a very large application takes a freaking long time.
if you worked so long and under intense duress for so long, the client would be in a rush to use his software
not sit down with you, and count the lines using of all methods a tedious method.
Non programmers hav very little interest in code . It's like children who dont like maths seeing maths, it scare them . So this clients interest in counting code lines ... hmmm.

let me give you som info of lines of code:
couchdb- was 20k lines of terse erlang code. It was a game changer
I was reading a blog once by a programmer who wrote an application with 100k lines of code,it took him 10yrs!!
youtube and facebook - yeah, the global phenomenoms. With all the intense grinding work of the founders
were about 10k lines of code at launch!! - think of it.
Facebook - zuckerberg resigned to concentrate full time on building facebook.
with 3 or so other coders and it hand only about 10k lines!!!
Dude.

When you add testing!!! Testing 100k lines of code alone could take you months or more.
Testing every function ...
infact by the time you're pushing out 100k lines of code, you'd hav spawned so many frameworks and libraries from the effort.

Then architecting, remember you can't just hack 100k+ . it must be architected like a professional.
The architectural phase alone would take months.
The testing will take months.
The building will take a few minutes or even up to half an hour.

Doing all these in a few months -- hmm!! It looks exaggerated.
Dude,think again. But i could be wrong.

Right now am shaking my head for you.

Let me use some very provocative logic, maybe you can reason a little. LOL

Are you a dullard??

Can you prove that you are not cos it does not add up.

LOL.

Anyway by the side, the banking applications you use, mobile banking etc. Core banking applications, many telecoms applications.

Most of this applications have millions of lines of code.

You are probably still a learner, cos i use erlang OTP too.

Its less declarative compared to java (most functional languages are less declarative).

If you have not written much code or you dont want to post how many was your lines you had in your longest work, then GET off my thread and stop making a nuisance of yourself.


We want to inspire others and not argue senseless.

So please prove you are not a dullard. Am waiting.....

Olodo JJC.

dhtml18 come and settle this case oh.

asalimpo:


Bros, your story still doesnt add up. It smells fishy and i aint afraid to tell you so.
Architecting, then coding, then debugging a very large application takes a freaking long time.
if you worked so long and under intense duress for so long, the client would be in a rush to use his software
not sit down with you, and count the lines using of all methods a tedious method.
Non programmers hav very little interest in code . It's like children who dont like maths seeing maths, it scare them . So this clients interest in counting code lines ... hmmm.

let me give you som info of lines of code:
couchdb- was 20k lines of terse erlang code. It was a game changer
I was reading a blog once by a programmer who wrote an application with 100k lines of code,it took him 10yrs!!
youtube and facebook - yeah, the global phenomenoms. With all the intense grinding work of the founders
were about 10k lines of code at launch!! - think of it.
Facebook - zuckerberg resigned to concentrate full time on building facebook.
with 3 or so other coders and it hand only about 10k lines!!!
Dude.

When you add testing!!! Testing 100k lines of code alone could take you months or more.
Testing every function ...
infact by the time you're pushing out 100k lines of code, you'd hav spawned so many frameworks and libraries from the effort.

Then architecting, remember you can't just hack 100k+ . it must be architected like a professional.
The architectural phase alone would take months.
The testing will take months.
The building will take a few minutes or even up to half an hour.

Doing all these in a few months -- hmm!! It looks exaggerated.
Dude,think again. But i could be wrong.

You might be wrong....

It's not as difficult as you make it seem...

Poor architecture can also increase lines of code.... so the programmer does not necessarily need to spend months planning

Secondly, you make it sound like the programmer knows how many lines of code he's about to write before even embarking on the project

My point is: It's possible to write that much code without even too much planning or testing (Although 100K lines is a lot). I've done A LOT of unplanned projects so I know

FrankLampard:
dhtml18 come and settle this case oh.

On my thread. Be careful ohh..