Get 100% marks in 510-410 exam with these Free Exam PDF

At, we give very legitimately Sybase 510-410 Actual Questions that are needed for the Passing 510-410 test. We genuinely empower people to improve their insight to remember the Sybase ase sql developer associate practice exam and guarantee their 100 percent achievement. It is the best choice to lift up your situation in your association.

Exam Code: 510-410 Practice test 2022 by team
Sybase ase sql developer associate
Sybase developer health
Killexams : Sybase developer health - BingNews Search results Killexams : Sybase developer health - BingNews Killexams : Samsung adds new developer tools for Health and Wellness

Samsung developer tools

Samsung is launching a new range of developer tools for Health and Wellness ahead of its 2022 Samsung Developer Conference.

Samsung will be working with a range of health providers and also adding a new fall detection API to their platform and more.

Samsung Electronics unveiled a series of new tools ahead of the Samsung Developer Conference 2022 (SDC22) that will aid developers and communities in shaping health, wellness and safety habits for consumers everywhere. These tools include the Samsung Privileged Health SDK program for select partners, the Fall Detection API to support user safety, Samsung’s new end-to-end research solution for educational, clinical and healthcare programmers, as well as ongoing opportunities for partners with Health Connect.

“Samsung’s health foundation is rooted in our advanced hardware and sensor technology and is bolstered by our open ecosystem and collaborative approach,” said TaeJong Jay Yang, Executive Vice President and the Head of Health R&D Team at Mobile eXperience Business, Samsung Electronics. “That is why I am excited to announce expanded developer tools, APIs and partner offerings that allow third-party experts, research centers and universities to advance wearable tracking and insight capabilities for a wider health, wellness and safety.”

You can find out more details about these new Samsung developer tools for Health and Wellness over at Samsung’s website at the link below.

Source Samsung

Filed Under: Technology News

Disclosure: Some of our articles include affiliate links. If you buy something through one of these links, Geeky Gadgets may earn an affiliate commission. Learn more.

Latest Geeky Gadgets Deals

Tue, 11 Oct 2022 23:11:00 -0500 Roland Hutchinson en-US text/html
Killexams : Small business needs a different sort of software developer

Software developers are some of the most highly sought-after IT professionals, and many companies consistently struggle to find the coders they need. 

That can be especially true of smaller businesses, particularly if they lack the money to tempt developers who might otherwise end up going to big technology companies. But what's also true is that not every developer wants to work for a giant, faceless corporation. And in any case, every software developer has to begin designing code somewhere, whether at a mid-size tech company or their old college roommate's startup, which means that smaller businesses are often a route into the industry for many developers just starting out.

And depending on a company's size, a developer will face different challeges and use different skill sets.

Brendan O'Leary, developer evangelist at GitLab, says that smaller companies can offer greater feelings of connectedness between a developer and their work's impact on their company. O'Leary says smaller companies allow developers to focus more on their cycle time, which is the time it takes from writing the first line of code to seeing it go into production.

That can be a huge advantage that a small company can offer, he says: "That's an intrinsic motivator that's really hard to replace with money or anything else."

O'Leary says developers at larger companies are more likely to feel disconnected from their work's direct impact on their company and its customers. 

Also: The future of the web will need a different sort of software developer

Amanda Richardson, CEO of CoderPad, agrees that developers at smaller companies have a unique chance to witness the fruits of their labor by working on a project in its entirety.

"Working at a smaller company can provide the opportunity to work from start to finish on projects while seeing the immediate impact of your work," she says. 

According to Richardson, small businesses might be the route new or inexperienced developers choose, as startups are typically operating within the bounds of small budgets. Developers at smaller companies will need excellent problem-solving and research skills. On the other hand, she says more prominent companies are in the market for IT professionals who might not have a broad scope of experience in all facets of software development but have a deep understanding of one specific topic.

"Because budgetary constraints often mean startups can't match the pay of large companies, they are more open to considering profiles that don't tick all the boxes in terms of degrees or professional experience," she says.

