# data[].attributes.body
Curso de como crear software desde el principio, mostrando el proceso creativo, modelado, investigacion, diagramacion de una app en vez de ya mostrar el producto final. Todos sabemos replicar lo de un video, pero no cualquiera podría hacerlo solo.

# data[].attributes.body
ISO/IEC 12207:2017 - Procesos de Ciclo de Vida del Software.
ISO/IEC 27001:2013 - Sistema de Gestión de Seguridad de la Información
ISO/IEC 29119 - Pruebas de Software
ISO/IEC 330xx - Normas relacionadas con la Ingeniería de Software
ISO/IEC 20000-1:2018 - Gestión de Servicios TI

# data[].attributes.body
Karate Framework
Appium
JMeter
Postman
K6
LoadRunner
SoapUI
Kobiton o similares
Serenity BDD
Unit Test
Automatizacion de Apis

# data[].attributes.body
Estaría genial que incluyan más programas para Testing, como Appium y Selenium, así también como Apache, testing manual etc. Gracias 💜

# data[].attributes.body
*Testing manual y automatizado
*Programación orientada a testing
*Principales herramientas en automation (Selenium, Cypress, etc.)

# data[].attributes.body
He estado aprendiendo flutterflow pero solo he encontrado apoyo en youtube y en la pagina oficial... me encantaria que platzi hiciera un curso completo de flutterflow y de hasta como lanzarlo y mostrarlo en la playstore.

# data[].attributes.body
Me gustaria un curso de Sonarqube para realizar calidad de codigo.

