|
このページはEtoJ逐語翻訳フィルタによって翻訳生成されました。 |
Bookmark this on Delicious
Recommend to StumbleUpon
I have 公式文書，認めるs for 翻訳家s, if you would 追加する a translation. Please 公式文書，認める: This "translations" 封鎖する will be moved to a place その上の 負かす／撃墜する the page if it becomes 広範囲にわたる.
This page, as it stood in May 2017, is 利用できる, translated by humans, into Albanian by Strong 自動車.
This page is "browser friendly". Make your browser window as wide as you want it. The text will flow nicely for you. It is easier to read in a 狭くする window. With most browsers, 圧力（をかける）ing 加える, minus or 無 while the 支配（する）／統制する 重要な (ctrl) is held 負かす／撃墜する will change the texts size. (大きくする, 減ずる, 回復する to default, それぞれ.) (This is more fully explained, and there's another tip, at my 力／強力にする Browsing page.)
Before I start on something else that I start on before I answer "what is design", a word of 警告. This page rambles. It doesn't "tell you what button to 圧力（をかける）". It doesn't have ビデオ clips or pretty pictures. But if you are willing to settle 負かす／撃墜する, and dig in, I think there are things here which you could find 価値のある.
Some people are content to bump along, with the world we are used to. Others have an itch to change things.
Too much lip service is paid in schools the xxx idea that anyone can do anything, just as long as the want it enough, try hard enough. While I applaud the hopes of teachers to be encouraging, they いつかs lean so 堅固に to the 政治上 訂正する, and the "安全な" that children fail to understand that while we all have the same basic 権利s to aspire, and that we should not be 否定するd 確かな things based on irrelevant 基準, we are also all different. The child with a club foot will never 勝利，勝つ a footrace against a 同時代の born with 井戸／弁護士席 連係させた, 井戸／弁護士席 機能（する）／行事ing 四肢s.
Not only are we born with different 団体／死体s, but we are born with different minds. If minds were food, you might say that one mind is "steak", another "ice cream". Neither is "better". Both are 価値のある. But it would be absurd to serve ice cream as a main course, or steak for 砂漠. And it must also be 認める that some minds faster than others. Some minds see things more easily that others do.
But it is an over-simplification to say mind "A" is more 有能な than another. You have to 明示する a field. I'm a pretty good computer programmer, but I can't read music.
That brings me to one last thing before we get 負かす／撃墜する to what is design,
I said I can program, but can't read music. What I need to 追加する to that is that I've tried やめる hard at both. I've also had good teaching in both fields. If you want something 不正に enough, perspiration can somewhat 補償する for inspiration. I knew a boy who was a first class cricket player, にもかかわらず 存在 blind in one 注目する，もくろむ. Follow your heart... but try to know something about which roads might be 平易な for you, which might be a struggle.
So... 支援する to "steak" and "ice cream". Some people were born artists. If they 追求する that road, they can learn a lot about the （手先の）技術 of their medium, but to become 広大な／多数の／重要な, they will also have to "use the 軍隊", and draw on their capacity to feel what is going to create beauty.
Some people have talent in relating to others. Maybe they will become 助言者／カウンセラーs, carers, etc, etc.
Some have mechanical aptitude. They are good with their 手渡すs.
And then some are good at thinking up machines... in 幅の広い 条件... which 港／避難所't 存在するd before, or thinking of variations on 存在するing machines which will give mankind a new useful 装置.
These are the designers.
They make things by a 科学の approach, rather that the more intuitive approach of the artist. That isn't to say that there is no design in art, or art in design... it is a question of 強調.
So... what is design? It is a disciplined 過程 of looking at what we 要求する of what we are designing, and looking at the 所有物／資産／財産s and 能力s of the 構成要素s and 構成要素s 利用できる to us, as we try to 橋（渡しをする） the gap between where we are and where we want to be.
Whether you are designing a mechanical 装置, an electronic 回路・連盟, a computer program, or something else: Keep It Simple
If the 職業 can be done with 5 parts, don't use the design that uses 10 parts. Of course, no one sits at a desk with a 5 part design in one 手渡す, and a 10 part design in the other, and says, ummm, which shall I use. But if you find yourself sitting there with a 10 part design, ask yourself... could I do this with より小数の parts?
The simpler something is, the より小数の things there are to go wrong.
Of course, it must be fit for 目的. If we were in the same room, I could communicate with you with nothing more than my 発言する／表明する. To communicate with thousands who care to 見本 my thoughts, across thousands of miles, takes a more コンビナート／複合体 design. But you may have noticed that even though I am using computers and the internet, the page you are reading has very few "whiz bang" fancy headings, no animated graphics, etc, etc. If I 手配中の，お尋ね者 to show you how a four-一打／打撃 内部の 燃焼 engine worked, I'd use an animated graphic. But that's more than these ideas need.
When you 達成する a simple design to a コンビナート／複合体 design challenge, if you have an engineer's 地雷, you will know you've done it. To an engineer, their is a beauty in something simple.
In something like a car, the modules are obvious. Other design challenges also 産する／生じる to the old 概念 of "divide and 征服する／打ち勝つ". At the 最高の，を越す level of a car, you might 分裂（する） things up into...
Taking just one of those, the engine, we can divide the problem again, this is the second level of the 階層制度... We'll pretend our car is to have a ガソリン engine. Design of the engine could be broken up into 冷静な／正味のing, lubrication, 製図／抽選 in the 燃料/空気／公表する mixture, 供給するing a 誘発する... etc
Now consider "供給するing a 誘発する". Where does the electricity come from? How is it 配達するd to the 権利 place? At 権利 time?
You get the idea? Modules. 階層制度s. And remember: The same 原則s can be 適用するd to electronic 回路・連盟s, computer programs, and more.
Later discussions will shed more light on the answer to that, I hope, but let me here （人命などを）奪う，主張する that with a good modular design, you can work on parts of your design in 孤立／分離. And where things aren't やめる 権利, you can 改善する their design more easily when you can work on modules 分かれて.
I hope that while I was talking about the way you might 分裂（する） up the problem of designing an engine, you were thinking, "Wait a minute... it would be better to 分裂（する） things like..."
A big part of the "art" of design is choosing how you've broken the problem up. What is a "good" 計画／陰謀? One that gives you modules you can work with in 孤立／分離, one amenable to something we are about to talk about: "最高の，を越す 負かす／撃墜する design/ 底（に届く） up 開発"
How do you go about breaking the problem up so that you will have "good" modules... Ah... a question which is not so easily answered. The more you 努力する／競う to do it, the better you will get at it... but you have to remember to try!
This 原則 encourages you to start the design 過程 in 幅の広い 条件. "幅の広い" need not be another way of 説 "wooly". But start with a （疑いを）晴らす 声明 of the 事業／計画（する）'s goal. Continuing the car example, at the very 最高の，を越す of the design 過程 you might say "We're creating something to move people at 速度(を上げる）s of up to 70 miles per hour, in reasonable 慰安, 絶縁するd from the 環境."
Part of the "trick" of 最高の，を越す 負かす／撃墜する 開発 is to keep one 注目する，もくろむ on where you are going at the same time as you are "using the other 注目する，もくろむ" to take care of some 明確な／細部s.
持続するing the 権利 level of specificity as you work from the upper, more general, levels 負かす／撃墜する to the 底（に届く）, 高度に 明確な／細部 詳細（に述べる）s of each part of a part of a part.... of the design. It is an art, and takes practice. And at the same time, the art of breaking the problem into a useful structure of modules is 存在 演習d.
When you begin to get it 権利, again, you should feel that things are 権利. You will feel that you are "on 最高の，を越す" of whatever piece of the puzzle you are working on at the moment. Again, "beauty" is not too strong a word. You should see a beauty in the structure. You should be able to read what you have written, and be comfortable that you understand what is going on, and feel that you know "your place" in the 全体にわたる 計画／陰謀. If you don't feel this, then continue to work on your design until you have it pretty 井戸／弁護士席 "finished", at least ーに関して／ーの点でs of 明示するing what all the parts will be, how they fit together, what is taken care of by each module, sub module, sub- sub module, etc.
Far better to 乗る，着手する on the next 段階... the "底（に届く） up 開発"... from a 計画／陰謀 which "should" work. Yes, of course you will find "little things" (or maybe not so little things!) that, on reflection, need 改正. But the harder you work in the first 段階, the より小数の of them there will be. And 直す／買収する，八百長をするing them during the planning is a lot easier than making changes when you've started building modules. For one thing, it 避けるs the need of going 支援する and 改訂するing bits which should have been "done"!
If you are 警報, you will from time to time find you've painted yourself into a corner. Annoying, and something you will get better at 避けるing, as you get better at the whole 過程... but it is good if the 過程 lets you see the problem 早期に, which it may. It is hard to 避ける doing it, but it is worse if you do it, but don't discover it until late in the building 過程!
Suppose you were having a house built. That's a design problem. You and your architect would start with a 幅の広い, "最高の，を越す level" idea of what you 手配中の，お尋ね者. Together you would develop the design, 徐々に 演説（する）／住所ing greater and greater levels of 詳細（に述べる）. If you've ever been 伴う／関わるd in such things, you will know that it is very much better to have the 計画（する） finished before you start construction. Even if you have an honest 建設業者, making changes as you go along is a 高くつく／犠牲の大きい 事件／事情／状勢, because "直す／買収する，八百長をするing" things that have to be changed in the 計画（する）, after building has 開始するd is much harder than it would have been to do "it" 権利, once.
So! You have a brilliant 計画（する）. All of the things that could go wrong have been carefully considered and 供給するd for. Everything the 事業／計画（する） should 達成する has been built in. (権利... and my 現在の 在庫／株 大臣の地位 is perfectly balanced... but we can dream!)
Are you sure??
If so, then it is time to go on to the 開発 段階. But get the "最高の，を越す 負かす／撃墜する design" work 適切に finished, first, if you want to save yourself grief.
Three things to look out for:
Impatience: Are you itching to "get going"? I hope so! But don't give in to a want for instant gratification if the planning of the work is not truly 完全にする!
疑問s: If you are honest with yourself, is there some little corner of the 計画（する）s about which you have 疑問s? To put that a different way, are you 全く 確信して that you 削減（する） no corners along the way? If you have got any 疑問s, you really せねばならない look under those 激しく揺するs now.
Worries: いつかs at this 行う／開催する／段階 there's an element of a design that you are, if you search your soul, 内密に a little worried about. Suppose you are designing an electronic 回路・連盟, and you need a 確かな 構成要素 to 許容する a 500mA 現在の, and you aren't やめる sure 正確に／まさに how high the 現在の there is going to be. Find a way to get the answer now. Don't start the main 底（に届く） up 開発 until you know you aren't going to have a problem with that 500mA 制限. Or find a way to go around the 制限. Often you can built little 実験（する） 回路・連盟s (or small computer programs, etc... whatever you are designing) to （疑いを）晴らす up a worry which you have been clever enough to notice and を取り引きする 早期に, thus 避けるing having to do 複雑にするd backtracking during the 開発 段階.
Once you have the design 権利, you start on the 開発. Let's say we're building a new design of car.
Remember we talked of "modules"? The engine is a module in a car, and within that we have modules like the 誘発する plugs, the carburetor, a piston/ connecting 棒/ cylinder module.
In 底（に届く） up 開発, we try to work first with sub-sub-sub 議会s. For instance, a 誘発する plug. We built that and 実験（する） it. (We can't fully 実験（する） it, of course, but we can make some 実験（する）s. Will it make a 誘発する, when a voltage is 適用するd? Will it screw into a threaded 穴を開ける of the size we ーするつもりである to make in the 最高の，を越す of the cylinder? Does it 生き残る 存在 as hot as it will be when the engine is running? The more 実験（する）s you can think of and run, the better.
Let me digress for a moment to the realm of creating computer programs,
In that realm, modules are easily encapsulated in subroutines. (In some languages, these are "機能（する）／行事s" and "手続きs".) The more 技術d you become at using these, the さらに先に you will go as a programmer. You need to see where to use a subroutine. You need to master "chopping up" your code into subroutines. You need to master your language's 施設s for passing data to and from subroutines. And you need to master "nesting" subroutines, in other words building subroutines out of subroutines which themselves are built of subroutines, etc. (Like a hall of mirrors.)
Going 支援する to 底（に届く） up 開発....
We were creating an new sort of car. We'd finished the "最高の，を越す 負かす／撃墜する design".
The 原則 of "底（に届く） up 開発...and 実験（する）ing..." 要求するs that we look for sub- sub... 議会s, like the 誘発する plug. We build that, and 実験（する） it. Then we go on and build other sub- sub- 議会s... wheel, door, carburetor, 無線で通信する... etc.
Why all the 強調 on 実験（する）ing?
If you 実験（する） as you go, you won't be left at "the end" (of building the first 原型) with a daunting 実験（する）ing (and tweaking!) 段階 ahead of you. And....
More importantly, by 実験（する）ing as you go along, you may discover things which 要求する changes which will be easier to make now than it will be to make them later.
In a わずかに 緊張するd example, let's pretend that we planned for a 無線で通信する module which is 12cm 深い. But when we build the module, and 実験（する） it, we find that we just can't do it... the module needs to be 15cm 深い. What if the way we designed the 無線で通信する's "home" in the car there isn't room for the deeper 無線で通信する module? We are going to be rewarded for our 実験（する）ing! We won't build the unsuitable dashboard now. We will redesign it first, to 融通する the extra 3cm that we need.
So... we've built and 実験（する）d some sub- modules. Next we 組み立てる／集結する those into sub-modules, e.g. the engine, and we 実験（する） again.
Another advantage of the "最高の，を越す 負かす／撃墜する design/ 底（に届く） up 開発" method is that the 職業 usually gets easier as you go along. The 早期に 行う／開催する／段階s are hard, and somewhat boring, work. But as you get closer to the end... if you've done the first parts 権利... everything "comes together" very nicely.
枠組みs: As you proceed, you may need to build 枠組みs. In our "make a car" example, when we've got to the 行う／開催する／段階 of 組み立てる／集結するing the engine from its sub-modules, some sort of 枠組み to 開始する it in will be necessary before we can do 実験（する）ing. いつかs you will have other parts of the 底（に届く） up 開発 十分に far along that you can "開始する the engine" in the でっちあげる，人を罪に陥れる it will 結局 go in. Other times, you will make a 一時的な でっちあげる，人を罪に陥れる, just for the 実験（する）ing 段階.
While such things are, I hope, 平易な enough to visualize in the 事例／患者 of building a car, maybe they aren't as obvious to readers who will be building ソフトウェア.
In any 事例／患者, in either 事例／患者, the building of such 枠組みs is part of the art of the design 過程. There are no simple answers. But you 徐々に become more 技術d, as long as you keep trying. Keep in mind the basic 必要物／必要条件: You want to build your 製品 "from the ground up". You want to 組み立てる／集結する sub- sub- sub...議会s first. And 実験（する） them. Then 連合させる them to build the next level. 実験（する） that. Etc. 底（に届く） up.
As you 伸び（る） 技術 with the "最高の，を越す 負かす／撃墜する design/ 底（に届く） up 開発" 過程, you should find more and more that the way you broke the 事業／計画（する） up during the "最高の，を越す 負かす／撃墜する" 段階 helps you proceed easily during the "底（に届く） up" 段階.
Returning to "枠組みs": In the 事例／患者 of building ソフトウェア, where we use subroutines to encapsulate modules, we will often build little scratch programs to "演習" the subroutines.
Suppose our finished program is supposed to encrypt とじ込み／提出するs, using a 使用者-供給（する）d 重要な.
There will probably be "支配するs" about the 重要な... must not be too short, must have at least one digit in it, etc.
Again, a わずかに 緊張するd example, but with some sense in it 非，不，無-the-いっそう少なく: You will almost certainly have a module called "GetKeyFromUser". During the 底（に届く） up 開発, you might produce a small program, 含む／封じ込めるing what you hope will be the final code of "GetKeyFromUser". The small program would 供給する a 枠組み for calling the GetKeyFromUser module, and then just popping up a "passes 支配する 実験（する）s" or "fails 支配する 実験（する）s" message.
Continuing with that a little bit: The subroutine would return two values: A boolean (true/誤った) which I'll pass to "boPassesRulesTest", and a string, to 持つ／拘留する the 重要な, which I'll put in "sKey". (公式文書，認める: The "実験（する）s" here aren't the 実験（する）ing we are doing during our 底（に届く） up 開発. They are the 実験（する）s the ソフトウェア should 適用する to the 重要な the 使用者 has 供給（する）d, to see if it 会合，会うs the program's 必要物／必要条件s... long enough, digit 含むd, etc.)
The 枠組み for 実験（する）ing GetKeyFromUser... and, up to a point, the call's 状況 in the final program... will look something like the に引き続いて. 現実に getting something from the 使用者, in my example, would be built into GetKeyFromUser. The last line below would be as shown for the 実験（する）ing 枠組み, so the design tester can try 重要な after 重要な after 重要な, seeing how GetKeyFromUser 答える／応じるs... and yet still the tester has an elegant way to 出口 the 実験（する）ing 過程... by entering 'q' as "the 重要な". In the final program, we'd probably take the "else showmessage('Good 重要な') bit out, and we would certainly change the "until" part... which could be as simple as "until boPassesRulesTest==true". (A 欠陥 in that perhaps over-simple "answer" is that it gives 失望させるd 使用者s no way out when they can't find a 重要な that is 許容できる to the program's 必要物／必要条件s.)
repeat
GetKeyFromUser(boPassesRulesTest,sKey)
if boPassesRulesTest==誤った then showmessage('Bad 重要な')
else showmessage('Good 重要な')
until sKey=='q'
So... I hope that makes sense? (Have a quick second 試みる／企てる, if not, as I'm about to take it a bit その上の.)
I am still talking about 枠組みs, and the "底（に届く） up" deve3lopment 過程.
While you could develop the program that way, if you were a bit more artful, in this 事例／患者, you might 井戸／弁護士席 proceed as follows.
First build the bits of the program around where you will 結局 挿入する the call of GetKeyFromUser. And, while developing those other parts, just put, in place of the GetKeyFromUser, sKey='tempkey123'
That would give you a "working" value for sKey, for 実験（する）ing all the bits of the program which need the 重要な... and 許す you to, later, "plug in" the 決まりきった仕事 which will bring the program closer to the final wants by 追加するing the part which gets a 重要な from the 使用者, rather than just using a "直す／買収する，八百長をするd" 重要な.
Be a bit careful, though. If you only 実験（する） the other parts with one 重要な, e.g. "tempkey123", there may be things in the part you think you are "実験（する）ing" which work with that, but fail with other valid 重要なs.
Learning "what 事柄s", so you can do 効果的な 実験（する）ing, is another of those areas which 需要・要求する that you be artist 同様に as engineer.
That's it for "底（に届く） Up 開発 and 実験（する）ing", and thus we also finish "最高の，を越す 負かす／撃墜する Design / 底（に届く） Up..."
(By the way... this essay "built", in some ways, using the 原則s of "最高の，を越す 負かす／撃墜する design/ 底（に届く） up 開発"! Think how that might be? Some of the techniques your English teacher may have tried to 派手に宣伝する into you were just a variation on that.)
Moving on, to finish up by considering two other 面s of "good design". Making things maintainable and making them fail 安全な.
How many times have you had to throw something out because one small element of it has failed, and that "can't" be mended? I once had to discard an さもなければ good laptop because the 冷静な／正味のing fan had dies, and couldn't be 取って代わるd. Needless to say, I 避ける that brand now.
As you develop your design, try to 心配する what parts may fail, and make it 平易な to service or 取って代わる them. There is a 推論する／理由 car wheels are connected to the axles with bolts, not rivets!
Not only should it be possible to 取って代わる 構成要素s, try to put the modules of your design together so that you can disconnect them for 実験（する）ing. The door to my home is locked with a system which 解放（する）s an electromechanical strike plate when the 権利 RFID tag is brought up to the sensor. The syste3m recently stopped working. Happily, the strike plate module is connected by a plug that mates with a socket. It was 平易な to unplug the cable and put a voltmeter on the socket, to see if it was the strike plate, or the 回路・連盟s 運動ing the strike plate which had failed.
Yes... the modules I was just speaking of in 関係 with maintainability in a design are the same modules that we designed from the 最高の，を越す 負かす／撃墜する, and developed from the 底（に届く） up.
Remember that Mr. Murphy, him of the eponymous 法律, is out there waiting for us.
In grade school, I was taught that the Westinghouse ブレーキ was a 抱擁する break-through in the 開発 of the 鉄道s. Before Mr. Westinghouse's eureka moment, as a "make it fail 安全な" designer, ブレーキs were used in many things... but you had to 活動させる／戦時編成する the ブレーキ... and if the 機械装置 was in some way 欠陥のある, 井戸／弁護士席, that was a pity. Too bad you didn't know there was something wrong before you needed the ブレーキs to come on...
Westinghouse's ブレーキ takes a different tack. It's almost a bad 指名する. The might better be called "wheel rotation allowers". When something is fitted with Westinghouse ブレーキs, the wheels "ordinarily" won't turn. The ブレーキ pads are 圧力（をかける）d against the wheels by large, powerful, simple springs. To make the train 動きやすい, first, the pads must be pulled away from the wheels by 比較して コンビナート／複合体 pneumatic actuators. You don't "適用する" the ブレーキs... they 適用する themselves, very 簡単に, in a way ありそうもない to "go wrong". But... if you want to move, you have to "UN-適用する" the ブレーキs. If everything is working 正確に, you can move. If something is wrong... if a system has failed... you can't move, and if you are moving, before long you stop.
Mr. Westinghouse looked at the system he was designing a module for. He asked himself what 明言する／公表する was least 安全な. And he designed his ブレーキs so that, in general, when the things that could go wrong did go wrong, the system moved to a 安全な 明言する／公表する, as …に反対するd to the いっそう少なく 安全な 明言する／公表する.
平易な when someone shows you!
What about the thing you are designing? Can you make it "fail 安全な"? First you have to identify what the "安全な" 明言する／公表する would be. Then you have to look at the design you have, 正確に identify the ways it could fail. For each of them, is the result a 安全な 明言する／公表する?
I've seen several designs for computer controlled electric doors, e.g. the 前線 door of someone's home.
If the electricity fails, what happens? Does the door swing 解放する／自由な in the 微風? Probably いっそう少なく than wonderful, ーに関して／ーの点でs of keeping 夜盗，押し込み強盗s out. But what happens if when the electricity fails the door locks up? Not funny, if you are at home, in bed, and the 力／強力にする has failed because you have a 解雇する／砲火／射撃 in your home. Hmm. Designing for "fail 安全な" can be やめる important.
What about a system to water houseplants? Suppose you hook a small "靴下／だます" up to the general water 供給（する）, and have an electrically operate 弁 which is opened when the 工場／植物s get too 乾燥した，日照りの? Is this really a good idea? What if the system fails at a moment when the 弁 is open, and you are away from home for the 週末. You'd be amazed how much 損失 half an インチ of water across all of the ground 床に打ち倒す rooms in your home will 原因（となる）. Look around. Who would have thought you had so many things on the 床に打ち倒す!
So... What could fail? What 明言する／公表する would that leave things in?
許す a small digression, meant 単に to amuse? In his thriller "移転 of 力／強力にする", Fince Flynn imagines a テロリスト with a flair for fail 安全な design. The テロリスト has 工場／植物d 爆弾s throughout the White House. He doesn't want the Good Guys to 勝利，勝つ. So his 爆弾s will go off if they don't receive a "stay 静かな" code every five minutes. Bad Man. Good Designer.
Thank you for taking the time to read this... I hope it has helped you become a better engineer, whether you are building physical things like electronic 回路・連盟s, or more abstract things like computer programs or databases. The 原則s 始める，決める out above of good design 適用する across many disciplines.
|
|
If you visit 1&1's 場所／位置 from here, it helps me. They host my website, and I wouldn't put this link up for them if I wasn't happy with their service. They 申し込む／申し出 things for the beginner and the 会社／団体.
Page 実験（する）d for 同意／服従 with INDUSTRY (not MS-only) 基準s, using the 解放する／自由な, 公然と accessible validator at validator.w3.org
....... P a g e . . . E n d s .....