What's more, there's absolutely no evidence to back up the belief that babies require more bonding between them and their mother than with their father.
Because there's a risk of someone misinterpreting that statement as implying that parents and children or mothers and children don't need bonding - a
quickfewgoogled hits about the benefits of bonding (or risks of not bonding).
There's more out there, but I suggest to go talk to a midwife and/or doula if you are genuinely interested in knowing more about the subject.
Nothing wrong with them requiring VB skills from the beginning if they want their new developer to be able to hit the ground running. Sure, maybe you could get up to speed after a few months or even weeks, but if they don't have that time (read: money) to spare it's their choice.
A good developer would be up and running with a language that's in a similar paradigm as a known language in a matter of days or hours not weeks. What takes weeks is getting used to the new company's domain, existing code base conventions. Knowing the language doesn't help with that.
Once I was searching for a new job and an HR type rejected me because my CV did not show Visual Basic.
This really irks me these days. Most job offers are buzzword bingo with a long list of "absolutely required" niche technology du jour stuff, none of which are particularly hard to pick up if you're a half-decent developer, but you will NOT get past the HR drones because you don't tick the boxes.
If the range is weird (2-8 weeks), I push for the engineer to tighten their estimate through discussing or raising and discovering the unknowns or the risks that they are aware off.
You are potentially making a mistake there. There are often unknowns that you cannot eliminate unless by actually trying to do it, which means you have to accept the original range. You are expressing distrust of your engineers' expertise by pushing them to tighten their estimates when they have given you a wide range to indicate that type of uncertainty. Tighter is not "better", tighter is not "more realistic", sometimes the range just is weird because the problem is.
European, skinny jeans, hoodie, senior development professional for an international company, and I'm by no means an exception here. But don't let the facts get in the way of YOUR self-righteousness.
only one comment was sexual in nature. the dongle one. the other one was about forking being a form of flattery, which adria misconstrued as sexual. just as the dongle comment was inappropriate, it was equally inappropriate to post their picture to twitter w/o even confronting them.
Posting their picture publically without their explicit consent might also very well be *illegal*, which I, apparently wrongly, thought might actually be more serious than *offensive*.
I've used software that allowed only a low number of concurrent installs (I think 3), registered online. It provided an online interface to move an install: log in, unregister one of your licensed machine, get back the key you used for that one, use it for the new install. Worked well enough for me through about 6 or so moves in the past years.
Most amusing (and effective) DRM I ever saw was actually a fairly loose and easily broken copy protection scheme... the program could detect when it had been "cracked" but still gave full functionality to the cracked version... just with some interesting bugs that only appeared late game on the cracked version. It was a game, and deliberately corrupted the load of certain textures on pirated version so the game was still playable, but had quality degradation. Is it possible you could do something like that with the utility?
In general: do NOT do this without talking to a lawyer first. Deliberate hidden degradation after crack detection potentially opens you up to legal liability. You broke the user's software deliberately, any unintended consequences might be on you.
Right now the pinnacle of story-driven game achievement seems to be: a decent prewritten linear plot with depth that is supported well by the gameplay mechanics, with maybe a few branches here and there. That's still very cool, and if done right with the proper characterizations you hardly even notice (or care) that you're being railroaded. You, as the protagonist, feel that the choices made by the writer are the correct ones for the character.
However, I'm hoping that at some point in the near future there will be the possibility of a game that creates a story arc with decent depth through extrapolating and manipulating the actions taken by the player in the game. Something that wraps around gameplay actions to create quite different story arcs for different gameplay choices. This will have its limits, mostly because it does require the player to actually attempt to make meaningful choices - purely random play is unlikely to emerge into a good arc.
"Whether it was sensible or not doesn't matter - it is the Law"
I think you show an obvious lack of critical thinking and so you should not have the right to vote.
No, you are reading something into my post that isn't there. I am simply pointing out that there is a cause and effect relationship with breaking the law and/or a contract. The parameters of the effect in this particular case were clearly set out in the agreement between Microsoft and the EU, and Microsoft agreed to them before breaking the agreement.
Finally, why does having the **right to vote** matter to you, if you don't actually accept the rule of law?
It was illegal and a violation of the agreement that Microsoft themselves signed with the EU after Microsoft lost the browser bundling court case. That's all that matters. The EU said "you can't do that" to Microsoft, Microsoft fought it hard in court, Microsoft lost, Microsoft agreed to a specific remedy, Microsoft then violated that remedy, Microsoft gets fined to send a message to any company that might think it's not that big a deal to violate a legal agreement with the EU.
Whether it was sensible or not doesn't matter - it is the Law, and as a company you cannot flip off the Law and expect to get away with it.
With documentation you usually just get an API reference, and maybe a simple example. With community sites like Stack Overflow you get vetted examples and best practices from real world users. It's almost always more helpful than just a static reference.
Or put another way: knowing all the components (documentation) doesn't necessarily mean you grok the system (stackoverflow).
When you follow the API and your program doesn't work,
That's a pretty good indication that the docs are bad
Or that the API complexity is beyond what's capturable in reasonable "what this call does" style documentation. This happens very quickly in modern OO designs that follow the SOLID principles, because absolutely nothing is completely "local". What I mean by that is that in order to fully understand a single API call or class, you also need to understand all its parameter types, its injected dependencies, its superclasses, in some cases its derived classes, etc. etc.
Documentation of the type "what does this class do" or "what does this API call do" almost never captures the full complexity / possibilities of the system. What *you* want to do with that class may have specific effects in all those dependencies that cannot (and should not) reasonably be documented in the API call, but in the dependencies, but if you don't know where to look, you'll never find it.
Slashdot Mirror
Damn, I thought this was going to be the last forking warning against posting Bitcoin stories on Slashdot.
It's still a better measure than not trying to measure it at all
I find that 5 friends from a non-existent social circle are even more secure.
What's more, there's absolutely no evidence to back up the belief that babies require more bonding between them and their mother than with their father.
Because there's a risk of someone misinterpreting that statement as implying that parents and children or mothers and children don't need bonding - a quick few googled hits about the benefits of bonding (or risks of not bonding).
There's more out there, but I suggest to go talk to a midwife and/or doula if you are genuinely interested in knowing more about the subject.
Nothing wrong with them requiring VB skills from the beginning if they want their new developer to be able to hit the ground running. Sure, maybe you could get up to speed after a few months or even weeks, but if they don't have that time (read: money) to spare it's their choice.
A good developer would be up and running with a language that's in a similar paradigm as a known language in a matter of days or hours not weeks. What takes weeks is getting used to the new company's domain, existing code base conventions. Knowing the language doesn't help with that.
You can have things on your phone that you can't have in a briefcase in your car.
You can have your *phone* in your briefcase in your car.
you will NOT get past the HR drones because you don't tick the boxes
But do you really want to work for those kind of companies anyway?
I'm willing to bet many of those companies are perfectly fine, once you get past HR's incredibly myopic view.
I think a better question would be, how often does something genuinely new come along?
Every time HR gets a new buzzword to give reason to reject your application because it doesn't mention said buzzword.
Once I was searching for a new job and an HR type rejected me because my CV did not show Visual Basic.
This really irks me these days. Most job offers are buzzword bingo with a long list of "absolutely required" niche technology du jour stuff, none of which are particularly hard to pick up if you're a half-decent developer, but you will NOT get past the HR drones because you don't tick the boxes.
Come on mods, mod the AC up!
If the range is weird (2-8 weeks), I push for the engineer to tighten their estimate through discussing or raising and discovering the unknowns or the risks that they are aware off.
You are potentially making a mistake there. There are often unknowns that you cannot eliminate unless by actually trying to do it, which means you have to accept the original range. You are expressing distrust of your engineers' expertise by pushing them to tighten their estimates when they have given you a wide range to indicate that type of uncertainty. Tighter is not "better", tighter is not "more realistic", sometimes the range just is weird because the problem is.
Did they go ballistic b/c they thought they were paying for 54 months, or because you confirmed that their goal of 6 months wasn't possible?
Knowing the industry, the answer is probably both, at the same time.
What kind of shoes do you wear?
Dynamically typed ones.
European, skinny jeans, hoodie, senior development professional for an international company, and I'm by no means an exception here. But don't let the facts get in the way of YOUR self-righteousness.
Sounds like you have a bee in your bonnet about this.
It's under his tin foil hat, unable to communicate with the outside world :(
Back in my day, we programmed with one bit... uphill... both ways.
You mean one way uphill until you wrapped around the universe back to the bottom of the hill!
only one comment was sexual in nature. the dongle one. the other one was about forking being a form of flattery, which adria misconstrued as sexual. just as the dongle comment was inappropriate, it was equally inappropriate to post their picture to twitter w/o even confronting them.
Posting their picture publically without their explicit consent might also very well be *illegal*, which I, apparently wrongly, thought might actually be more serious than *offensive*.
"Gazole" is diesel in french actually.
I've used software that allowed only a low number of concurrent installs (I think 3), registered online. It provided an online interface to move an install: log in, unregister one of your licensed machine, get back the key you used for that one, use it for the new install. Worked well enough for me through about 6 or so moves in the past years.
Most amusing (and effective) DRM I ever saw was actually a fairly loose and easily broken copy protection scheme... the program could detect when it had been "cracked" but still gave full functionality to the cracked version... just with some interesting bugs that only appeared late game on the cracked version. It was a game, and deliberately corrupted the load of certain textures on pirated version so the game was still playable, but had quality degradation. Is it possible you could do something like that with the utility?
In general: do NOT do this without talking to a lawyer first. Deliberate hidden degradation after crack detection potentially opens you up to legal liability. You broke the user's software deliberately, any unintended consequences might be on you.
Right now the pinnacle of story-driven game achievement seems to be: a decent prewritten linear plot with depth that is supported well by the gameplay mechanics, with maybe a few branches here and there. That's still very cool, and if done right with the proper characterizations you hardly even notice (or care) that you're being railroaded. You, as the protagonist, feel that the choices made by the writer are the correct ones for the character.
However, I'm hoping that at some point in the near future there will be the possibility of a game that creates a story arc with decent depth through extrapolating and manipulating the actions taken by the player in the game. Something that wraps around gameplay actions to create quite different story arcs for different gameplay choices. This will have its limits, mostly because it does require the player to actually attempt to make meaningful choices - purely random play is unlikely to emerge into a good arc.
"Whether it was sensible or not doesn't matter - it is the Law"
I think you show an obvious lack of critical thinking and so you should not have the right to vote.
No, you are reading something into my post that isn't there. I am simply pointing out that there is a cause and effect relationship with breaking the law and/or a contract. The parameters of the effect in this particular case were clearly set out in the agreement between Microsoft and the EU, and Microsoft agreed to them before breaking the agreement.
Finally, why does having the **right to vote** matter to you, if you don't actually accept the rule of law?
It ruined no one by not having that list present
It was illegal and a violation of the agreement that Microsoft themselves signed with the EU after Microsoft lost the browser bundling court case. That's all that matters. The EU said "you can't do that" to Microsoft, Microsoft fought it hard in court, Microsoft lost, Microsoft agreed to a specific remedy, Microsoft then violated that remedy, Microsoft gets fined to send a message to any company that might think it's not that big a deal to violate a legal agreement with the EU. Whether it was sensible or not doesn't matter - it is the Law, and as a company you cannot flip off the Law and expect to get away with it.
With documentation you usually just get an API reference, and maybe a simple example. With community sites like Stack Overflow you get vetted examples and best practices from real world users. It's almost always more helpful than just a static reference.
Or put another way: knowing all the components (documentation) doesn't necessarily mean you grok the system (stackoverflow).
When you follow the API and your program doesn't work,
That's a pretty good indication that the docs are bad
Or that the API complexity is beyond what's capturable in reasonable "what this call does" style documentation. This happens very quickly in modern OO designs that follow the SOLID principles, because absolutely nothing is completely "local". What I mean by that is that in order to fully understand a single API call or class, you also need to understand all its parameter types, its injected dependencies, its superclasses, in some cases its derived classes, etc. etc.
Documentation of the type "what does this class do" or "what does this API call do" almost never captures the full complexity / possibilities of the system. What *you* want to do with that class may have specific effects in all those dependencies that cannot (and should not) reasonably be documented in the API call, but in the dependencies, but if you don't know where to look, you'll never find it.