Thursday, November 28, 2019
Here Are Some Tips and Tricks for Writing a Short Bio
Here Are Some Tips and Tricks for Writing a Short BioHere Are Some Tips and Tricks for Writing a Short BioWhat do editors and agents mean when they ask for a short bio? For writers just starting out, the idea of writing abio, short or otherwise, to go along with their submissions to a literary journalcan be daunting. What exactly are editors looking for? What if you havent published anything yet? Is it important to include your education, your job, your favorite ice cream flavor? Should you be cheeky, friendly, or boringly professional? These general rules of thumb might help. If You Have No Published Works or Awards If the editor or agent has specifically said that theyre open to new work, theyre not going to mind if you dont have an MFA or a slew of impressive awards. You can be brief and honest. They want a short paragraph, literally a few lines, to put your submission in context. They often use this paragraph for the Contributors Notes at the back of the journal if they accep t your story. They dont have to worry about soliciting it later on if they get your bio up front. If You Have Been Published If youvebeen published inother literary journals or have an MFA or both, toot your horn. You should list these things first. A clean and acceptable short bio with credentials might go something like this John Doe received an MFA in fiction from Writing University in 2006. He stories have previously been published inWriting MagazineandBest Fiction. He lives in Ontario, Canada. Friendly or Boring fruchtwein bios are on the dry side, but take a look at those of other writers in the journal to get a feel for what the editor or agent is looking for. You can be a little creative if it looks like theyre open to something more colorful. Reading real bios from published writerscan give you a framework to get you started. Shorter Is Sweeter John Does bio above says just enough. It doesnt distract from the story hes submitted. You dont want your bio to be a t urn-off for an editor. You dont want her to begin wishing she could stop reading before she gets to the end of it. Dos and Donts Morgan Beatty is the editor of People Holding..., the website that sends authors found photographs and asks them to write about them in 550 words or less. We asked him what advice he has for writers sending short bios. Heres his list of dos and donts. Do rememberthat if you despair over using the third person, youre a writer.Dont forget that self-deprecation lends an aftertaste to your work.Do remember that your pets dont mind being left out.Dont forget to never overstay your welcome. The Three-Sentence Rule Consider using the three-sentence rule. Even if you have more published works than Shakespeare, dont try to list them all. Pick the very best, and let the spotlight shine on them. If youve won more awards than Katherine Hepburn, stick to the most prestigious. If you want to mention where you live, thats fine, but theres no need to describe the view from your window. You might want to write several bios. Put them aside and forget about them for a day or two, then go back and look at them cold. You might be surprised to realize that you see them in a whole new light.
Saturday, November 23, 2019
Making Boilers More Efficient
Making Boilers More Efficient Making Boilers More Efficient In the boiler world, fruchtwein upgrades over the years have been small innovative steps rather than anything highly revolutionary as the industry continues to improve safety and efficiency and to control emissions.Today, efficiency is the name of the game, and recently, companies have been focusing on changing the way the burner operates on the boiler as an important way to gain greater efficiency. The result for one company has been what Alan Wedal, product manager for commercial boilers at Cleaver-Brooks Inc., Milwaukee, WI, calls the biggest major development in decades and perhaps even since World War II.It all became possible due to advances in computer modeling within the past decade that allowed engineers to work faster, generate information from the modeling program, and test prior to building and testing new boilers.Now, we build and test to verify. Its not as much trial and error as before, says Florian Wisinski, Wedals counterpart for industrial boilers at Cleaver-Brooks.Oxygen LevelThe goal was to get to a constant oxygen level across the entire firing range of the boiler, which is accomplished through controls and sensors, says Wisinski.A traditional burner typically operates at lower efficiency ratings because additional oxygen is required for the burner to fire properly, and too much excess air, as the added oxygen is termed, can lower boiler efficiency.According to Cleaver-Brooks, research has shown that 15% excess air is the optimal amount to introduce into the boiler combustion process. While some boilers have been able to achieve 15% excess air at the top end of a boilers firing range, the challenge comes at the lower end when the boiler is operating well below its maximum capacity. Thats because most boilers tend to demand greater excess air in the lower range.Furthermore, Wedal explains, most boilers typically operate in the lower range the vast majority of the time. So if you can improve the efficiency at the lower firing range and youre operating there quite a bit of the time, the overall effect can be a very good efficiency gain for the end user, he adds.New DesignIn what became a 24-month process from initial concept, konzept, and validation through testing, engineers at Cleaver-Brooks started by designing a new boiler incorporating the idea of changing the burner, says Wisinski. One critical factor was a re-design of the tubes within the boiler to increase heat transfer in the tubes. Engineers added helical ribs to the inside of the tubes, creating more turbulence of the hot flue gasses and thus more heat transfer.Tubes with added helical ribs increase the heat transfer coefficient in applications using a gas or fluid with low thermal conductivity. Image source Mstube.comBut it was only with the aid of CAD embedded with CFD that engineers were able to perform extremely complex calculations on various elements of a boiler system, including analyzing prob lems that involve fluid flows. Calculations allowed simulation of the interaction of liquids and gases with surfaces, which in turn enabled engineers to improve the tube profile and increase heat transfer by 85% compared to a traditional bare tube.Now that the equipment is available commercially, more than half of the boilers Wisinski is providing quotes for to prospects are using this new design, which provides between 1 percent and 5 percent greater efficiency in the lower ranges and is comparable in cost to older models.Its changing the marketplace as people learn about it and understand it, Wedal says. Were seeing it replacing a lot of our older models that we had been using, driven by the efficiency gains.Over time, Wisinski expects this will totally replace older technology although boilers can have a long life, some as long as 50 years. The new boilers have many applications for heating buildings and for all sorts of industrial processing from food, paper and plastic manufact urers to pharmaceutical and computer chip manufacturing facilities to providing process steam at healthcare facilities and other institutions.While efficiency was the main focus, there are additional benefits, including a reduction in emissions, savings related to using less fuel and an optimized design so that the new model typically has a much smaller footprint than older boilers for a comparable size. There are gains on many different fronts, says Wedal.Nancy Giges is an independent writer.So if you can improve the efficiency at the lower firing range and youre operating there quite a bit of the time, the overall effect can be a very good Florian Wisinski, product manager, Cleaver-Brooks.
Thursday, November 21, 2019
6 Basic SDLC Methodologies
6 Basic SDLC Methodologies6 Basic SDLC MethodologiesThe Software Development Life Cycle (SDLC) is the software development worlds spellcheck - it can flag errors in software creation before theyre discovered (at a much higher cost) in successive stages. But its much more than that, of course SDLC can also lay out a plan for getting everything right the first time.The SDLC process involves several distinct stages, including planning, analysis, design, building, testing, deployment and maintenance. Whats the best SDLC methodology? Here are six methodologies, or models, to consider.Software development lifecycle methodologiesAgileLeanWaterfallIterativeSpiralDevOpsEach of these approaches varies in some ways from the others, but all have a common purpose to help gruppes deliver high-quality software as quickly and cost-effectively as possible.Reviewing a brief description of the six most common SDLC methodologies may help you decide which is best for your team1. AgileThe Agile model has been around for about a decade. But lately, it has become a major driving force behind software development in many organizations. Some businesses value the Agile methodology so much that they are now applying it to other types of projects, including non-tech initiatives.In the Agile model, fast failure is a good thing. The approach produces ongoing release cycles, each featuring small, incremental changes from the previous release. At each iteration, the product is tested. The Agile model helps teams identify and address small issues on projects before they evolve into more significant problems, and engage business stakeholders and get their feedback throughout the development process.As part of their embrace of this methodology, many teams are also applying an Agile framework known as Scrum to help structure more complex development projects. Scrum teams work in sprints, which usually last two to four weeks, to complete assigned tasks. Daily Scrum meetings help the whole team mon itor progredienz throughout the project. And the ScrumMaster is tasked with keeping the team focused on its goal. (For more on Scrum, see the Scrum Alliance website.)2. LeanThe Lean model for software development is inspired by lean manufacturing practices and principles. The seven Lean principles (in this order) are eliminate waste, amplify learning, decide as late possible, deliver as fast as possible, empower the team, build integrity in, and see the whole.The Lean process is about working only on what must be worked on at the time, so theres no room for multitasking. Project teams are also focused on finding opportunities to cut waste at every turn throughout the SDLC process, from dropping unnecessary meetings to reducing documentation.The Agile model is actually a Lean method for the SDLC, but with some notable differences. One is how each prioritizes customer satisfaction Agile makes it the top priority from the outset, creating a flexible process where project teams can resp ond quickly to stakeholder feedback throughout the SDLC. Lean, meanwhile, emphasizes the erledigung of waste as a way to create more overall value for customers - which, in turn, helps to enhance satisfaction.Ready to fill an open role? Use our candidate finder.3. WaterfallSome experts argue that the Waterfall model was never meant to be a process model for real projects (check out the discussion on this topic on StackExchange). Regardless, the Waterfall model is widely considered the oldest of the structured SDLC methodologies. Its also a very straightforward approach finish one phase, then move on to the next. No going back. Each stage relies on information from the previous stage and has its own project plan.The downside of Waterfall is its rigidity. Sure, its easy to understand and simple to manage. But early delays can throw off the entire project timeline. With little room for revisions once a stage is completed, problems cant be fixed until you get to the maintenance stage. This model doesnt work well if flexibility is needed or if the project is long term and ongoing.Even more rigid is the related Verification and Validation model - or V-shaped model. This linear development methodology sprang from the Waterfall approach. Its characterized by a corresponding testing phase for each development stage. Like Waterfall, each stage begins only after the previous one has ended. This SDLC model can be useful, provided your project has no unknown requirements.4. IterativeThe Iterative model is repetition incarnate. Instead of starting with fully known requirements, project teams implement a set of software requirements, then test, evaluate and pinpoint further requirements. A new version of the software is produced with each phase, or iteration. Rinse and repeat until the complete system is ready.Advantages of the Iterative model over other common SDLC methodologies is that it produces a working version of the project early in the process, and makes it less e xpensive to implement changes. One disadvantage Repetitive processes can consume resources quickly.One example of an Iterative model is the Rational Unified Process (RUP), developed by IBMs Rational Software division. As explained in this document from IBM, RUP is a process product designed to enhance team productivity that also captures many of the best practices in modern software development in a form that is suitable for a wide range of projects and organizations.RUP divides the development process into four phases inception, when the idea for a project is set elaboration, when the project is further defined, and resources are evaluated construction, when the project is developed and completed and transition, when the product is released. Each phase of the project involves business modeling, analysis and design, implementation, testing, and deployment.5. SpiralOne of the most flexible SDLC methodologies, the Spiral model takes a cue from the Iterative model and its repetition th e project passes through four phases (planning, risk analysis, engineering and evaluation) over and over in a spiral until completed, allowing for multiple rounds of refinement.The Spiral model is typically used for large projects. It enables development teams to build a highly customized product, and incorporate user feedback early on in the project. Another benefit of this SDLC model is risk management. Each iteration starts by looking ahead to potential risks, and figuring out how best to avoid or mitigate them.6. DevOpsThe DevOps methodology is the newcomer to the SDLC scene. As this article explains, it emerged from two trends the application of Agile and Lean practices to operations work, and the general shift in business toward seeing the value of collaboration between development and operations staff at all stages of the SDLC process.In a DevOps model, Developers and Operations teams work together closely - and sometimes as one team - to accelerate innovation and the deplo yment of higher-quality and more reliable software products and functionalities. Updates to products are small but frequent. Discipline, continuous feedback and process improvement, and automation of manual development processes are all hallmarks of the DevOps model.Amazon Web Services describes DevOps like this DevOps is the combination of cultural philosophies, practices, and tools that increases an organizations ability to deliver applications and services at high velocity evolving and improving products at a faster pace than organizations using traditional software development and infrastructure management processes. So, like many SDLC models, DevOps is not only an approach to planning and executing work, but also a philosophy that demands significant mindset and culture changes in an organization.Choosing the right SDLC model for your software development project will require careful thought. But keep in mind that a methodology for planning and guiding your project is only one ingredient for success. Even more important is assembling a solid team of skilled talent committed to moving the project forward through every unexpected challenge or setback.Interview technology candidates right awayIf youre hiring an IT pro, we can help make the process easier. You can see profiles of IT candidates in your area using our online database. Tell us who catches your eye, and we can arrange an interview or placement ASAP.Find web developer candidates in Austin, TexasFind software developer candidates in Boise, IdahoFind help desk analyst candidates in Charlotte, N.C.Find desktop support candidates in Sacramento, Calif.Find database administrator candidates in Tucson, Ariz. Tags
Subscribe to:
Posts (Atom)