Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!

 



Forgot your password?
typodupeerror

Slashdot videos: Now with more Slashdot!

  • View

  • Discuss

  • Share

We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).

×

Comment: Re:No one is forcing anyone to do anything (Score 1) 536

He purchased the space with the designated purpose of writing code. This isn't akin to conducting business in an office setting (seeing clients, conducting meetings, etc.). It is more akin to writing prose. If he feels he is more productive in a personal setting, then this is no different from a novelist renting a cabin in the woods to finish that novel that's just not getting out. Would anyone recommend a novelist to rent office space instead of a somewhat isolated personal space to do creative work?

Bullshit. Writing code is not writing pose, and the artistic characteristics of software development drown in the setting of engineering and problem solving.

No, I wouldn't recommend a novelist to rent an office space to write the next "The Old Man and the Sea", but this is not a novelist, but a software developer (or artistic code monkey or whatever) that needs fast internet access at an affordable price to make his living.

What he does is his business. But don't tell me that selling his house instead of renting office space is an objective, rational decision (it isn't), and don't tell me he is an artist that needs green space to arrange bytes into perfection, because that is bullshit and no one pays a developer to be a Dali or Hemingway of coding.

Comment: Re:welcome to home buying 101 (Score 1) 221

by luis_a_espinal (#49354025) Attached to: Broadband ISP Betrayal Forces Homeowner To Sell New House

"Always verify everything yourself and don't trust anyone.

Pay for the previous owner's internet for a month or two"

That's very easy to be said -after the fact.

What else should the prospective owner pay before buying the house just in case? Sewage? tap water? electricity? Maybe he also should burn out the house just to see if the firefighter brigade can really appear in time, right?

Apples and oranges. The items you mentioned are required by law to be accessible if they are mentioned explicitly or implicitly in a home purchase contract, are typically provided via the local government, and are part of a standard inspection. Fast internet access is not.

This is one of the reasons I always look for existing bills of service (internet) before I move in anywhere. And I like the idea of offering paying for installation of internet -or have it deducted it from the final sale price. It is something I will be trying in the next few weeks as I buy a house...

And this is another reason why I will never leave in the boondocks. If I require tech to make my living, I will stay in a tech hub, or in a worst case scenario, within trivial driving distance to a rental office space with the services I require.

Unless our country becomes like, I dunno, Finland, living in a remote area is a risky proposition for anyone who relies on fast internet at relatively affordable prices to make one's living.

Comment: Re:No one is forcing anyone to do anything (Score 2) 536

Presumably he paid for a home space which would accommodate the office. What he should or shouldn't do is pretty much his business and his alone.

Yes, it is his business alone, but that doesn't insulate him from reasonable criticism of his choices. Exploring the choice of renting office space is much,much cheaper than reselling a home, specially one recently purchased.

Comment: Re:No one is forcing anyone to do anything (Score 1) 536

Heck, he could, you know, rent an OFFICE to conduct his business from that has connectivity. There are tons and tons of incubator spaces that would be happy to have his business.

I've conducted business from home. It sucks. There are many good reasons to separate work and home.

You took the words right out of my mouth (or keyboard). This is one of my plan-B's when I work from home and internet connectivity at works sucks. It sucks to pay an extra few hundred dollars a month, but it sucks less than not working or having to relocate.

Comment: Re:Seriously... (Score 1) 757

by luis_a_espinal (#49275675) Attached to: Was Linus Torvalds Right About C++ Being So Wrong?

That's what "typedef" is for. Put "typdef" in front, replace signal with signal_handler, and it's only really ugly in one place.

Or cdecl...

Of course. IRL we would use typedef to manage that kind of ugliness. But one will always encounter definitions like that - signal will never be defined with a typedef in any form of POSIX documentation.

Thus working at certain levels, it is important to understand such declarations (if not fully, at least partially to ask the right questions.)

Comment: Seriously... (Score 1) 757

by luis_a_espinal (#49229483) Attached to: Was Linus Torvalds Right About C++ Being So Wrong?
Seriously, if we are going to complain about crazy parsing, pointer to array of ints is not a good example. This is a good (and thank goodness, relatively obscure) example:

void (*signal(int, void (*)(int)))(int)

with signal as a function that takes one int and one pointer to function that takes one int and returns void, and which in turn returns a pointer to function which takes an int and returns void. Thankfully, this shit is seldom seen in most applications of C, except in very specialized cases.

The rest of cases it's nothing mind-warping if you know the rules.

Comment: Re:Syntax and typo errors compile (Score 1) 757

by luis_a_espinal (#49229393) Attached to: Was Linus Torvalds Right About C++ Being So Wrong?

gahh. I just typoed my example!!! oops. int (*foo)[20]; int *foo[20];

But I bet that error would even compile!

Not mind boggling. A person that works in C *must* know the syntax and how that stuff gets parsed.

First a pointer to an array of 20 ints (the parenthesis binds the '*' to the variable, making it a pointer). Second, an array of 20 pointers to int (the [20] binds to the variable, making it an array of 20 something, that something being determined by int * (pointer to int).

Yes, the parsing is idiotic (go right till no more, then left till no more and non-sense like that), but the rules have existed forever. And to me, that is a prerequisite to work in C... and when in doubt, use cdecl.

Comment: Gawd! Damnit, not Mayans! (Score 3, Interesting) 61

by luis_a_espinal (#49181293) Attached to: Lost City Discovered In Honduran Rain Forest

Or someone very closely related to them? You know, the group in that area that formed a thriving civilization that supposedly fell apart during a drought...RIGHT AT THAT TIME?

Those unknown people?

Mayans were only one of the many people living in the area. There were/are Pech in the East (linguistically affiliated with Macro-Chibchan), the powerful Lenca in the north west (also Macro-Chibchan) living where the Mayan once were, Tolupan/Xicaque (language isolate), Pipil (Uto-Aztecan), Ulwa, Tawahka, Mayagna, and Matagalpa (Misumalpan), etc.

That is, Mayan are just the best known culture in Honduras. They weren't even the predominant culture anymore by the time of the Spanish conquest of Honduras. I've been hearing the rumors of the "White City" since the late 80's, and we keep finding archeological stuff in Honduras and Nicaragua which are really hard to categorize as cultures go.

The location of it, in the Mosquitia region, far to the east, is waaaay too far away from the Honduran Mayan homelands. The culture from this site are almost certainty neither Mayan nor Lenca. I doubt they are Tolupan because the proposed Tolupan homeland is to the north of Honduras.

By the geographic location of it, the culture was either Proto-Pech or Misumalpan (or even a culture long gone with no linguistic/ethnic survivors).

Comment: WTF? Ease of analysis =/= ease of maintenance??? (Score 1) 247

by luis_a_espinal (#49181169) Attached to: Study: Refactoring Doesn't Improve Code Quality

A team of researchers in Sri Lanka set out to test whether common refactoring techniques resulted in measurable improvements in software quality, both externally (e.g., Is the code more maintainable?) and internally (e.g., Number of lines of code). Here's the short version of their findings: Refactoring doesn't make code easier to analyze or change (PDF); it doesn't make code run faster; and it doesn't result in lower resource utilization. But it may make code more maintainable.

From the OP, how the fuck do we reconcile this:

Refactoring doesn't make code easier to analyze or change

with this:

But it may make code more maintainable.

Seriously, those two statements conflict with one another. And since when refactoring was done primarily to make things run faster or more efficient resource-wise? Optimization is typically an architectural issue, or a point of local optimization in changing algorithms and data structures. Refactoring for the most part has always been about structural changes to enable analysis, re-usability and replacement and to ensure correctness (or at least to avoid introducing new fuck-ups.)

On The Onion News at 11, refactoring does not make code more eco-friendly/gmo-free.

Comment: Re:Crime (Score -1, Troll) 538

Shes a democrat, she could kill children on the street and get away with it.

Unlike Republicans who have gotten our soldiers and drones in a position to kill civilians of all genders and ages, even children, in Iraq and Afghanistan, and whom are all in jail because of that... err, wait.

Seriously, stop injecting your stupid political pet peeves in every conversation. How old are you? 10?

Fools ignore complexity. Pragmatists suffer it. Some can avoid it. Geniuses remove it. -- Perlis's Programming Proverb #58, SIGPLAN Notices, Sept. 1982

Working...