### Author:  [@essenciary](https://discourse.julialang.org/u/essenciary)
#### Post date: [October 18, 2017, 8:09pm UTC](https://discourse.julialang.org/t/looking-for-technical-reviewer-for-my-upcoming-julia-book/6531/1 "2017-10-18T20:09:05Z")
I’m working with Packt on “Julia v1.0 By Example”, a beginner’s book about Julia. It covers various topics related to data science and general and web computing. I’m putting a lot of time, energy and love into the book - I’m hoping it’s going to help some people find their way into programming with Julia and enjoy it as much as I do. I really want to come out as a valuable resource and contribute to the growth of the language and its great community.
Part of it is that we need the support of a technical reviewer, and again, I’m reaching out to the awesome Julia users 🙂
I’m looking for a partner to work with me on the project as the technical reviewer: go over the book, provide feedback about the code, ideas for improvement of the technical info, squash bugs, etc. If you’re interested, please message me, I’ll put you in touch with the Packt team for more details. Thanks!
---
### Author:  [@o314](https://discourse.julialang.org/u/o314)
#### Post date: [October 18, 2017, 10:07pm UTC](https://discourse.julialang.org/t/looking-for-technical-reviewer-for-my-upcoming-julia-book/6531/2 "2017-10-18T22:07:24Z")
> [@essenciary](#):
>
> ergy and love into the book - I’m hoping it’s going to help some people find their way into programming with Julia
That’s good news!
Nothing to see with Genie.jl inside by the way?
---
### Author:  [@Tamas\_Papp](https://discourse.julialang.org/u/Tamas_Papp)
#### Post date: [October 19, 2017, 8:34am UTC](https://discourse.julialang.org/t/looking-for-technical-reviewer-for-my-upcoming-julia-book/6531/3 "2017-10-19T08:34:26Z")
> [@essenciary](#):
>
> various topics related to data science
While in general I am very happy to see new books appear on Julia, and I also think that examples are the best way to do it, are you sure that this is the best time for it given the current state of transition in the DataFrames ecosystem? I suspect that by the time the ink dries, most examples will not run.
---
### Author:  [@essenciary](https://discourse.julialang.org/u/essenciary)
#### Post date: [October 19, 2017, 9:27am UTC](https://discourse.julialang.org/t/looking-for-technical-reviewer-for-my-upcoming-julia-book/6531/4 "2017-10-19T09:27:06Z")
It’s pretty much work in progress. The book targets the v1.0 release of Julia - with a preliminary publishing date for spring 2018. So yes, some of the APIs will change for sure and I’ll just have to update the code accordingly. But I expect that by the time we see a Julia v1.0 release, the DataFrames public APIs will be stable. What do you think? Also, can you please point me to the documentation regarding breaking API changes in the upcoming DataFrames?
---
### Author:  [@essenciary](https://discourse.julialang.org/u/essenciary)
#### Post date: [October 19, 2017, 10:56am UTC](https://discourse.julialang.org/t/looking-for-technical-reviewer-for-my-upcoming-julia-book/6531/5 "2017-10-19T10:56:11Z")
Probably not 🙂 The web development parts are more about supporting data science features (web mining, exposing data on the web, etc), so very light stuff. So far I’m going with HTTP.jl.
For Genie, the plan is to use my newly acquired literary skills to write the long overdue guides and proper docs. 😊
---
### Author:  [@Tamas\_Papp](https://discourse.julialang.org/u/Tamas_Papp)
#### Post date: [October 19, 2017, 11:02am UTC](https://discourse.julialang.org/t/looking-for-technical-reviewer-for-my-upcoming-julia-book/6531/6 "2017-10-19T11:02:21Z")
I am not the best person to ask about his, but this post could be a good starting point:
> [@Announcement: An Update on DataFrames Future Plans](https://discourse.julialang.org/t/announcement-an-update-on-dataframes-future-plans/4646):
>
> This post summarizes the current roadmap for DataFrames.jl and the data ecosystem in general for the Julia 1.0 milestone. Plans have changed significantly since [the previous post](https://discourse.julialang.org/t/announcement-dataframes-future-plans/266). Indeed, it has appeared that representing missing values via the special Nullable type is not the only solution to attain a high performance in Julia. Thanks to [work](https://github.com/JuliaLang/julia/pull/20593) [done](https://github.com/JuliaLang/julia/pull/22441) by @jameson and @quinnj, it turns out that representations of nullable values similar to that used by DataArrays (i.e. Union{T, NAtype}) can also be …
Some of the issues/PRs mentioned there have been resolved already, look on Github for new ones 😉
Also
>
>
> This issue lists packages which depend on DataFrames, with links to PRs which po…rt them to the new \`Missing\` and \`CategoricalArray\` based DataFrames. Please add new PRs as they are opened to track progress, and check boxes once they have been merged. Some packages may not need any adjustments and could be moved to a separate section.
>
> Packages with open PRs (tick the box once PR is merged):
> \- \[x\] CSV: https://github.com/JuliaData/CSV.jl/pull/95
> \- \[x\] CovarianceMatrices: https://github.com/gragusa/CovarianceMatrices.jl/commit/0d12f70c8cd82251257918014a479f042c3864c2
> \- \[x\] DataFramesMeta: https://github.com/JuliaStats/DataFramesMeta.jl/pull/79
> \- \[x\] ExcelFiles
> \- \[x\] ExcelReaders
> \- \[x\] Feather: https://github.com/JuliaStats/Feather.jl/pull/48
> \- \[x\] FixedEffectModels: https://github.com/matthieugomez/FixedEffectModels.jl/pull/20
> \- \[x\] FreqTables: https://github.com/nalimilan/FreqTables.jl/pull/16
> \- \[x\] Gadfly: https://github.com/GiovineItalia/Gadfly.jl/pull/1088 https://github.com/GiovineItalia/Gadfly.jl/pull/1090
> \- \[x\] GeoStats
> \- \[x\] GeoStatsDevTools
> \- \[x\] IterableTables: https://github.com/davidanthoff/IterableTables.jl/pull/60, https://github.com/davidanthoff/IterableTables.jl/pull/62
> \- \[x\] LogParser
> \- \[x\] Microeconometrics: https://github.com/lbittarello/Microeconometrics.jl/commit/ef496df7527e9060e8626bb415362908e6c71b12
> \- \[x\] Mimi
> \- \[x\] MixedModels: https://github.com/dmbates/MixedModels.jl/pull/103
> \- \[x\] MySQL: https://github.com/JuliaDB/MySQL.jl/pull/91 https://github.com/JuliaDB/MySQL.jl/pull/92
> \- \[x\] ODBC: https://github.com/JuliaDB/ODBC.jl/pull/173
> \- \[x\] PlotlyJS: https://github.com/sglyon/PlotlyJS.jl/pull/145
> \- \[x\] Quandl: \[milktrader/Quandl.jl#111\](https://github.com/milktrader/Quandl.jl/pull/111)
> \- \[x\] Query: https://github.com/davidanthoff/Query.jl/pull/155
> \- \[x\] QueryOperators: https://github.com/davidanthoff/QueryOperators.jl/pull/2
> \- \[x\] RCall
> \- \[x\] RData: https://github.com/JuliaStats/RData.jl/pull/28
> \- \[x\] RDatasets: https://github.com/johnmyleswhite/RDatasets.jl/pull/48 (package works with 0.11 already with deprecation warnings)
> \- \[x\] ReadStat
> \- \[x\] ScikitLearn: https://github.com/cstjean/ScikitLearn.jl/commit/9555a438b2c7b3d90577958b213a9c462abc7dd9
> \- \[x\] SQLite: https://github.com/JuliaDB/SQLite.jl/pull/131
> \- \[x\] StatFiles: https://github.com/davidanthoff/StatFiles.jl/commit/a171896d6df02e7ac0deb03b4ab1218f0efee18b
> \- \[x\] StatsModels: https://github.com/JuliaStats/StatsModels.jl/pull/30
> \- \[x\] Taro: https://github.com/aviks/Taro.jl/pull/38
> \- \[x\] UAParser
>
> Packages which do not need any changes:
> \- \[x\] StatPlots
> \- \[x\] Twitter
>
> Packages which need new PRs:
> \- \[\] BeaData
> \- \[\] Bedgraph
> \- \[\] BedgraphFiles
> \- \[\] Benchmark
> \- \[\] BioMedQuery
> \- \[\] BlsData
> \- \[\] Bootstrap
> \- \[\] Brim
> \- \[\] COMTRADE
> \- \[\] Celeste
> \- \[\] CrossfilterCharts
> \- \[\] DBFTables
> \- \[\] DSGE
> \- \[\] DataCubes
> \- \[\] Deldir
> \- \[\] DimensionalityReduction
> \- \[\] Diversity
> \- \[\] EEG
> \- \[\] EasyPhys
> \- \[\] EconDatasets
> \- \[\] EconModels
> \- \[\] EventHistory
> \- \[\] ExperimentalAnalysis
> \- \[\] FaSTLMM
> \- \[\] FinancialMarkets
> \- \[\] FredData
> \- \[\] GeoIP
> \- \[\] Gillespie
> \- \[\] GoogleCharts
> \- \[\] Graft
> \- \[\] GraphGLRM
> \- \[\] Hive
> \- \[\] InteractiveFixedEffectModels
> \- \[\] JWAS
> \- \[\] JuliaFEM
> \- \[\] LazyQuery
> \- \[\] LifeTable
> \- \[\] LinguisticData
> \- \[\] LowRankModels
> \- \[\] MLDataUtils
> \- \[\] MachineLearning
> \- \[\] Mads
> \- \[\] mPulseAPI
> \- \[\] MultidimensionalTables
> \- \[\] NLOptControl
> \- \[\] NLreg
> \- \[\] OdsIO
> \- \[\] OpenGene
> \- \[\] OpenSecrets
> \- \[\] OptiMimi
> \- \[\] PGFPlots
> \- \[\] PhyloNetworks
> \- \[\] PrettyPlots
> \- \[\] ProjectTemplate
> \- \[\] PySide
> \- \[\] Q
> \- \[\] ROCAnalysis
> \- \[\] Resampling
> \- \[\] Rif
> \- \[\] Robotlib
> \- \[\] RobustStats
> \- \[\] SloanDigitalSkySurvey
> \- \[\] Sparrow
> \- \[\] SpatialEcology
> \- \[\] SpeedDate
> \- \[\] StackedNets
> \- \[\] TermWin
> \- \[\] TextAnalysis
> \- \[\] TimeData
> \- \[\] TimeSeriesIO
> \- \[\] ValueOrientedRiskManagementInsurance
> \- \[\] WorldBankData
> \- \[\] XSim
> \- \[\] ZipCode
>
> Abandoned packages:
> \- \[x\] kNN
>
> Packages that already did not load on Julia 0.6:
> \- \[x\] Augur
> \- \[x\] BIGUQ
> \- \[x\] BayesNets
> \- \[x\] BayesianDataFusion
---
### Author:  [@essenciary](https://discourse.julialang.org/u/essenciary)
#### Post date: [October 19, 2017, 11:16am UTC](https://discourse.julialang.org/t/looking-for-technical-reviewer-for-my-upcoming-julia-book/6531/7 "2017-10-19T11:16:08Z")
Thank’s so much @Tamas_Papp!
---
### Author:  [@davidbp](https://discourse.julialang.org/u/davidbp)
#### Post date: [October 19, 2017, 11:26am UTC](https://discourse.julialang.org/t/looking-for-technical-reviewer-for-my-upcoming-julia-book/6531/8 "2017-10-19T11:26:39Z")
There is no need to focus or even use dataframes. Scikit-learn is all build under the assumtion that the input and output data comes from arrays.
---
### Author:  [@nalimilan](https://discourse.julialang.org/u/nalimilan)
#### Post date: [October 19, 2017, 11:44am UTC](https://discourse.julialang.org/t/looking-for-technical-reviewer-for-my-upcoming-julia-book/6531/9 "2017-10-19T11:44:37Z")
The docs for the next DataFrames release are already online (there’s also an open PR to improve them): [Introduction · DataFrames.jl](https://juliadata.github.io/DataFrames.jl/latest)
Of course there’s no guaranty the API won’t change during the next year (though in general code won’t break without printing a deprecation first).
---
### Author:  [@Tamas\_Papp](https://discourse.julialang.org/u/Tamas_Papp)
#### Post date: [October 19, 2017, 11:59am UTC](https://discourse.julialang.org/t/looking-for-technical-reviewer-for-my-upcoming-julia-book/6531/10 "2017-10-19T11:59:13Z")
Certainly, but
1. a `DataFrames`-like representation with named columns, and
2. consistent handling of missing data
make data analysis much more convenient. That’s why so many languages have these features.
---
### Author:  [@cstjean](https://discourse.julialang.org/u/cstjean)
#### Post date: [October 19, 2017, 12:03pm UTC](https://discourse.julialang.org/t/looking-for-technical-reviewer-for-my-upcoming-julia-book/6531/11 "2017-10-19T12:03:18Z")
Data science without dataframes would feel like a step back. ScikitLearn.jl [has support for them](http://scikitlearnjl.readthedocs.io/en/latest/dataframes/) ported over from [sklearn-pandas](https://github.com/pandas-dev/sklearn-pandas).
---
### Author:  [@ellisvalentiner](https://discourse.julialang.org/u/ellisvalentiner)
#### Post date: [October 19, 2017, 7:05pm UTC](https://discourse.julialang.org/t/looking-for-technical-reviewer-for-my-upcoming-julia-book/6531/12 "2017-10-19T19:05:31Z")
Oh no! You’re going to finish your book first! Oh well…
I would absolutely love to help review your book. Perhaps you can help review mine (after I actually get around to writing it).
---
### Author:  [@o314](https://discourse.julialang.org/u/o314)
#### Post date: [October 20, 2017, 7:52pm UTC](https://discourse.julialang.org/t/looking-for-technical-reviewer-for-my-upcoming-julia-book/6531/13 "2017-10-20T19:52:40Z")
Good news you will do this stuff for Genie.jl later Adrian.
I will be interested to read it.
May be i could help by drawing a few sketchs or technical diagrams.
---
### Author:  [@essenciary](https://discourse.julialang.org/u/essenciary)
#### Post date: [October 23, 2017, 11:26am UTC](https://discourse.julialang.org/t/looking-for-technical-reviewer-for-my-upcoming-julia-book/6531/14 "2017-10-23T11:26:33Z")
That would be much appreciated - I’m thinking for v1.0 I can start with the initial draft then we can use Git(Hub) to improve and maintain.
---
### Author:  [@iwelch](https://discourse.julialang.org/u/iwelch)
#### Post date: [October 23, 2017, 3:08pm UTC](https://discourse.julialang.org/t/looking-for-technical-reviewer-for-my-upcoming-julia-book/6531/15 "2017-10-23T15:08:20Z")
I looked for an email address, but could not find one, so my response has to be public.
I have a lot of students in a class in Winter quarter. I would be happy to strongly suggest a book for learning julia, even if it is just a prototype. please email me: [ivo.welch@gmail.com](mailto:ivo.welch@gmail.com)
/iaw
---
### Author:  [@essenciary](https://discourse.julialang.org/u/essenciary)
#### Post date: [October 23, 2017, 3:33pm UTC](https://discourse.julialang.org/t/looking-for-technical-reviewer-for-my-upcoming-julia-book/6531/16 "2017-10-23T15:33:58Z")
Thanks Ivo - I wrote you a PM in Discourse to follow up. You might wanna edit your public message so that the email address isn’t harvested. 🕵️♂️
---
### Author:  [@iwelch](https://discourse.julialang.org/u/iwelch)
#### Post date: [October 23, 2017, 5:14pm UTC](https://discourse.julialang.org/t/looking-for-technical-reviewer-for-my-upcoming-julia-book/6531/17 "2017-10-23T17:14:22Z")
your and my email have probably been harvested a gazillion times already, if only from emails we have sent to non-friends. the only thing that protects us are good spam filters, like gmail’s.
I am glad that julia has not closed down its syntax and semantics yet, but the drawback is that googling for solutions can often provide old, outdated, non-working answers. this is an obstacle to adoption. c’est la vis. for your book to succeed, keeping examples working all the way up to 1.0 is essential. (you should aggressively drop obsolete julia versions IMHO.) . I am looking forward to it. the more working and checked examples, the better.
regards,
/iaw
---
### Author:  [@essenciary](https://discourse.julialang.org/u/essenciary)
#### Post date: [October 23, 2017, 5:30pm UTC](https://discourse.julialang.org/t/looking-for-technical-reviewer-for-my-upcoming-julia-book/6531/18 "2017-10-23T17:30:30Z")
Yeah, I guess I’m old-fashioned, still obfuscating email addresses on websites 🙂
Absolutely - it’s not just Julia itself (which will hopefully evolve smoothly into v1.0) but (mostly) the packages. The previously discussed `DataFrames`, or `WebServer` and `Requests` morphing into `HTTP.jl` are just some of the key packages used in the examples. Staying up to date is an uphill battle now, but things will hopefully settle down around v1. Fingers crossed.
---
### Author:  [@tparker](https://discourse.julialang.org/u/tparker)
#### Post date: [October 25, 2017, 6:36am UTC](https://discourse.julialang.org/t/looking-for-technical-reviewer-for-my-upcoming-julia-book/6531/19 "2017-10-25T06:36:52Z")
Is that title set in stone? Somehow the inclusion of “v1.0” in the title strikes me as being too specific, especially considering that v1.0 will be the only officially supported version at publication time.
---
### Author:  [@essenciary](https://discourse.julialang.org/u/essenciary)
#### Post date: [October 25, 2017, 6:56am UTC](https://discourse.julialang.org/t/looking-for-technical-reviewer-for-my-upcoming-julia-book/6531/20 "2017-10-25T06:56:00Z")
Yes, good point. I’m not sure what’s the justification behind this very specific title, but I’ll ask.
The minor version is especially troubling since it suggests that it won’t work for a v1.1. Which it should, since minor versions are non-breaking.
The major version number is OK I think, as it implies breaking changes – and is a good opportunity to come up with a 2nd edition, for “v2”.
[Next page](https://discourse.julialang.org/t/looking-for-technical-reviewer-for-my-upcoming-julia-book/6531.md?page=2)