Bigger businesses do offer specific advantages for certain types of individuals. At a larger company, software developers and engineers can expect more structure, clearly designated roles and responsibilities, and established processes. A larger company is probably further along in its DevOps growth and hires developers who are ready to face a project head-on. That can be a good environment for someone just starting out.

"Working as a developer at a large company implies a structured environment with well-established processes and roles," Richardson says. "It can be especially valuable for young graduates to learn within a structured environment and see software development at scale while acquiring best practices."

The downside, of course, is that developers in a bigger business might find themselves completing mundane tasks. According to a Stack Overflow survey, 45% agreed that feeling unproductive is the number one reason they're unhappy at work, with inflexible working practices not far behind as something to complain about.

This issue is particularly true at larger companies if developers work on a small part of a larger project, with each team of developers holding one piece of the puzzle, and little sense of what the completed work looks like.

In contrast, smaller companies can offer software developers a more comprehensive range of knowledge, as each developer will need to take on more pieces of the puzzle and manage more parts of a project. At these companies, developers will be closer to understanding a problem and will work closely with the required steps to find a solution. 

Both Richardson and O'Leary agree that smaller companies have a slight advantage over larger companies with how fast they can develop new software. 

Richardson thinks this advantage is because larger companies must make more complex decisions. At the same time, O'Leary says it's because developers can focus more intensively on their cycle time at smaller companies.

Larger companies overcome some of the challenges of building software by using smaller groups to make the process more manageable. Smaller teams can communicate and collaborate faster, releasing software at lightning speed. As a company grows, it will need to split its engineers and developers into much smaller teams, and each team will oversee a small portion of a project.

Even some of the largest tech companies still want their developers to keep to small teams, to emulate the agility of small businesses.

"The smaller the team, the better the collaboration," says Amazon – hardly a small company – in its so-called "two-pizza team rule", which states that DevOps teams should be small enough for two pizzas to feed everyone on the team.

"Collaboration is also very important as the software releases are moving faster than ever. And a team's ability to deliver the software can be a differentiating factor for your organization against your competition. Imagine a situation in which a new product feature needs to be released or a bug needs to be fixed – you want this to happen as quickly as possible so you can have a smaller go-to-market time," it says.

Also: GitHub vs GitLab: Which program should you go with?

Flexibility is another factor. Richardson says developers working at small companies and startups have more autonomy and responsibilities than they would at larger business. This autonomy creates room for developers to pitch new ideas to the company. According to the Stack Overflow survey, 39% of respondents said that a lack of growth opportunities makes them unhappy with their jobs. A developer's possibilities to expand and grow in their career might be much higher at smaller companies.

But the same autonomy can mean a lack of guidance and more room for error.

"The drawback of working for a smaller company is you're unlikely to have the reassuring support of a seasoned engineer to answer questions and help you ramp up or be able to test your ideas at scale," she says.

O'Leary says it all depends on the developer and what kind of career goals they have. Some people might enjoy the challenges of trialing new code and solving problems that small businesses face. Others might prefer the stability of a larger, more established company.

Working at a small, mid-size, or large company has positive and negative aspects. It all depends on what an individual developer or engineer strives for in their career, and how many responsibilities they'd like to take on in their professional lives.

But it's almost universal for developers to want to understand the impact of their work and feel like the work they complete is meaningful and valuable to society. So in a tough market, hiring managers at companies big and small should look at the work they are offering and consider how the developers they recruit can be made to feel like they are really making a difference.

Sun, 09 Oct 2022 12:00:00 -0500 en text/html
Killexams : Health News

President Joe Biden is highlighting his administration’s efforts to lower prescription drug costs on Friday as part of his three-state Western tour this week, as he confronts a sobering inflation report in the waning weeks before midterm elections

October 14

Sun, 20 Aug 2017 00:17:00 -0500 en text/html
Killexams : SYBASE Data Types Killexams : SYBASE Chapter, First Edition : SYBASE Data Types
SAS/ACCESS Software for Relational Databases: Reference

