Jump to page: 1 2
Thread overview
Where to go after "Programming in D"
Mar 01, 2016
karabuta
Mar 01, 2016
realdonaldtrump
Mar 01, 2016
David DeWitt
Mar 01, 2016
David DeWitt
Mar 01, 2016
karabuta
Mar 02, 2016
tsbockman
Mar 02, 2016
karabuta
Mar 01, 2016
cym13
Mar 01, 2016
Ali Çehreli
Mar 01, 2016
Daniel Kozak
Mar 01, 2016
Ali Çehreli
March 01, 2016
I am almost done with the "programming in D" book. Where will you suggest a go from there. My current focus is on network programming, database systems, data manipulation and software architectures for database related apps(mostly Linux platforms with D).

I am aiming to become a hardcore and better coder(quality code) than you :) Please suggest.


March 01, 2016
On Tuesday, 1 March 2016 at 16:50:12 UTC, karabuta wrote:
> I am almost done with the "programming in D" book. Where will you suggest a go from there. My current focus is on network programming, database systems, data manipulation and software architectures for database related apps(mostly Linux platforms with D).
>
> I am aiming to become a hardcore and better coder(quality code) than you :) Please suggest.

You can never be as good as me so you should just quit.  If you think you can I will probably sue you.
March 01, 2016
On Tuesday, 1 March 2016 at 16:50:12 UTC, karabuta wrote:
> I am almost done with the "programming in D" book. Where will you suggest a go from there. My current focus is on network programming, database systems, data manipulation and software architectures for database related apps(mostly Linux platforms with D).
>
> I am aiming to become a hardcore and better coder(quality code) than you :) Please suggest.

I'd probably skim thru the Language Reference and Phobos.  After that I would practice using Ranges and get a better grasp on the functions in std.algorithms.  std.algorithm has some good stuff for dealing with data.  Since you want to do Network programming I would suggest Vibe.d and read thru the source of it.  Also whatever DB you normally use check out the projects for those drivers and maybe contribute as some need ppl.  Since you say you want to become "hardcore" I would suggest porting some popular libraries over to D.  After that maybe look to get involved in Phobos and/or the compiler of your choosing.
March 01, 2016
On Tuesday, 1 March 2016 at 16:50:12 UTC, karabuta wrote:
> I am almost done with the "programming in D" book. Where will you suggest a go from there. My current focus is on network programming, database systems, data manipulation and software architectures for database related apps(mostly Linux platforms with D).
>
> I am aiming to become a hardcore and better coder(quality code) than you :) Please suggest.

I would suggest the "D Cookbook" by Adam Ruppe, it's a great book for everything related to D metaprogramming.
March 01, 2016
On Tuesday, 1 March 2016 at 17:21:16 UTC, David DeWitt wrote:
> On Tuesday, 1 March 2016 at 16:50:12 UTC, karabuta wrote:
>> I am almost done with the "programming in D" book. Where will you suggest a go from there. My current focus is on network programming, database systems, data manipulation and software architectures for database related apps(mostly Linux platforms with D).
>>
>> I am aiming to become a hardcore and better coder(quality code) than you :) Please suggest.
>


Forgot to add:

https://github.com/PhilippeSigaud/D-templates-tutorial


March 01, 2016
On 03/01/2016 08:50 AM, karabuta wrote:
> I am almost done with the "programming in D" book. Where will you
> suggest a go from there.

Like others said, I would spend time on Phobos to become familiar with it; there are many gems in there.

I am still reading both Mike Parker's "Learning D" and Adam Ruppe's "D Cookbook"; they are great. (Is Kai Nacke's "D Web Development" out yet? The page still says "pre-order".)

  http://wiki.dlang.org/Books

Ali

March 01, 2016
On Tuesday, 1 March 2016 at 19:59:19 UTC, Ali Çehreli wrote:
> On 03/01/2016 08:50 AM, karabuta wrote:
>> I am almost done with the "programming in D" book. Where will you
>> suggest a go from there.
>
> Like others said, I would spend time on Phobos to become familiar with it; there are many gems in there.
>
> I am still reading both Mike Parker's "Learning D" and Adam Ruppe's "D Cookbook"; they are great. (Is Kai Nacke's "D Web Development" out yet? The page still says "pre-order".)
>
>   http://wiki.dlang.org/Books
>
> Ali

Yep, I have my copy (even print one) for some time on my desk :)

https://twitter.com/kozzi11/status/700340359927349249
March 01, 2016
On Tuesday, 1 March 2016 at 17:53:27 UTC, David DeWitt wrote:
> On Tuesday, 1 March 2016 at 17:21:16 UTC, David DeWitt wrote:
>> On Tuesday, 1 March 2016 at 16:50:12 UTC, karabuta wrote:
>>> I am almost done with the "programming in D" book. Where will you suggest a go from there. My current focus is on network programming, database systems, data manipulation and software architectures for database related apps(mostly Linux platforms with D).
>>>
>>> I am aiming to become a hardcore and better coder(quality code) than you :) Please suggest.
>>
>
>
> Forgot to add:
>
> https://github.com/PhilippeSigaud/D-templates-tutorial

Big thanks
March 01, 2016
On 03/01/2016 12:40 PM, Daniel Kozak wrote:

> Yep, I have my copy (even print one) for some time on my desk :)
>
> https://twitter.com/kozzi11/status/700340359927349249

Nooo! :( :p

Ali

March 02, 2016
On Tuesday, 1 March 2016 at 17:21:16 UTC, David DeWitt wrote:
> On Tuesday, 1 March 2016 at 16:50:12 UTC, karabuta wrote:
>> I am aiming to become a hardcore and better coder(quality code) than you :) Please suggest.
>
> I'd probably skim thru the Language Reference and Phobos.

Just to add to this - the quality and style of the code in Phobos varies greatly from module to module, mostly as a function of age. Many of the older Phobos modules were designed before anyone really knew how to use D2 properly.

The newer modules are generally of high quality and reflect a more mature understanding of the language; I strongly suggest surveying the code base as a whole before studying any one module too closely - otherwise you might pick up some bad habits from the more out-dated parts of Phobos.

Also, if you're looking for examples of good, idiomatic code, stay away from DMD (which was only recently converted to D, and still contains many artifacts of its C++ heritage) and D runtime, which hasn't benefited from the same high level of attention and continual reworking as Phobos.
« First   ‹ Prev
1 2