# data[].attributes.headline
quiero hacer un curso de como ser inteligente :(

# data[].attributes.subject
quiero hacer un curso de como ser inteligente :(

# data[].attributes.body
micro front end components usando Bit.cloud

# data[].attributes.attachment_caption
Solidworks abarca muchas especialidades de diseños en la industrial y tecnología.

# data[].attributes.headline
Escuela de Solidworks y Diseño Macánico.

# data[].attributes.subject
Escuela de Solidworks y Diseño Macánico.

# data[].attributes.body
El mundo de diseño en Solidworks tiene muchas especialidades, por ejemplo, superficies, chapa metálica, estructuras, etc.

# data[].attributes.headline
Escuela o Cursos de Realidad Aumentada, Realidad Virtual para Negocios

# data[].attributes.subject
Escuela o Cursos de Realidad Aumentada, Realidad Virtual para Negocios

# data[].attributes.body
Necesito un curso de producción musical

# data[].attributes.headline
Escuela de testing QA - ISTQB - testing de servicios, BD sql server, mobile, C#, automatización

# data[].attributes.subject
Escuela de testing QA - ISTQB - testing de servicios, BD sql server, mobile, C#, automatización

# data[].attributes.body
Herramientas para prevenir el lavado de dinero.

# data[].attributes.body
Curso de simulación de circuitos con Microcap un simulador gratuito para electrónicos, excelente complemento para un curso de electrónica.

# data[].attributes.body
Funcionamiento. Conectores, Empalmes. Sistemas WDM. Prueba de FO. Diseño de Red de FO. Instalación FO. Redes FTTH y FTTx. Estándares de cableado de FO. Presupuestos de F.O.

# data[].attributes.body
Curso de Programación de Drones con python y drone didactico Tello Talent Ryze DJI.
https://www.youtube.com/watch?v=QcXHmzmyoas&t=340s https://www.youtube.com/watch?v=LmEcyQnfpDA&pp=ugMICgJlcxABGAE%3D

# data[].attributes.body
Blockchain avanzado

# data[].attributes.body
para comunicar mejor

# data[].attributes.body
Uso de sonarqube y demás herramientas de análisis de cálidad de código y seguridad.

# data[].attributes.body
CURSO DE ROBOTICA

# data[].attributes.body
Pruebas de unidad
Pruebas de componentes
Pruebas de componentes
Pruebas de integración
Pruebas de componentes para UI
Pruebas de mutación
Integración continua y pruebas automatizadas

# data[].attributes.headline
Hacer los cursos más practico, incluir el desarrollo de casos reales, paso a paso.

# data[].attributes.subject
Hacer los cursos más practico, incluir el desarrollo de casos reales, paso a paso.

# data[].attributes.headline
Curso de gestión y mejora de procesos en TI.

# data[].attributes.subject
Curso de gestión y mejora de procesos en TI.

# data[].attributes.headline
Curso de Estadística descriptiva e inferencial con Julia.

# data[].attributes.subject
Curso de Estadística descriptiva e inferencial con Julia.

# data[].attributes.body
Más cursos para testers de software

# data[].attributes.headline
Escuela de Testing Manual y Automatizacion 

# data[].attributes.subject
Escuela de Testing Manual y Automatizacion 

# data[].attributes.body
- Casos Practicos y conceptos mas a profundidad de ciclo de vida
-Casos de pruebas
- Fases del testing Manual
- Analisis y diseño
- Especificacion
- Ejecucion
- Ciclo de defectos
- Preparacion de examen de la fundation level  ISQTB
-Syllabus
- Unit Testing
- Integrate Testing
- System Testing
- End-to-end
- Automation
- Jira
- Jira Xrays
- Selenium
- SOAP UI
- RestAssure in Java

# data[].attributes.headline
Escuela de Testing y Automatizacion de Pruebas

# data[].attributes.subject
Escuela de Testing y Automatizacion de Pruebas

# data[].attributes.body
- ISQTB Syllabus
- Unit Testing
- Integrate Testing
- System Testing
- End-to-end
- Automation
- Jira
- Jira Xrays
- Selenium
- SOAP UI
- RestAssure in Java

# data[].attributes.body
Construir un servicio de una API

# data[].attributes.body
UN CURSO DE HASKELL

# data[].attributes.body
Programación de microservicios en C#, Java u otro lenguaje.

# data[].attributes.body
Selenium , serenity bdd

# data[].attributes.body
curso de cypress y / o testcafe, ya que son temas que hoy en dia tienen mucho auge y es dificil encontrar buena documentacion y cursos en latinoamerica

# data[].attributes.body
Falta ampliar mucho la ruta de ciencias. Podría ser ampliada con un curso de astronomía, química, física (en concreto astrofísica o mecánica cuántica). No necesariamente tendrían que ser cursos avanzados, sino básicos o introductorios.

# data[].attributes.body
c# avanzado (manejo de eventos, WCF, Concurrencia)
Unit Testing con c#.
Más manejo en el IDE Visual Studio Community.

# data[].attributes.body
Principios SOLID con .net o java

# data[].attributes.body
Zbrush moldeado de personajes

# data[].attributes.body
Seria genial un curso de web assembly y un lenguaje propio para eso, por ejemplo rust.

# data[].attributes.headline
Cursos de herramientas de Seguridad DevSecOps

# data[].attributes.subject
Cursos de herramientas de Seguridad DevSecOps

# data[].attributes.body
Latino es un lenguaje de programación con sintaxis en Español.
Aquí los enlaces:
• https://www.lenguajelatino.org
• docs.lenguajelatino.org

# data[].attributes.attachment_link.readable_text
Latino es un lenguaje de programación de código abierto el cual tiene como objetivo mejorar el aprendizaje en la computación y la programación con una sintaxis limpia, intuitiva y fácil de trabajar.

Latino es un lenguaje que ha recibido el cariño y apoyo de usuarios hispanos al rededor del mundo y estos han contribuido en el crecimiento de este proyecto ayudando en la divulgación y aportando en el código fuente del lenguaje.

# data[].attributes.attachment_link.description
Latino es un lenguaje de programación de código abierto el cual tiene como objetivo mejorar el aprendizaje en la computación y la programación con una sintaxis limpia, intuitiva y fácil de trabajar.

# data[].attributes.body
Hace falta un curso en primero lugar actualizado de cypress y en el que se trabajen conceptos mas avanzados

# data[].attributes.body
Ayudaría mucho un curso de Introducción a MatLab u Octave para personas que, como yo, estudiamos Ing. Electrónica u otras ingenierias

# data[].attributes.body
Tecnologias como Asterisk y FreePbx o como crear un servidor propio

# data[].attributes.body
GAME ES UNA LIBRERIA DE pYTHON

# data[].attributes.body
- Desktop
- Web
- Cloud
- AI
- Mobile

# data[].attributes.attachment_link.readable_text
Richard

Today, we're announcing that the next release after .NET Core 3.0 will be .NET 5. This will be the next big release in the .NET family.

There will be just one .NET going forward, and you will be able to use it to target Windows, Linux, macOS, iOS, Android, tvOS, watchOS and WebAssembly and more.

We will introduce new .NET APIs, runtime capabilities and language features as part of .NET 5.

From the inception of the .NET Core project, we've added around fifty thousand .NET Framework APIs to the platform. .NET Core 3.0 closes much of the remaining capability gap with .NET Framework 4.8, enabling Windows Forms, WPF and Entity Framework 6. .NET 5 builds on this work, taking .NET Core and the best of Mono to create a single platform that you can use for all your modern .NET code.

We intend to release .NET 5 in November 2020, with the first preview available in the first half of 2020. It will be supported with future updates to Visual Studio 2019, Visual Studio for Mac and Visual Studio Code.

Check out .NET Core is the Future of .NET to understand how .NET 5 relates to .NET Framework.

.NET 5 = .NET Core vNext

.NET 5 is the next step forward with .NET Core. The project aims to improve .NET in a few key ways:

Produce a single .NET runtime and framework that can be used everywhere and that has uniform runtime behaviors and developer experiences.

Expand the capabilities of .NET by taking the best of .NET Core, .NET Framework, Xamarin and Mono.

Build that product out of a single code-base that developers (Microsoft and the community) can work on and expand together and that improves all scenarios.

This new project and direction are a game-changer for .NET. With .NET 5, your code and project files will look and feel the same no matter which type of app you're building. You'll have access to the same runtime, API and language capabilities with each app. This includes new performance improvements that get committed to corefx, practically daily.

Everything you love about .NET Core will continue to exist:

Open source and community-oriented on GitHub.

Cross-platform implementation.

Support for leveraging platform-specific capabilities, such as Windows Forms and WPF on Windows and the native bindings to each native platform from Xamarin.

High performance.

Side-by-side installation.

Small project files (SDK-style).

Capable command-line interface (CLI).

Visual Studio, Visual Studio for Mac, and Visual Studio Code integration.

Here's what will be new:

You will have more choice on runtime experiences (more on that below).

Java interoperability will be available on all platforms.

Objective-C and Swift interoperability will be supported on multiple operating systems.

CoreFX will be extended to support static compilation of .NET (ahead-of-time - AOT), smaller footprints and support for more operating systems.

We will ship .NET Core 3.0 this September, .NET 5 in November 2020, and then we intend to ship a major version of .NET once a year, every November:

We're skipping the version 4 because it would confuse users that are familiar with the .NET Framework, which has been using the 4.x series for a long time. Additionally, we wanted to clearly communicate that .NET 5 is the future for the .NET platform.

We are also taking the opportunity to simplify naming. We thought that if there is only one .NET going forward, we don't need a clarifying term like "Core". The shorter name is a simplification and also communicates that .NET 5 has uniform capabilities and behaviors. Feel free to continue to use the ".NET Core" name if you prefer it.

Runtime experiences

Mono is the original cross-platform implementation of .NET. It started out as an open-source alternative to .NET Framework and transitioned to targeting mobile devices as iOS and Android devices became popular. Mono is the runtime used as part of Xamarin.

CoreCLR is the runtime used as part of .NET Core. It has been primarily targeted at supporting cloud applications, including the largest services at Microsoft, and now is also being used for Windows desktop, IoT and machine learning applications.

Taken together, the .NET Core and Mono runtimes have a lot of similarities (they are both .NET runtimes after all) but also valuable unique capabilities. It makes sense to make it possible to pick the runtime experience you want. We're in the process of making CoreCLR and Mono drop-in replacements for one another. We will make it as simple as a build switch to choose between the different runtime options.

The following sections describe the primary pivots we are planning for .NET 5. They provide a clear view on how we plan to evolve the two runtimes individually, and also together.

High throughput and high productivity

From the very beginning, .NET has relied on a just-in-time compiler (JIT) to translate Intermediate Language (IL) code to optimized machine code. Since that time, we've built an industry-leading JIT-based managed runtime that is capable of very high throughput and also enabled developer experiences that make programming fast and easy.

JITs are well suited for long-running cloud and client scenarios. They are able to generate code that targets a specific machine configuration, including specific CPU instructions. A JIT can also re-generate methods at runtime, a technique used to JIT quickly while still having the option to produce a highly-tuned version of the code if this becomes a frequently used method.

Our efforts to make ASP.NET Core run faster on the TechEmpower benchmarks is a good example of the power of JIT and our investments in CoreCLR. Our efforts to harden .NET Core for containers also demonstrates the runtime's ability to dynamically adapt to constrained environments.

Developer tools are another good example where JIT shines, such as with the dotnet watch tool or edit and continue. Tools often require compiling and loading code multiple times in a single process without restarting and need to do it very quickly.

Developers using .NET Core or .NET Framework have primarily relied on JIT. As a result, this experience should seem familiar.

The default experience for most .NET 5 workloads will be using the JIT-based CoreCLR runtime. The two notable exceptions are iOS and client-side Blazor (web assembly) since both require ahead-of-time (AOT) native compilation.

Fast startup, low footprint, and lower memory usage

The Mono Project has spent much of its effort focused on mobile and gaming consoles. A key capability and outcome of that project is an AOT compiler for .NET, based on the industry-leading LLVM compiler project. The Mono AOT compiler enables .NET code to be built into a single native code executable that can run on a machine, much like C++ code. AOT-compiled apps can run efficiently in small places, and trades throughput for startup if needed.

The Blazor project is already using the Mono AOT. It will be one of the first projects to transition to .NET 5. We are using it as one of the scenarios to prove out this plan.

There are two types of AOT solutions:

solutions that require 100% AOT compilation.

solutions where most code is AOT-compiled but where a JIT or interpreter is available and used for code patterns that are not friendly to AOT (like generics).

The Mono AOT supports both cases. The first type of AOT is required by Apple for iOS and some game consoles, typically for security reasons. The second is the preferred choice since it offers the benefits of AOT without any of its drawbacks.

.NET Native is the AOT compiler we use for Windows UWP applications and is an example of the first type of AOT listed above. With that particular implementation, we limited the .NET APIs and capabilities that you can use. We learned from that experience that AOT solutions need to cover the full spectrum of .NET APIs and patterns.

AOT compilation will remain required for iOS, web assembly and some game consoles. We will make AOT compilation an option for applications that are more appliance-like, that require fast startup and/or low footprint.

Fundamentals and overlapping experiences

It is critical that we continue to move forward as an overall platform with startup, throughput, memory use, reliability, and diagnostics. At the same time, it also makes sense to focus our efforts. We'll invest more in throughput and reliability in CoreCLR while we invest more in startup and size reduction with the Mono AOT compiler. We think that these are good pairings. Throughput and reliability go together as do startup and size reduction.

While there are some characteristics where it makes sense to make different investments, there are others that do not.

Diagnostics capabilities need to be the same across .NET 5, for both functional and performance diagnostics. It is also important to support the same chips and operating systems (with the exception of iOS and web assembly).

We will continue to optimize .NET 5 for each workload and scenario, for whatever makes sense. There will be even greater emphasis on optimizations, particular where multiple workloads have overlapping needs.

All .NET 5 applications will use the CoreFX framework. We will ensure that CoreFX works well in the places it is not used today, which is primarily the Xamarin and client-side Blazor workloads. All .NET 5 applications will be buildable with the.NET CLI, ensuring that you have common command-line tooling across projects.

C# will move forward in lock-step with .NET 5. Developers writing .NET 5 apps will have access to the latest C# version and features.

The birth of the project

We met as a technical team in December 2018 in Boston to kick off this project. Design leaders from .NET teams (Mono/Xamarin and .NET Core) and also from Unity presented on various technical capabilities and architectural direction.

We are now moving forward on this project as a single team with one set of deliverables. Since December, we have made a lot of progress on a few projects:

Defined a minimal layer that defines the runtime <-> managed code layer, with the goal making >99% of CoreFX common code.

MonoVM can now use CoreFX and its class libraries.

Run all CoreFX tests on MonoVM using the CoreFX implementation.

Run ASP.NET Core 3.0 apps with MonoVM.

Run MonoDevelop and then Visual Studio for Mac on CoreCLR.

Moving to a single .NET implementation raises important questions. What will the target framework be? Will NuGet package compatibility rules be the same? Which workloads should be supported out-of-the-box by the .NET 5 SDK? How does writing code for a specific architecture work? Do we still need .NET Standard? We are working through these issues now and will soon be sharing design docs for you to read and give feedback on.

Closing

The .NET 5 project is an important and exciting new direction for .NET. You will see .NET become simpler but also have broader and more expansive capability and utility. All new development and feature capabilities will be part of .NET 5, including new C# versions.

We see a bright future ahead in which you can use the same .NET APIs and languages to target a broad range of application types, operating systems, and chip architectures. It will be easy to make changes to your build configuration to build your applications differently, in Visual Studio, Visual Studio for Mac, Visual Studio Code, Azure DevOps or at the command line.

See: .NET 5 on Hacker News

# data[].attributes.attachment_link.description
Today, we're announcing that the next release after .NET Core 3.0 will be .NET 5. This will be the next big release in the .NET family. There will be just one .NET going forward, and you will be able to use it to target Windows,

# data[].attributes.body
Todo lo relacionado a testing, desde pruebas manuales, automatizadas y de performance

# data[].attributes.headline
Creo que falta ampliar la oferta en ciencias:  Hace mucha falta cursos de química.  Igualmente hacen falta cursos de LaTeX y econometria básica.

# data[].attributes.subject
Creo que falta ampliar la oferta en ciencias:  Hace mucha falta cursos de química.  Igualmente hacen falta cursos de LaTeX y econometria básica.

# data[].attributes.body
Tienen componentes excelentes que ayudan en la programación y la experiencia de usuario.

# data[].attributes.body
Quiero un curso para certificarme en S

# data[].attributes.body
Estaría padre para las personas de otras areas académicas

# data[].attributes.body
Quiero un curso o carrera para poder ser arquitecto de software

# data[].attributes.body
Creo que ya han tardado mucho en hacer un curso de como Vender en Amazon FBA.. aunque parece que nadie lee las sugerencias por aqui

# data[].attributes.body
Perfiles y calibración de dispositivos para impresión y digital.

# data[].attributes.body
Conceptos como trans

# data[].attributes.body
curso de phyton con bases de datos mysql

# data[].attributes.headline
Curso de Investigación y Gestión de la Información. 📚

# data[].attributes.subject
Curso de Investigación y Gestión de la Información. 📚

# data[].attributes.body
En el mundo de ahora, donde tenemos millones de bytes de información en la palma de nuestra mano, es necesario que se enseñe sobre como investigar correctamente y el saber como organizar y refinar esa información que necesitas para tus proyectos o vida diaria.
----------------------------------------------------------------
Me encantaría que hubiera una forma de poder platicarles las ideas que tengo sobre esto, ya que trato de especializarme en este tema y hacer una estrategia efectiva en la cual se pueda tener una buena gestión de la información que se pueda implementar a cada ámbito de Plazti (Programación, diseño, crecimiento profesional, Marketing, etc.) y del mundo laboral.

Les dejo una imagen de apuntes que hago a la hora de la investigación y gestión.

Alexis Santiago Lopez
Tw: @AlexSanLpez1

# data[].attributes.body
Quiero este Curso en Platzi
Nunca pares de Aprender

Anahi Salgado
 +  339
●
9d

# data[].attributes.body
Un curso de React Native con Mobx State Tree

# data[].attributes.body
Me gustaría un curso de como funciona un Call Center en la Parte Operativa

# data[].attributes.body
Este tema se aborda en el curso de Big Data con AWS...
Pero sería estupendo que creen un curso específico de ElasticSearch!