Every column in a table has a name and a data type. The data type indicates to the DBMS how much physical storage to reserve for the column and the format in which the data is stored. SYBASE data types fall into four categories: types for character data, types for numeric data, types for abstract values, and user-defined data types. Each of these types is described in the following sections.

Note:   SAS/ACCESS does not support the following SYBASE data types: BINARY, VARBINARY, IMAGE, NCHAR(n), and NVARCHAR(n). SAS/ACCESS provides an error message when it attempts to read a table that has at least one column that uses an unsupported data type.  [cautionend]

You must enclose all character data in single or double quotation marks.

CHAR(n) is a character string that can have 1 to 255 letters, symbols, and numbers. You specify the maximum length of the string with n. Storage size is also n, regardless of the real entry length.
VARCHAR(n) is a varying-length character string that can have 1 to 255 letters, symbols, and numbers. You specify the maximum length of the string with n. Storage size is the real entry length.
TEXT stores character data of variable length up to two gigabytes. SAS supports the TEXT data type provided in SYBASE; however, SAS only allows a maximum of 32,767 bytes of character data.
Exact numeric values have specified degrees of precision (p) and scale (s). NUMERIC data can have a precision of 1 to 38 and scale of 0 to 38, where the value of s must be less or equal to than the value of p. The DECIMAL data type is identical to the NUMERIC data type. The default precision and scale are (18,0) for the DECIMAL data type.
Floating-point values consist of an integer part, a decimal point, and a fraction part, or scientific notation. The exact format for REAL and FLOAT data depends on the number of significant digits and the precision that your machine supports. You can use all arithmetic operations and aggregate functions with REAL and FLOAT except modulus. The REAL (4 byte) range is approximately 3.4E-38 to 3.4E+38, with 7-digit precision. The FLOAT (8 byte) range is approximately 1.7E-308 to 1.7E+308, with 15-digit precision.
Integers contain no fractional part. The three integer data types are TINYINT (1 byte), which has a range of 0 to 255; SMALLINT (2 bytes), which has a range of -32,768 to +32,767; and INT (4 bytes), which has a range of -2,147,483,648 to +2,147,483,647.
BIT data has a storage size of one bit and holds either a 0 or a 1; other integer values are accepted but are interpreted as 1. BIT data cannot be NULL and cannot have indexes defined on it.

SYBASE date and money data types are abstract data types and are described in this section. Refer to your documentation on Transact-SQL for more information about abstract data types.

SMALLDATETIME data is 4 bytes long and consists of one small integer that represents the number of days after January 1, 1900, and one small integer that represents the number of minutes past midnight. The date range is from January 1, 1900, to December 31, 2079.
DATETIME data has two 4-byte integers. The first integer represents the number of days after January 1, 1900, and the second integer represents the number of minutes past midnight. Values can range from January 1, 1753 to December 31, 9999.

DATETIME values are input as quoted character strings in various alphabetic or numeric formats. Time data must be entered in the prescribed order (hours; minutes; seconds; milliseconds; AM, am, PM, pm) and must include either a colon or an AM/PM designator. Case is ignored, and spaces can be inserted anywhere within the value.

When you input DATETIME values, the national language setting determines how the date values are interpreted. You can change the default date order with the SET DATEFORMAT statement. See your Transact-SQL documentation for more information.

You can use SYBASE built-in date functions to perform some arithmetic calculations on DATETIME values.

TIMESTAMP data is used by SAS in UPDATE mode. If you select a column that contains TIMESTAMP data for input into SAS, the values are displayed in hex format.
SMALLMONEY data is 4 bytes long and can range from -214,748.3648 to 214,748.3647. When displayed, it is rounded up to two places.
MONEY data is 8 bytes long and can range from -922,337,203,685,477.5808 to 922,337,203,685,477.5807. When input, a dollar sign ($) must appear before the MONEY value. For negative values, the minus sign must follow the dollar sign. Commas are not allowed.

MONEY values are accurate to a ten-thousandth of a monetary unit. However, when they are displayed, the dollar sign is omitted and MONEY values are rounded up to two places. A comma is inserted after every three digits.

