Please create an account to participate in the Slashdot moderation system


Forgot your password?

Comment Re:Nice summary! (Score 1) 123

It's only common within a subset of the community.

I've been a Slashdot reader forever; I own a smartphone; I have been a professional programmer since before they even had smartphones. But until I joined a group that actually had to interact with MDM software (I do email sync; we need to interact with policy managers to support Exchange ActiveSync policies), I had never heard of MDM as an acronym.

Comment Re:TRS-80 Basic (Score 1) 78

My first computer was a ZX80 -- fond memories!

I liked it enough that my hobby Calculator app for Windows is now programmable in BASIC. It turns out that making a BASIC interpreter is pretty simple these days; there's a bunch of parser-generators to make it simple to program up the language, and modern computers are super-fast even when dealing with non-optimized code. In fact, the hard part is that people expect more GUI bits in the code, and getting those to all work took longer than the actual programming.

The downside is that it doesn't emulate any particular computer, and it's missing some nice features like "graphics" and "multiple statements on a line".

Link to app:

Link to manual:

Comment Re:Feedback (Score 2) 232

Yes....and no. There are four codes like you say -- T40.8X1, .8X2, .8X3 and (no surprise) .8X4.

But you know what? Each of the drug overdose sections includes the same subtypes, and using the same codes (except that actually LSD is an outlier; the other ones in the same section include items for "Adverse effect" and "underdosing".

Doctors (and intake nurses) who use electronic patient records (which should be most by now) should find that their software will guide them through the codes as they enter the patient data.

Comment Re:Shouldn't this work the other way? (Score 1) 194

You go to war with the army you have

What we have is Unicode and a good set of font fallbacks. What we don't have is an unspecified, unplanned, unwritten way to somehow insert a "pictogram" inside my stream of "glyphs".

What we need is a way to draw shapes on a screen or piece of paper where a designer gets to pick roughly what they look like. Unicode does that, and therefore seems like an adequate tool for this job.

Comment Re:Shouldn't this work the other way? (Score 1) 194

Yes, except that they didn't. They took a list of eight items (section of the underlying CODEX STAN 1-1985), and presented a proposal for seven of them. What happened to the last? I don't know: perhaps they didn't figure out how to make a character for "Sulphite in concentrations of 10 mg/kg or more".

They also missed section 5.2.1, irradiated foods, with a separate symbol.

Comment Re:The difference... (Score 1) 97

I've recently been pawing through my old Basic manuals (I'm implementing a Basic environment for run). And what stands out is how incomplete and limited most of the old environments were (although I did love them at the time).

The Basics were grossly limited. Examples includes the Sinclair AND and OR statements, the very limited FN statements and severe limitations on FOR loops. Given the high expense of disks in those days, it's no surprise that disk handling was uneven at best.

Networking capabilities were trivial to non-existent, and mostly non-existent.

The connection to their environment was deeply weird. From a modern perspective, the first thing we normally do when we see a bit of hardware is to wrap it in a little bit of code to make it simpler to control. The common pattern in the old days was to revel in the POKE and PEEK statements, directly setting hardware registers.

The difference between then and now is that then my plan was to write an program to play lunar lander. My plan today is to write a program that will listen to my mailboxes and change the color of my lights accordingly ("Make it pink!", "Make it blue!")

Comment Re:SubjectsInCommentsAreStupid (Score 1) 529

So, of that persons comments, the one about branded actually makes sense. Different companies actually do work on different frequencies (and there's a bunch of other differences; frequency is just part of it). Once we posit that some microwaves cause problems, it's very reasonable that different frequencies would cause more or fewer problems.

Comment Re:Two things... (Score 1) 583

I'm going to rephrase what you said, and change it. Don't whine at your boss. Don't complain at your boss.

But do ask for advice ("this other team is delivering really slowly, how should I handle it?", or, "I think I have a better solution for the problem of the day, but I'm having trouble advocating for it, can you help me?")

And let them know when you're behind. My company takes the output of many, many teams and sells the result; there's nothing they hate more than surprises.

Comment Re:Last week I tried to write a Win8.1 universal a (Score 1) 133

I've got several apps in the store. Most of the UI code is fully shared, and moderately adoptive to screen size. In a few places, I needed something special for one or the other.

My trick is that the 8.1 universal apps have two mainpage.xaml files (one for desktop, one for phone). I just make a shared UserControl. Each MainPage just has one object, which is the shared control

(BTW: I work at Microsoft, but not in the group that does XAML; my way works but that doesn't mean there isn't a better way)

Comment Re:Lift the gag order first... (Score 1) 550

It's called, "the general operations budget" I work for a big company; from on high we get general guidelines ("computers are expected to last xyz years" and "you have abc to spend on travel this year"). itt's up to the more lower-level people to decide how to portion it out.

In the FCC's case, congress has already given them money to inforce their regulations (and gave them the authority to make the regulations, but also gave them requirements like hainvg a certain number of public hearings). The FCC can then spend it on those things.

Slashdot Top Deals

All the simple programs have been written.