The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
Finding client is a big problem. I am aware that the websites where we bid to get the job include a large number of small companies who work through that. This reduces chance of independents to get something. Moreover, the kind of work offered there needs a giant sieve to get to something good.
Walt Fair, Jr. wrote:
The object is not to ofer the latest technology, the object is to solve probnlems that you clients need solved!
As of now, I have decided to stick to a normal full time job. I am working on writing a complete website with a decent range of technologies just to showcase what I have and can work with. In few months that should be out on the web and hopefully that will help getting some visibility.
I am using hopefully, as I have made a habit of putting my CP profile link on the resume and also SO profile. But thus far it seems that is irrelevant. I would still not remove it though.
So I got this scenario where I have like 4000+ objects which can all be linked to the 3999+ other objects.
One lookup containing 4000 objects (needs to be paged or whatever).
One table containing 3999 objects minus the ones that are already linked (needs to be paged).
Another table containing 3999 objects minus the ones that aren't linked yet (needs to be paged).
The problem isn't getting the data from the back-end to the front-end, I've optimized the sh*t out of that (it's probably even faster than doing additional round-trips).
The problem also isn't that so much data makes everything unclear to users, paging will only make it less clear I think.
The processing of the data on the front-end is pretty simple, so that's also not the bottleneck.
The only problem is that a browser can't render so much data in under ten seconds, which is pretty detrimental to the user experience
Don't know about your scenario, but how about an master-detail (vertical split screen) endless list (loading more data dynamically when needed/visible) combined with some filtering to easy the pain to begin with?
In order to understand stack overflow, you must first understand stack overflow.
The trouble with the endless list is that the items can be modified, so you certainly want some filtering, and you need to be able to "remember" edits even when the data is unloaded.
Luckily, my list isn't endless though
The data won't grow all that much, so my current scheme will work at least for the years to come.
I've currently got 8000 items and it still performs really well (except for a lookup, which takes a second to open).
I've found a select module that will handle a lot of the work for me, so I might do this the "will-scale-up-to-infinity" way after all.
That will pose new difficulties, like you're trying to edit data that's not actually loaded yet and may unload when a new page is selected.
Man, I hate paging and the additional work that comes with it
I've currently got 8000 items and it still performs really well
I seriously doubt that it works "really well" for the users that actually need to use the page.
They presumably need to find something on that page and they know what they are looking for. So rather than tell you so you can return just that they must manually scan those 8000 items, one average of course probably at least 4000 lines, to find it.
It's a composite of visible light from Hubble (the central galaxy, over 1000 times more massive than the Milky Way) and radio data from VLA - the plasma jets are over 1,000,000 light years long. Hercules A - Wikipedia[^]
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!