You can store values for currencies other than USA dollars, but no form of conversion is provided.

You can supplement the SYBASE system data types by defining your own data types with the SYBASE system procedure sp_addtype. When you define your own data type for a column, you can specify a default value (other than NULL) for the column and define a range of allowable values for the column.

SYBASE has a special value that is called NULL. NULL means that a value in a row is not known or is missing; it does not mean that the value is blank or zero. It is analogous to the SAS System's missing value.

By default, SYBASE columns are defined as NOT NULL. NOT NULL tells SYBASE not to add a row to the table unless the row has a value for the specified column.

If you want a column to accept NULL values, you must explicitly define it as NULL. Here is an example of a CREATE TABLE statement that defines all of the columns for a table to be NULL except for CUSTOMER. In this case, SYBASE only accepts a row that contains a value for CUSTOMER.

create table CUSTOMERS
   (CUSTOMER        char(8)    not null,
    STATE           char(2)        null,
    ZIPCODE         char(5)        null,
    COUNTRY         char(20)       null,
    TELEPHONE       char(12)       null,
    NAME            char(60)       null,
    CONTACT         char(30)       null,
    STREETADDRESS   char(40)       null,
    CITY            char(25)       null,
    FIRSTORDERDATE  datetime       null);

LIBNAME Statement Data Conversions

LIBNAME Statement: Default SAS Formats for SYBASE Server Data Types shows the default SAS System variable formats that the libname statement assigns to SYBASE data types during input operations.

LIBNAME Statement: Default SAS Formats for SYBASE Server Data Types

SYBASE Column Type SAS Data Type Default SAS Format
CHAR(n ) character $n. (n <= 255)

$255. (n > 255)

VARCHAR(n ) character $n. (n <= 255)

$255. (n > 255)

TEXT character $n. (n <= 32,767)

$32,767. (n > 32,767)

BIT numeric 1.0
TINYINT numeric 4.0
SMALLINT numeric 6.0
INT numeric 11.0
NUMERIC numeric w, w.d (if possible)
DECIMAL numeric w, w.d (if possible)
FLOAT numeric
REAL numeric
MONEY numeric DOLLAR24.2

LIBNAME STATEMENT: Default SYBASE Data Types for SAS Variable Formats shows the default SYBASE data types that the LIBNAME statement assigns to SAS variable formats during ouput operations.

You can override these default data types by using the DBTYPE= option on the data set.

ACCESS Procedure Data Conversions

PROC ACCESS: Default SAS Formats for SYBASE Server Data Types shows the default SAS System variable formats that the ACCESS procedure assigns to SYBASE data types.

PROC ACCESS: Default SAS Formats for SYBASE Server Data Types

SYBASE Column Type SAS Data Type Default SAS Format
CHAR(n ) character $n. (n <= 200)

$200. (n > 200)

VARCHAR(n ) character $n. (n <= 200)

$200. (n > 200)

BIT numeric 1.0
TINYINT numeric 4.0
SMALLINT numeric 6.0
INT numeric 11.0
FLOAT numeric BEST22.
REAL numeric BEST11.
MONEY numeric DOLLAR24.2

The ACCESS procedure also supports SYBASE user-defined data types. The ACCESS procedure uses the SYBASE data type on which a user-defined data type is based in order to assign a default SAS format for columns.

Note:   The DECIMAL, NUMERIC, and TEXT data types are not supported in PROC ACCESS. The TIMESTAMP data type is not displayed in PROC ACCESS.  [cautionend]

DBLOAD Procedure Data Conversions

PROC DBLOAD: Default SYBASE Data Types for SAS Variable Formats shows the default SYBASE data types that the DBLOAD procedure assigns to SAS variable formats.

PROC DBLOAD: Default SYBASE Data Types for SAS Variable Formats

SAS Variable Format SYBASE Data Type
$w., $CHARw., $VARYINGw., $HEXw. VARCHAR(w)
IBw.d, PIBw.d INT
FRACT, E format, and other numeric formats FLOAT
any datetime, date, or time format DATETIME

