Perl 6 - the future is here, just unevenly distributed

IRC log for #webwork, 2014-04-15

| Channels | #webwork index | Today | | Search | Google Search | Plain-Text | summary

All times shown according to UTC.

Time Nick Message
02:47 mgage_ joined #webwork
03:26 mgage_ joined #webwork
03:50 rbeezer joined #webwork
11:20 mgage_ joined #webwork
13:10 goehle joined #webwork
14:35 shdw_work joined #webwork
14:36 mgage_ joined #webwork
14:52 rbeezer joined #webwork
15:39 goehle hey mgage or mgage_
15:39 mgage_ hi geoff
15:40 goehle so I managed to get a little bit ahead on my lectures and have break for the next few days
15:40 goehle so I wnated to get started on my project.
15:41 goehle The current plan is to not do any of the database or object oriented refactoring
15:41 mgage_ ok
15:41 goehle add a table for jitar sets to the database
15:41 goehle and tack it onto webwork much the same way that gateway sets are done now
15:42 mgage_ ok.  that will probably get the project going quickest.  keep notes about how you might like the whole Database to be refactored at some later date.
15:43 goehle i'm a little uneasy with the approach since its just adding to the problem and not making anything better
15:45 mgage_ yeah — but sometimes you have to see the full extent of the problem before you can fix it.
15:45 mgage_ in particular getting a good design for the database is going to take some time which you probably don’t have for this particular project.
15:46 goehle I suppose
15:46 goehle its going to make the content generator code even worse
15:46 goehle and I dont know how the transition to the new interface will work
15:46 goehle the deeper peter gets with the current db
15:46 goehle the harder it will be to move over to the new one
15:47 goehle in any case, I'm not proficient enough to lone wolf it so that kind of discussion will have to wait
15:53 mgage_ sorry — had a distraction
15:56 mgage_ that may be the choice we have to live with for now.  I’m afraid that I’m still not ahead with my lectures and other preparations but I’m keeping this issue in mind as something to look at more closely — hopefully with several people and if possible with someone with actual heavy duty database design experience. (still looking for that person :-) )
15:56 goehle I'm sure mark would be willing to help
15:56 goehle (the cs prof here to went to the code camp)
15:56 goehle he definitely does things mysql style
15:57 goehle I asked him for a lot of advice when putting together the db design
15:57 mgage_ I’m feeling that the sql style is ok for the type of data we are collecting on the student-problem state.  It fits pretty well into the table/row format.
15:59 mgage_ What doesn’t fit so well is maintaining state for the app front end — that’s a much more object oriented or document oriented type of db.   it’s possible that we’ll want two types of databases.
15:59 mgage_ I’m also continuing to look at foundationDB which seems to be trying to bridge the gap — David was intrigued by their approach.
17:32 mgage_ joined #webwork
18:21 mgage_ joined #webwork
19:14 mgage_ joined #webwork
22:24 mgage_ joined #webwork
23:54 mgage_ joined #webwork

| Channels | #webwork index | Today | | Search | Google Search | Plain-Text | summary