The DBLOAD procedure also supports SYBASE user-defined data types. Use the TYPE= statement to specify a user-defined data type.

Inserting TEXT into SYBASE from SAS

TEXT data can only be inserted into a SYBASE table by using the BULK= data set option, as in the following example:

data yourlib.newtable(bulk=yes); 
   set work.sasbigtext;

If the BULK option is not used, you will receive the following error message:

ERROR: Object not found in database. Error Code: -2782 
An untyped variable in the PREPARE statement 'S401bcf78' 
is being resolved to a TEXT or IMAGE type. 
This is illegal in a dynamic PREPARE statement.

National Language Support for SYBASE

To support output and update processing from SAS into SYBASE in languages other than English, special setup steps are required so that date, time, and datetime values can be processed correctly. In SAS, you must ensure that the DFLANG= system option is set to the correct language. This can be globally set by the system administrator or set by a user within a single SAS session. In SYBASE, the default client language, set in the locales.dat file, must match the language used in SAS.

Copyright 1999 by SAS Institute Inc., Cary, NC, USA. All rights reserved.

Mon, 06 Dec 2021 11:15:00 -0600 text/html
Killexams : South Omaha health, recreation campus scrapped by developer after cost rises

A health and recreational campus that would have spanned a 25-acre industrial tract of land no longer is on the table.

Developers found that the project, which was expected to cost more than $100 million, no longer was feasible on the site, David Lutz said.

Lutz is president and co-founder of Community Health Development Partners, the company behind the proposed campus.

“What became clear is what we thought was going to be a $100 million project was multiples of that,” he said.

The site, near 28th and Martha Streets, proved difficult to build on. Infrastructure costs would have been much higher than anticipated, Lutz said.

The project, dubbed The Intersections, was introduced in November 2021. It would have offered recreational facilities, including an electronic sports arena and for-profit health care programming.

People are also reading…

The boundaries of the campus would have been roughly Martha Street on the north, Deer Park Boulevard on the south, Interstate 480 to the west and Union Pacific railroad tracks to the east.

Lutz said developers had yet to close on the land, so no work has been done beyond a construction fence going up. But developers did purchase about 20 homes near the site.

At the time, homeowners were able to take anything they wanted from the houses, so many are stripped. Lutz said they’re working on a plan that would restore the houses before putting them back in the community, either for sale or rent.

Lutz said several parties have expressed interest in working with Community Health Development Partners on the housing element.

“We’re committed to leaving the neighborhood in at least as good of condition as we found it,” he said.

The organization paid above market value for the homes, so it’s likely they will take a loss on the homes and overall project.

Lutz said his group still plans to complete a project in Omaha. It would be smaller in scope and would be completed in pieces.

Splitting the project into smaller pieces would be quicker and more cost effective, Lutz said.

He said he expects the first portion to focus on health and wellness and be placed within the general vicinity of the original site.

Not being able to complete the project as intended is disappointing, he said.

“It was an ambitious plan, and I think it would have been great for the community. Everything needs to fit together well, and that just didn’t work,” Lutz said. “But we’re committed to do something in Omaha that’s going to have some of the same components the original plan would have. We’re still very focused and excited to do things for the Omaha community.”

Thu, 29 Sep 2022 08:11:00 -0500 en text/html
Killexams : iOS 16 Developer Beta 3: What to Know Before You get It

This story is part of Focal Point iPhone 2022, CNET's collection of news, tips and advice around Apple's most popular product.

iOS 16 has only been officially released for three weeks now, but iPhone users are already preparing for the bug fixes and feature additions that will arrive with iOS 16.1, expected in October. A third developer beta for 16.1 previews those fixes and features, but it's not for everyone.

CNET Tech Tips logo

The first beta version of iOS 16.1 brought developer tools for the new Dynamic Island and a Clean Energy Charging feature. The second beta added a whole new look for the reintroduced battery percentage icon.

iOS 16.1 beta 3 continues Apple's trend of making moderate fixes and adding a few new features, the most notable being Live Activities -- a new add-on to the Dynamic Island that lets users track real-time events like sports scores without unlocking their iPhones.

Even if you really want the new battery percentage design and Live Activities, should you get and install iOS 16.1 beta 3? And how do you do it?

Although it's easy to get and install iOS 16.1, developer beta versions aren't intended for general use, especially because they may have unfinished features and issues that might make the iPhone difficult to use. Certain iPhone apps might not work completely with iOS 16.1 yet. These early beta releases are intended for developers, to help them keep their apps up to date while also providing early access to the existing features.

The new battery percentage meter in iOS 16.1 beta 2

The second developer beta for iOS 16 tweaks the battery percentage icon.

Screenshot by Nelson Aguilar/CNET

In short, you probably shouldn't install the developer beta on your primary iPhone. If you really want to get iOS 16.1 early, try to find a spare iPhone that is new enough (iPhone 8 or later) to work with iOS 16.1 instead. For those who still want to dive in, we'll show you how to install the iOS 16.1 developer version, as well as what to do in case you want to revert to a stable version of iOS 16.

Now playing: Watch this: Testing iOS 16 (Edit/Delete Sent Messages, New Lock Screen...


If you want to learn more about iOS 16, check out all the new features you should know about, including some cool hidden features and some other not-so-cool settings.

What to know before you get the iOS 16.1 developer beta

Because the iOS 16.1 developer beta is an early prerelease version, the software could have bugs and other issues.

Again, if you're thinking about downloading iOS 16.1, do it on a backup or secondary phone, if available. The iOS 16.1 developer beta's issues could cripple your iPhone and make it difficult to use, disabling phone calls or text messages or making it extremely laggy. However, if you only have your main phone or tablet available, make sure to back up your iPhone on iOS 16 before updating to iOS 16.1. That way you have the option to return to iOS 16 if there are too many issues on the new OS.

Also, you must have an iPhone 8 or later to run iOS 16.1. iOS 16 and its updates are not supported on the iPhone SE (2016), iPhone 6S, ‌iPhone‌ 6S Plus, ‌iPhone‌ 7 or ‌iPhone‌ 7 Plus and earlier. 

iPhone SE

Fortunately, the 2022 version of the iPhone SE will support iOS 16.

Patrick Holland/CNET

In order to get the iOS 16.1 developer beta 3, you must be enrolled in the Apple Developer Program, which costs $99 a year. If you don't want the latest developer's beta release, you can join the Apple Beta Software program and get the public beta version for free (currently iOS 16, but will soon be iOS 16.1).

How to enroll in the Apple Developer Program

The first step to get the iOS 16.1 developer beta 3 on your iPhone is to enroll in the Apple Developer Program if you aren't already a member. If you're on your iPhone, here's how you can enroll:

1. get the Apple Developer app from the App Store.

2. Launch the app, go to Account and tap Enroll Now.

3. Sign in with your Apple ID credentials.

4. Read through the various benefits and instructions, enter your personal information and scan your ID to verify your identity.

5. Once this information is submitted, you must choose your entity (individual for most people) and agree to the program license agreement.

6. Finally, pay the Apple Developer membership fee (with Apple Pay), which is $99 (about £80 or AU$140) a year.

Signing up for Apple Developer Program

The Apple Developer app is free to get from the App Store.

Nelson Aguilar/CNET

After you successfully make the payment, you'll be redirected to your Account page in the Apple Developer app. Here you can verify that you're now enrolled, and you can also check out the date of your membership's expiration next year.

Install iOS 16.1 beta 3 with an over-the-air update on your iPhone

The easiest way to get the iOS 16.1 developer beta 3 is via over-the-air update -- the way you would update to any other new software release on your device. Here's how:

1. On your iPhone or iPad, go to the Apple Developer Program download page, tap Install Profile for iOS 16.1 beta 3 and hit Allow.

2. Next, open the Settings app, tap on Profile Downloaded and hit Install on the top right when it appears. Enter your passcode if prompted and then tap Install two more times. Your phone will need to restart.

3. Once your phone boots back up, connect it to power, make sure you're on Wi-Fi and go to Settings > General > Software Update. If you don't instantly see an update available, wait a few minutes and check again.

4. Finally, hit Download and Install > Install and enter your passcode to update your device.

iOS 16 on the iPhone

Once you get and install the iOS 16.1 beta 3, any updates will appear as over-the-air updates on your iPhone.

Nelson Aguilar/CNET

After your phone finishes rebooting, you should have access to the latest iOS 16.1 developer beta 3.

Download the iOS 16.1 developer beta using your Mac

Over-the-air updates require a certain amount of storage, and if you don't have that available, using your computer is really the only way to update to iOS 16.1 beta 3 without manually clearing out space.

1. On your Mac, go to the Apple Developer Program download page, find iOS 16.1 beta 3 and click Download Restore Images.

2. get the iOS beta software restore image for your specific device.

3. Next, connect your device to your computer and enter your device passcode or hit Trust This Computer if prompted.

4. Open Finder and click your device in the sidebar under Locations.

5. In General, next to Software, you'll see the latest software your device is running. 

6. Hold down the Option key, click Check for Update and choose the iOS 16.1 beta 3 software restore image you just downloaded from the Apple Developer page.

iOS 16 beta  get on Mac

If you don't have much storage on your device, you can get and install iOS 16 beta 3 using your Mac.

Nelson Aguilar/CNET

The iOS 16 beta 3 software will install on your device. Wait for a few minutes and when your phone reboots, you should have access to the latest version of iOS 16.1.

If you just want to run the regular iOS 16, here's how you can get it right now. And after you do, here are three things to check out with the new iPhone OS.

Mon, 06 Jun 2022 18:44:00 -0500 See full bio en text/html Killexams : ThoughtSpot dev lead: The modern developer relations stack - part #2

This couplet of joint analysis pieces is written in full by Quinton Wall in his role as head of developer relations at ThoughtSpot.

As a company, ThoughtSpot likes to call itself a modern analytics cloud specialist that works in the ‘modern data stack’ space – it has core competencies in delivering natural language search and AI to perform data analytics and enable customers to automate entire business processes.

This series will discuss what software would constitute the best dev relations stack. From community management tools such as Orbit and Common room, how to use GitHub and NPM to track developer activity, mapping user journeys to tie it all together and more.

Choosing the right dev rel stack can make or break the success of developer engagement in your company.

Wall writes as follows…

In part 1 of this series, I described the modern developer relations stack as a technology stack that spans all the activities a developer relations team needs to gather insights into and Strengthen the developer experience. Part 1 focused on usage analytics, user journeys and tutorials and documentation.

Part 2, this article will cover the remainder of the stack: code samples, community management, product feedback and attribution.

Code samples

I’m a huge advocate for as many code samples as possible. Make them complete apps, not just snippets out of context. Put everything in GitHub and promote pull requests from the community. Closely track GitHub stars, forks and NPM downloads to see what is resonating with developers. Use to keep an eye on how your packages compare to your competitors. And why not try CodeTour for Microsoft VSCode too to add a little extra bling to your in-IDE experience.

Once you have your code samples available, make sure that they are easy to run and discoverable. At ThoughtSpot, we recently moved all of our developer workshop content to run via CodeSandbox to eliminate the need for local configuration saving a huge amount of time helping to debug attendees laptop setup and getting them to build apps much faster. Finally, make sure your samples stand out. Salesforce and Contentful do a fantastic job of highlighting their code in trial galleries.

Community management

At the heart of developer relations is the community of developers you serve. Many of us are familiar with Discourse and Slack for managing discussions, or Twitch for live chat, but where engagement fell between the cracks was what developers were doing across channels.

In accurate years, I have seen a massive leap forward in tools to deliver teams a full picture of community engagement. Commonroom, Orbit and Commsor do a fantastic job of filling in the gaps to let you identify which content is resonating, who is engaging with it and which community members are most active across all channels and assets.

Product feedback

On the other side of community management is the importance of using voices of the community to influence product direction. Community members, especially MVPs and early adopters, have invaluable feedback for product managers.

Use Productboard or Airtable to capture developer feedback and aligning product priorities. Once you identify needs, Canny and Dovetail can help user research teams dig deeper into new market opportunities or developer motivations for a feature.


I recently participated in a developer delations roundtable hosted by Sequoia Capital. I had proposed the question of what constitutes the modern developer relations stack? After a lively discussion, one of my peers raised the course of attribution – how do you attribute developer relations activities to sales and pipeline. In general, I am pretty hesitant to measure developer success with sales as the need to drive pipeline can inadvertently impact developer experience, but I get the importance of it.

Out of all the elements of the modern data stack I have discussed in this article, attribution is by far the weakest from an off-the-shelf product offering.

Things are a little easier with developer-led growth products where a developer can add their credit card to signup for a service, but with sales-led and larger cost product lead growth, it’s tricky.

To measure attribution, I’ve usually had to create custom solutions on top of Salesforce Sales Cloud and mash-up insights from Commonroom or Krunchdata, plus custom event/attendee tracking tools to come up with an approximation of developer influence. Eg: Did a developer attend a workshop in the past x months and did a deal close shortly after?

ThoughtSpot’s Wall: I’m a developer first and always an advocate for a great developer experience.

Developer attribution is certainly not a perfect science and an area I am actively investigating more. What I would suggest is to spend time measuring how much it costs to acquire a new developer (commonly called cost-per-acquisition, or CPA.)

Having a clear understanding of CPA helps you decide where you want to invest the budget to acquire devs and measure the success of such investments. This is much easier to measure and more aligned with the goals of providing a good developer experience, than pipeline or sales attribution.

Closing thoughts

The notion of what constitutes the modern developer relations stack, as described in part 1 and part 2 of this series, has intrigued me for years.

Like so much of the technology I work with, it’s constantly evolving.

The elements of the stack however have stayed consistent ever since I sketched the idea on my iPad. The steel thread that ties all of this together and why I love working in developer relations, is the importance of providing a great developer experience. Without it, no matter how much time you invest in your developer relations stack, your product won’t be successful.

Build great products that developers love to use, then measure it to know how to make it better.

Mon, 26 Sep 2022 23:54:00 -0500 en text/html
Killexams : Coinbase Cloud debuts Web3 developer platform

Blockchain infrastructure platform Coinbase Cloud has officially rolled out its Web3 developer platform, allowing users to build new decentralized applications free of charge. 

The new developer platform, dubbed Node, allows users to create and monitor Web3 applications while accessing the Ethereum blockchain and indexers, the company disclosed Wednesday. While Node offers a tiered subscription model, the free plan includes access to advanced APIs that allow for the creation of decentralized applications and nonfungible token (NFT) applications.

Coinbase Cloud claims that Node enables faster creation of Web3 applications while reducing both complexity and cost. This feeds into the platform’s broader service offerings, which include all-in-one access to payments, identity, trading and data infrastructure.

As the name implies, Coinbase Cloud was created by crypto exchange Coinbase in 2021 to provide developers with familiar tools for building decentralized products. Shortly after the developer suite was launched, Coinbase executives proclaimed that they “want to be the AWS of crypto,” referring to Amazon Web Services, which powers the enterprise cloud market.

Related: Web3 is creating a new genre of NFT-driven music

Web3 has become an all-encompassing buzzword describing some future version of the internet. Still, developers, venture capitalists and investors have a hurry interest in identifying and formulating what this future internet will look like beyond the common features of decentralization and user-controlled communities.

At the accurate Australian Crypto Convention, whic Cointelegraph attended, Trust Wallet CEO Eowyn Chen said three roadblocks were preventing widespread Web3 adoption: security, ease of use and privacy. While she outlined some solutions, Chen said the bear market could provide an excellent opportunity to address consumer concerns before Web3 concepts attract more mainstream attention.